MadWizard25

Ugh this is getting irritating I reinstalled the script, unchecked renumber formIDs, and created a new merged plugin from the REGS patches. Im still getting the same unresolved reference errors. Whats odd to me is that right after the merged plugin creation in tes5edit, checking for errors produces nothing. Once you save the merged plugin by closing tes5edit, and then loading the merged plugin in tes5edit, the errors appear after error checking. One note is that when closing tes5edit after creating the merged plugin, some of the plugins that were merged and/ or were masters, also seem to be modified (thicker text when tes5edit asks to save modified plugins). I never save the modified plugins, only the merged plugin. It seems weird because I dont expect the script to modify the individual plugins that are merged, and then require them to be saved. Is this what im doing wrong? Edit; well I asked on the nexus mod thread, and the author got a bit annoyed. Apparently I have been merging masters... which is bogus, since its easy to tell the difference. Im not merging masters, in this case just the REGS patches. Here is a list of the patches im merging; ETaC - Complete LoS Patch.esp Prometheus_NSUTR BDS Patch.esp Prometheus_NSUTR Falskaar Dock.esp ETaC - BFT Patch.esp REGS Patch - NSutR.esp REGS Patch - CRF.esp REGS Patch - ORS.esp REGS Patch - STEP Extended.esp REGS Patch - 3DNPC.esp And here are the unresolved reference errors im getting; Errors occur whether renumber formIDs is selected or not.

Ah bollocks, I always left the script options on default settings, so Renumber FormIDs was check/ activated in advanced settings. Ill try it without this option. Does running the script without renumbering formids apply to all merging? Is it best practice? If it is, one should wonder why it is on by default... Or does this apply only to patch plugins? Thanks for ninja quick reply.

Okay, so there are issues with merging REGS patches. After creating the merged plugin, saving it, closing tes5edit, opening tes5edit and loading the merged plugin, and then checking for errors via option, results in unresolved references. In fact, im getting this for any merged plugin I make. The amount of unresolved reference errors can be staggering. Im fixing them manually via a repair patch using tes5edit. However, tes5edit has issues when copying as override the merged plugin (which is use as the base for the repair). I have to use the original REGS plugins as the base for the repair the manually drag and drop from the REGS merged plugin. Sometimes that does not even work and tes5edit throws up errors. I then have to manually edit the subrecord. Its... tedious :confused: Just though you should have a heads up. The issue has been reported to the nexus mod page for the tes5edit merge script.

Yep, in MO there are conflicts reported. Ive moved Moon and Stars before SDO, will check in game in a bit. Thanks!

With REGS 3.2.2, I seem to get blue LOD building textures for the village "Little Vivec" from Moon and Stars, once I get in range they switch to standard textures. Any idea why they would be blue for LOD?

Did you try another UNP version to check if the issue is with the mod or your mod setup? I think there is UNPB Redux, as well as loads of alternative skin textures and meshes. THe only other thing i can think of is that you have consistent old people mod remnants baked into your save. Its an unfortunate effect of skyrim that when you uninstall certain mods, they can leave behind orphan scripts in your save. You can try this Save Game Script Cleaner; https://www.nexusmods.com/skyrim/mods/52363/? It may help clean out remnants of the mod. Its seems to work but keep in mind its still new, make backups of your saves if using.

2.2.9 already? Argh, so much to update already. Thanks for the tip on removing mods from the patches, I never did try loading ars metallica, diverse priests and the patch in tes5edit and checking manually for conflicts. I took the shortcut I posted. Ive also found out that the shortcut method does not detect all errors in tes5edit, no idea why its so selective in error checks. Some further info. Merging is a pain, often you get errors in subrecords (which tes5edit error check does not find), maybe this occurs when two mods that edit the same record get merged? I then make sure the merge mod is overwritten by a conflict resolution and repair patch. So its doable but takes even more tes5edit time. Tracking down mods which dont like to be merged; some (or 1) seem to cause CTD on save irritation. Ive narrowed it down to some 20 odd mods, thankfully its not any requiem or REGS patches. SFO addon plugins dont like to be merged either; you get the occasional tree LOD texture up close. Current setup takes up 3.5GB VRAM on average, 3.9GB VRAM at peak. Is this normal? Have a new 4GB card. All textures are 2048x2048, and exterior textures and normals are 1024x1024. Running Real Vision performance ENB with SMAA.

Gratz on increasing stability When you mention removing skyrim - textures.bsa, were you also loading the DDSoptimized textures from that bsa in MO? Just curious

The tool is actually that 1st link that i posted, it is(was) a little html site that asks you some questions and then generates a enblocal file for you. At the moment your best source for your enblocal.ini settings is the STEP Wiki ENB guide that I linked to.

Thanks again for the fast response, all questions answered... for now

I believe it might be referring to this link; https://www.iparadigm.org/pages/pnenb/ENBoost.html Unfortunately the link is dead. In any case, there are no mutiple versions of enblocal.ini, just configure the file manually. Here is a more in detailed guide; https://wiki.step-project.com/Guide:ENB#tab=Installation

Well, now I know this mod exists. The things modders will make

