anjenthedog

Little followup 1) couldn't find a version of improved camera that included freeflycam, although I only looked at the couple versions I actually archived., so I was probably wrong about where it came from. (although I still have no idea how it ended up on my system, since I don't use and never used ENB) 2) For the OP, (or anyone else interested) freeflycam is apparently available as a standalone and appear to be directly associated with ENB users, and has been for ~3 years see:

At a wild, speculative guess (only because I've been having issues with the hair and wigs since I installed 1.6.1170 and have seen even worse) it could/might/maybe be improperly "fit" (Bodyslide), so it's not sitting at the "correct" height on the head model, and things that aren't meant to be seen are being seen.

Hmm. OK, obvious answer (although perhaps not a "correct" answer/the answer that solves your issue ... idk) Aside from installing the correct version of SKSE for your game version, (In this case it'd be the one spec'd for use with 1.6.1170), after installing SKSE, and after first running the game at least once using the native Bethesda launcher, you use the SKSE game loader (skse64_loader.exe) to run Skyrim SE/AE. If not, you won't see SKSE operating, and, as a result, any SKSE dependent mods won't work. -- Beyond that "doh!" solution (it does happen), I'd figure that one or more mods are screwing with SKSE and "breaking" it quietly (ie game will run but SKSE doesn't work properly). Often times in the past (for me), it'd be installing an LE mod or another mod "Not made for Skyrim SE" that results in that issue. The solution in that case was to drop the associated mod(s) until a version-compliant mod could be sourced, and failing that, shrugging my shoulders and moving on.. If you're new to 1.6.1170 or "AE" in general, many support mods you might be familiar with from 1.5.97 have been updated specifically for AE, and while a few kinda work in 1170, any which have been updated (ex: many have new -NG variants made for AE) should be used in favor of the older ones you *might automatically install based on 1.5.97, as they can cause glitches in SKSE or in newer versions of mods with "AE" features or that rely on "AE" code changes as well. good luck

Somewhat academic question (fwiw): Is the presence of a dll (and ini where applicable) in the SKSE folder sufficient to be automatically included in the game compilation/launch?) Just wondering if one could choose to use it if they had possession of the dll and ini...

ps> confirmed there is no FreeFlyCam in my present (1.6.1170) installation.

Could be from an ENB mod, idk. I don't use ENB directly though... Have used a few different premade reshaders in the past, and otherwise I've used community shaders for the past ~year, including ~6 months or so under 1.5.97 (when it still acted like that for me). tbh, I'm still not exactly sure where FreeFlyCam came from. just guessing. So for the OP. see if you can find old beta versions of Improved camera. One of them *might include freeflycam, although I'm not sure how you'd manually parse it out so it can be recognized within skyrim. (and I probably wouldn't install an old beta version atop the newer one either)

Necro topic, but tbh, the best I could come up with back when I was experiencing it, is that one of the versions of Improved Camera, back when it was still in Alpha or Beta, added the modified behavior incidentally as part of its 'exploratory camera behavior improvements' during its development release phase, and either intentionally or unintentionally left the modified behaviors in place even when updating the mod (When it crashed, 1.5.97 died with what is the current version of improved camera installed, but those behaviors were still present... Improved Camera had been updated - incremental version by version up - to the release version, not installed "clean" ) I haven't seen any evidence of it in the 1.6.1170 environment I recently installed to replace the failed 1.5.97, and presumably, if my theory has any merit, since I simply installed the mod in its current form without any interim versions that inserted it. EDIT: --- And, fwiw, just looked at my old steamapps folder (archived when I thought I could till resurrect the old installation) the app (or DLL more specifically) involved is "FreeFlyCam.dll" This is the contents of the accompanying ini file (FreeFlyCam.ini). As you can see, there are hotkey definitions for camera roll and other "non standard" functions

Do you use and have you updated NVidia drivers within the past ~month or two? I see this during startup after a recent Nvidia Driver update that is now down-converting a larger footprint virtual canvas to 1080 "for improved detail" or something to that affect. When it hangs in the oversized footprint "mode", just click inside it and it should readjust to fill only one screen. It's also a bit "glitchy" on game unload, when the graphics mode is reset As for a real fix, idk, but if you find one, please post it...

Ok. whatever works. I was just saying, if you intend to restart the quest, the easiest way (IMO/IME) is just to take a few steps back. The quest itself takes all of a couple game days to complete (at best a couple days) and redoing the "work" it takes to complete it is pretty insignificant.

