SotiCoto

Figured. Well, I just went through the motions installing the Version 3 alpha. I see this one is a bit stricter about not putting the Dyndolod folder in the Skyrim VR folder. It didn't like that so I had to move it. Also it didn't like the fact that I had to name the Skyrim VR registry "Skyrim Special Edition" to make the Creation Kit work. Adding extra registry folder for Skyrim VR seemed to fix that. Well, at least if it stops me every single time it finds something wrong in the loading process, presumably that means fewer things that can go wrong in-game. Running DynDOLOD coughed out a ton of warning messages about overriding large references or somesuch, though I'd made sure to set "IgnoreLargeReferences=1" in the DynDOLOD_SSE.ini file. Not sure if that was how it was meant to be. I could vaguely see something about NOT ignoring warnings on the light-mode screen that popped up after the program finished, but I was too busy protecting my retinas from the searing hell of a white screen to take in what it was saying. Now I guess I have to load into the game, put myself in an interior cell and then load up the mod... right? The old one I already went to interior, unticked the MCM, saved, exited, removed, etc. I swear... my University exams were easier than modding Skyrim VR. I've had to start over 4 times already due to major mod issues, and I've sunk just enough time into the last to make it painful if I have to start a 5th. [Edit]: Huh... The Version 3 doesn't have an ESM? But it does have an Occlusion.esp file? Is that right?

Okay. I'll take your last bit of advice for sure. I think it might be too late for the other part since I'd already tried rebuilding the DynDOLOD files when I was trying to fix the issue. I'd guess that the IDs probably change when it is rebuilt, though I don't know. I mean... do they?

Okay. Well, it quite clearly wasn't obvious to me, or I wouldn't have asked. Anyhow... I've got something completely new that I've been informed probably IS something to do with DynDOLOD, though I didn't initially expect it (because everything initially suggested it was an issue with dialogue). I'm trying to work out how to fix a persistent crashing issue near Sarethi Farm with the help of some folks on the CrashLogger page at the Nexus. Here is a pastebin of the crash log. It was suggested to me that DynDOLOD was to blame, probably because it came up quite a few times in the crash log. And from the testing I've been able to do so far, the crashing doesn't seem to occur if the DynDOLOD files aren't active. Re-running the program didn't fix it either, unfortunately. Here is the DynDOLOD Log file, though I couldn't upload this to pastebin as it was too large. So... you wouldn't happen to have any insight, would you?

I don't mean this to be accusatory... but just how much IS DynDOLOD capable of screwing up the game? Asking because... how to put this? I've been installing a lot of mods lately. It wasn't causing me too much trouble until today. And technically today isn't the first time I've ran DynDOLOD, though I believe it was the first time I copied from its target folder to the Data folder. I'm pretty sure I followed the instructions closely, though there are so damned many of them that it overrode my short-term memory span, so I don't remember whether I did it right or not. BUT... after running it for the last time, I noticed that Skyrim VR was frequently freezing up and not progressing. So after some testing and poking, I found that deactivating the DynDOLOD files in the plugin list stopped the freezing. But that came with other issues. For some bizarre reason, I started getting weird animation stuttering that looks like FPS drops (though I can't see the FPS in-game, so I have no damned clue). It just seems REALLY conspicuous now. As in NPCs seem to vibrate when they walk past, and menu screens vibrate weirdly if I move my head. I've tried deleting all the files that came from DynDOLOD but that doesn't seem to fix it. I also tried deactivating all the other mods I installed today, but that didn't fix it. I've tried starting the game over from scratch, and that didn't seem to fix it either. In fact nothing seems to be fixing it... I'm completely at a loss now. I just want to know if DynDOLOD is capable of causing the problems I'm describing under any circumstances, because I can't narrow down the cause of the problem. Like maybe it stealth-changed something in Skyrim's INI files or somesuch? ... Oh... and something changed my computer's region setting to United States from United Kingdom. THAT I'm frankly horrified by. I have no damned clue what is going on, nor whether that change has anything to do with the others, but it is frustrating and confusing (and having to register here just to ask this question rather than being able to ask back at the Nexus is the icing on the stress-cake).