Perfect, thank you, does this apply to the Immersive Winterhold College patches as well? I can confirm this. I have been putting NSUTR BDS patch after No_snow_under_roof. A quick look in tes5edit showed its ok to do so, but perhaps there is a good reason to put it after better dynamic snow? WB kicks up a fuss when it does via the guide way as well.

CJ2311, I have been using mator's script for tes5edit, but have been avoiding REGS mods and patches because of potential navmesh issues. Are there any you know which are safe to merge?

I figured out the issue. It was my modified STEP Extended patch where ars metallica and diverse priest were edited out. I must have made a mistake somewhere. Ill list the steps i took here for the editing out, perhaps someone can spot where i went wrong? 1. Open up WB, save the ars metallica master in the step patch in a new empty .esp (i used thundering shout). Save 2. Open up step patch in tes5edit 3. check for errors 4. Delete all records thrown up by error check (except QUEST group) 5. clean masters 6. do the same for diverse priests Edit: Fixed it, removed whole records accidentally, not sub records as needed.

Run into a problem that i am having difficulty solving. The game starts, and loads the main menu with the dragon symbol. However, there is no start menu. The game runs, its not frozen. ENBoost responds, and both SPM and Task Manager show activity. Ive tried to disabled mods, and have gotten as far down as SR:LE only, previously SR:LE worked fine. Vanilla Skyrim works fine and i can load the start menu. Disabled all interface mods as well, apart from SkyUI. Vanilla inis, verified game files, bash patch, FNIS regenerated. Empty overwrite folder. Needless to say i am a bit puzzled. Google search says its usually a mod issue, but I have none of the mods mentioned. Has anyone ever experienced this issue before? Edit: Its not that the game is taking a long time to load; 10 minutes wait without change is surely enough.

Ah yeah, forgot to mention, im using 3.0 as well. However, i did get the MCM menu with version 4.25 as well. I see what you mean, DSR is compatible with 3.0, my apologies. Missed the * notice for incompatibilities only found in 4.25.

I dont think its fully compatible with DSR. You can only use the DSR vanilla meshes with EO, as well as any mod meshes. So if your installing the full DSR with EO that may be the issue. Are you also using another mod that allows dropping of lit torches? I believe there is one in STEP that needs to be uninstalled if using DSR. Lastly, how are you installing your mods? Using MO, NMM or WB?

Octopuss, if everything is as you say, then you are really only left with option to do a clean reinstall. All your info points to a potentially corrupt install, and steam file verification will not remove additional files or fix every issue. There really is nothing else to recommend with such bizarre CTD issues. If i were you at this point I would do the same. There are so many details and files that get changed added removed during modding sometimes its hard to remember everything that is changed. Best to start with a clean slate at this point. Its recommend by others for a good reason

Did you try and reinstall the mod? Did you try merging it? Because merging can break MCM menus. Make sure you are not using any conflict mods like Dual Sheath Redux or ATTT

Largely I agree, but if you are running STEP Core/ Extended and consistently crash within one minute of vurts stress test, then I would assume there is a problem. The threshold for vurts test is 5 minutes w/o CTD for a reasonable assumption of stable game play... and that is before any additional testing. So yeah, vurts will CTD, but not within 1 minute every time, especially on his hardware setup. I always like to think of vurts stress test as the 1st in a sequence of tests for a mod setup. Edit: Oops, posted past lock request, sorry. Last post was during writing of my post

Did you try verifying the games files through steam? Perhaps something got borked while you were modding? Additionally, you may just have a hardware issue. Try stress testing your GPU. Imo, you shouldnt be crashing on almost vanilla. Vurts stress test will crash eventually, but not after 1 minute on vanilla. Did you configure the skse properly, as in the skse.ini file within Data/ SKSE folder? I know i once overwrote it and forgot to add the memory patch ini settings You could also try raising the settings.

BSA extraction is perfectly safe. I think performance gains are negligible though. The real advantage for BSA extraction is that you get all the loose files from the mod, which allows MO to check if there are conflicts with other loose files from other mods. If its just BSAs MO has no idea whether the contents conflict. Its best practice to extract every mod BSA, there is no downside to doing so. Actually BSA extraction when done normally without MO's virtual directory would technically cause performance issues. The more files within the Skyrim directory, the more work has to be done while the game is running, kinda like real time indexing. Its called the 'thrashing' issue. Thankfully, MO totally solves this with the virtual directory system, so go nuts and extract every BSA. I even extracted the skyrim - textures.bsa and well as all the HRDLC bsas.

@ Nicpod You get 2 dark elf races at character creation? Thats just weird. Reproducible crash at whiterun for me was always a sysmptom of an unstable mod setup, rather than one specific mod. It was always solved by cutting back on mods in general. Your case might be completely different, but yeah this is what i think. @dreadflopp I think texture seams are a vanilla issue? Maybe it just becomes more pronounced if you use certain texture mods.

I was unable to use an ENB. I tried, but the sudden drops in fps, which was essentially the cause of stuttering, were even more pronounced with ENBs. Turning in a direction too quickly was never easy. I did find the the ENBoost setting enableunsafememoryhacks helped reduce stuttering, which was the only setting/ fix that helped, and without any ENB preset. It made the game playable, but not much more than that. Besides, there was an alleged stability trade off, but i didnt really notice the game being more CTD prone or anything. I came to the conclusion that it was hardware limit issue, hence i upgraded.