The easiest way is to start over from a savefile from prior to encountering the quest. And ideally, prior to even stepping foot into the city, since housekeeping will likely delete the victim's body after you've visited the area once, (erven if you didn't walk right by her) unless you have a third party dead-body mod AND have set it to keep anything you didn't kill yourself.

What is "automatic quarantine"? Do you mean your system quarantined it (ie as a virus or something)? Do you mean that you weren't able to access the mod page? If the former, could be, likely isn't a virus and is throwing a false flag, but I can't judge authoritatively so I'll just say "idk". If the latter, it's possible the mod author has moved on and shut down his or her mods from access, (for whatever reason) or that Nexus has some issue with said mod and quarantined it to prevent an actual problem (flawed file assemblage, missing content, something illegal like the occasional pedo content that shows up, or cloning someone else's content as their own, etc) or to address some Nexus promoted political controversy (ex: banning a mod that sought to remove LGBTQ posturing banners from a certain game...I think it was Spiderman but can't recall...) Anyway, back to the original question. What is "automatic quarantine"? without a clear def, all I can do is speculate as to your intent.

If they're invisible, the robes either haven't been built in Bodyslide and need to be (some armor mods come playable, some MUST BE FITTED before using) or are otherwise missing. The former is far more often the problem (ime) than the latter. (the latter being an issue of them not being included in the mod. something I've run into one or two times over the past 6 years) odd flat colors usually mean a problem with textures. invisibility means an issue with missing meshes

Improved Camera works just fine. Been using it since it was in early beta, maybe even back to alpha idk. Not sure what that ImmersiveCamera.ini error is about though. Perhaps there's a conflict between your existing camera mod (or some adjunct) and Improved Camera. I'd check for patches. PS> what IC proports to do (and afaik does) is conjoin your player perspective to the 3rd person body, at all times, irrespective of whether you're in 3rd person or 1st person. (ie, when in 1st person and you see your hands wielding a weapon or casting a spell, you're seeing your 3rd person hands, and when you look down, you're seeing your 3rd person feet or body, whereas in vanilla, when in 1st person, you're seeing "1st person hands" and vaguely, as I recall, nothing when looking down (note: I could be wrong on looking down, been quite a while since I started using IC)

At this point, (I've only had 1.6.1170 running for about a month and a half so far, after 1.5.97 died on me last Oct/Nov... edit: note: died because of a Steam FU that left the game inaccessible by Steam for play authorization, not because of installed mods), no, I haven't been forced into a new game. (with the exception of doing so to create my two new player character instances) And tbh, honest, while I did have some routine issues with 1.5.97, I never *had to* start a new game, I simply dealt/coped with the issues as they reared their figurative heads. The main issue I faced in 1.5.97 was a somewhat routine freeze termination, very likely (ie almost certainly) caused not by mods but by my overloading the game with too "stuff" much for my video subsystem to handle (1060SC 6G card) My new games were to introduce new player instances. That's all. The one REAL issue that I faced (and still face) with some routine as I periodically decided to purge old mods I wasn't really capitalizing on, or had grown tired of, or I had decided I wanted to replace with something else, was in *uninstalling* those existing mods. Some (most) uninstalled without issue, some uninstalled with resolvable issues, and a small handful, that once installed and played on for a while, simply cause the game to terminate without their presence (either disabled OR uninstalled was good enough to cause irredeemable havoc), either at game load or at save load, unless I'd go back to a save created before they'd been installed and "re" start from there (with them absent by disable or uninstall). And I'd bet that a substantive majority of those unremovable mods were unremovable because their creators were lazy and or sloppy... My advise about installing mods "mid way" would be "Be careful and test thoroughly after mod installation so you can back out gracefully if it goes belly up", but tbh, I've seen very little to substantiate the overbearing, preachy, condescending scolding about never installing mods "midgame" that some have engaged in over the years on the subject. I see no evidence to justify the sweeping advise. I could see advising people to be careful and make sure that they have older saves to fall back on if their choices lead to a failure, and make sure they have and know how to use utilities like falllrim, sseedit, nifskope etc for addressing issues, etc, but the sweeping fallacy that "And Goyd said: Thou shalt not install and uninstall mods "mid way", or thy Gamelord shall strike thy game dead" is palpably absurd and patently false. Been playing since early 2019. I've installed roughly 1500 mods and uninstalled roughly half as many, all during "mid game' situations. And I'd bet that 90% or more of those "experts" repetitively declaring "though shalt not" all the time have too. And frankly, were I a candid insider in their lives, I'd bet I'd find that their "midgame" installation and uninstallation numbers are far higher than mine. What it would mean, if everyone went by that rule, is that you'd have to start a literally new game every time you added or removed a mod. Worse is, it's no guarantee that said game will run smoothly, but admittedly, it's a really good corporate-level "dark matter" cover-story. Can't explain it? Fundamental model screwed up? Don't have an answer but want to maintain the robes of the "expert"? >>> It's dark matter. Dark matter explains everything. As so does "don't' install mid game"

For all the dire warnings made by experts over the past ~6 years I've been playing, I've had incredibly few problems with it to be perfectly honest