Nebulous112

Sure thing, Z! All done.
I couldn't find the wiki edit announcement you mentioned at a quick glance, but editing the wiki seems to be like riding a bike, lol. I think I've still got it.

I would suggest FAR - Forgotten Argonian Roots. https://www.nexusmods.com/skyrim/mods/42043/?

MO uses a virtual file system, so Skyrim or SKSE must be launched through MO for the installed mods to have effect.

Ignore the MO warning.
 
Easy to miss, but STEP actually recommends turning off the warning in MO as part of the initial MO setup.
 
"Go to the Plugins tab and click Basic diagnosis plugin on the left and double-click true next to check_modorder and change it to false."
 
https://wiki.step-project.com/Mod_Organizer#Recommendations

Ignore the MO warning.
 
Easy to miss, but STEP actually recommends turning off the warning in MO as part of the initial MO setup.
 
"Go to the Plugins tab and click Basic diagnosis plugin on the left and double-click true next to check_modorder and change it to false."
 
https://wiki.step-project.com/Mod_Organizer#Recommendations

Ralof issue is a known bug with Cutting Room Floor.
 
The carts going crazy is known as the "Helgen wild ride". Very well known. Just happens when there are a ton of scripts firing during the intro sequence.
 
The best way to fix that is to use Arthmoor's Alternate Start - Live Another Life mod. https://www.nexusmods.com/skyrim/mods/9557/?
 
Wait a few minutes before talking to the statue. The vanilla start is "crossing the border illegally". Something to skip the cart ride altogether, but put you in the same general area to continue from vanilla is "camping in the woods".

Ah, what DY I believe calls "Modder's Paradise" mode. Delete the bShowMarkers from Skyrim.ini. That should do it.

Hmm, the "ssl" in the dll filename makes me think downloading this might fix it: Win32 OpenSSL v1.0.2h Light from here. That is the light version of the full OpenSSL library for Windows.
 
I had some SSL errors with MO a while back and downloading that fixed it for me...I found this from an old link that GrantSP posted regarding this quite a while ago. I think another user recently posted a link for this as well and said it solved his SSL issues.

You are using crash fixes with the preloader? UseOSAllocators=1?
 
I think that crash can be caused by memory fragmentation. You need the new Crash Fixes 12 beta 4. Set it up the same way, but there are settings for memory blocks and an allocation log. If you check the posts section, on the first page or a page or two back there is a good explanation of how to set up the memory allocation blocks to reduce fragmentation. Should get rid of that crash.
 
On mobile atm, so it would be a pain for me to try and look up to quote.
 
If you can't find the info or get it working let me know and I will post more info this afternoon.

You are using crash fixes with the preloader? UseOSAllocators=1?
 
I think that crash can be caused by memory fragmentation. You need the new Crash Fixes 12 beta 4. Set it up the same way, but there are settings for memory blocks and an allocation log. If you check the posts section, on the first page or a page or two back there is a good explanation of how to set up the memory allocation blocks to reduce fragmentation. Should get rid of that crash.
 
On mobile atm, so it would be a pain for me to try and look up to quote.
 
If you can't find the info or get it working let me know and I will post more info this afternoon.

Yeah, those aren't in Falskaar IIRC.
 
As long as you set it up per this you should be fine (making sure you used the updated INI, and set the program up per the screen shots - except for the Behave foliage settings which should be disabled for any mods).
 
The only way I can think to "test" is check the log file and see the changes, and compare the sizes of the optimized textures to the unoptimized ones.
 
Also, in-game if you have purple missing textures then something went wrong, obviously. ;-)

For STEP Core you need the LOOT rules for ELE, Relighting Skyrim and AOS. The Book Covers Skyrim rule is not needed because that mod is not in STEP Core (only Extended).
 
Run LOOT through MO. In LOOT, find each of the mods in question. You can use the search bar at the top to make it easy. Then click the icon with the three vertical dots on the side of the mod you want to add the LOOT Metadata rule to.
 
For ELE and Relighting Skyrim, you need to add a priority number. To do this, in the "Main" tab after you click the dots icon, you will see a slider with Global Priority. Move the slider so that it turns blue (this will turn on global priority). Then under Priority Value, enter the value specified by the guide. When you are done, click the save button (looks like a blue floppy disk).
 
For AOS, you need a load after rule. After you click the dots icon, click the "Load After" tab. Click the "+" sign, then input the name of the plugin. It needs to be spelled correctly, and include the ".esp" at the end. If you include an extra space, or anything like that it will screw it up. It needs to be exactly the plugin name with the extension and nothing else. I just copy and paste from the guide. Again, when you are done, click the blue floppy disk icon to save.
 
Edit: Just to note, after the rules are done just press the icon with the three stacked horizontal lines at the very top (top-left button) to sort the load order.

For STEP Core you need the LOOT rules for ELE, Relighting Skyrim and AOS. The Book Covers Skyrim rule is not needed because that mod is not in STEP Core (only Extended).
 
Run LOOT through MO. In LOOT, find each of the mods in question. You can use the search bar at the top to make it easy. Then click the icon with the three vertical dots on the side of the mod you want to add the LOOT Metadata rule to.
 
For ELE and Relighting Skyrim, you need to add a priority number. To do this, in the "Main" tab after you click the dots icon, you will see a slider with Global Priority. Move the slider so that it turns blue (this will turn on global priority). Then under Priority Value, enter the value specified by the guide. When you are done, click the save button (looks like a blue floppy disk).
 
For AOS, you need a load after rule. After you click the dots icon, click the "Load After" tab. Click the "+" sign, then input the name of the plugin. It needs to be spelled correctly, and include the ".esp" at the end. If you include an extra space, or anything like that it will screw it up. It needs to be exactly the plugin name with the extension and nothing else. I just copy and paste from the guide. Again, when you are done, click the blue floppy disk icon to save.
 
Edit: Just to note, after the rules are done just press the icon with the three stacked horizontal lines at the very top (top-left button) to sort the load order.

Nice find! :-)
 
Nope, that is an issue everyone has, I'm pretty sure.
In the SR:LE known issues, Neo states:
 
I don't think anyone has known about this fix until now. Nice!
 
Edit: Did you just use the main file?
 
Also, it mentions Rustic Windows...did you use it as well?

Nice find! :-)
 
Nope, that is an issue everyone has, I'm pretty sure.
In the SR:LE known issues, Neo states:
 
I don't think anyone has known about this fix until now. Nice!
 
Edit: Did you just use the main file?
 
Also, it mentions Rustic Windows...did you use it as well?

PapyrusUtil maybe created them? All of those mods use PapyrusUtil IIRC. Not sure.
 
I would just move each to their corresponding mod, preserving the file / folder structure for each. That should prevent them from going back into overwrite.

PapyrusUtil maybe created them? All of those mods use PapyrusUtil IIRC. Not sure.
 
I would just move each to their corresponding mod, preserving the file / folder structure for each. That should prevent them from going back into overwrite.

Look on the bottom of the MO screen, you may have accidently checked the sort by groups option. There should be a drop down list with two or three items near the bottom of the screen which will allow you to make it look normal again.

Yes. The prompt to merge the files will occur if MO detects they are from the same Nexus page. If you change the name when you go to install the dragon priest update file to the same name as you used for Improved Closefaced Helmets, you will force the prompt to appear.

Yes. The prompt to merge the files will occur if MO detects they are from the same Nexus page. If you change the name when you go to install the dragon priest update file to the same name as you used for Improved Closefaced Helmets, you will force the prompt to appear.

If you are using Neo's guide and he doesn't mention something, you don't need it. I have no experience with SR:LE Extended, but I imagine it is the same.
 
If you are adding mods besides what is listed in either guide, then check out what the DynDOLOD patches are and if you need them. When you download the v2.07 Beta there will be a manual included. Look there.

If you are using Neo's guide and he doesn't mention something, you don't need it. I have no experience with SR:LE Extended, but I imagine it is the same.
 
If you are adding mods besides what is listed in either guide, then check out what the DynDOLOD patches are and if you need them. When you download the v2.07 Beta there will be a manual included. Look there.

It definitely shouldn't be ignored. Missing masters will cause the game to CTD on startup. However, it worked fine for me... try doing the process again. Download the main file from RS Children, the BoS patch and the merged complete and hide or delete the two .esp files indicated. Then download the new file from the link that Neo gives, and overwrite the old merged USKP .esp.
 
Then do the rest of the steps.
 
It sounds to me like it didn't properly overwrite the old merged USKP .esp when you installed it.

Yes, that is the value you should change. The number refers to (what I think is called) the keyboard scan code. B = 66.
 
https://www.cambiaresearch.com/articles/15/javascript-key-codes

Yeah, you are supposed to follow the steps exactly in the procedure. The script should be called DynDOLOD TexGen. Adding the TES5Edit files from Step 2 of the Installation procedure should have made that script appear when you next ran TES5Edit.
 
Try looking through the procedure again, but this time follow the screenshots. Every step has an accompanying screenshot...if it doesn't jive with what you are seeing, it's possible you missed a step along the way.