TechAngel85

You really shouldn't need to run DSR very often. I haven't ran it in forever and never have issues.

The external installer shouldn't be used for any mods STEP. It will run for a couple of them automatically as needed.

I think he's saying he turned the internal one back on as he was using the external installer.

Okay, first you have to look past the names of the parameters because there is nothing we can do about those. False = disabled/off True = enabled/on With DisableDriverMemoryManager, we want to allow our hardware to manage the memory; therefore, we do not want ENBSeries managing it. This parameter is mainly for AMD users with older cards. Turning this feature on (setting to true), enables the ENBSeries memory manager. Leaving it disabled (false), allows your hardware to manage the memory. Again, we want our hardware to do the managing so we leave it turned off (false). With DisablePreloadToVRAM, we find the same thing. Setting this to true will disable the preloading of textures and, thus, they will not be loaded until they are visible. This is not the behavior we want and it is not recommended to run with this feature on (true). Therefore, we leave this feature disabled (false). Do not think of the question you're asking yourself. Think, "do I want this feature on or off? False = off. True = on.

This is how we have it handled in the instructions.

If it's just a general update, it should be fine. Most mods can be updated without issue.

You're reading and analyzing it way too much. I'll address this when I have more time and am not on my phone.

Well, it reads the user needs to put one in manually. So I suggested just putting one into the templates so the user wouldn't have to worry about it. That way whenever a template is called on a page it automatically adds a line break.

Could we not just add a line break into the templates to prevent that?

Merging will be okay.

If you do that, skip the cleaning for the other DLC, as well, until you can clean Update.esm

I've completed that section of the Guide without issue unless something changed from MO v1.3.7 to v1.3.8 which is causing it. I could check again tonight if no one else gets to it before then.

I'd still like to compare against the vanilla originals in Nifskope to make sure nothing is missing too, but you may have already done that.

My second run for Extended was under 1.4gb. I'm going to run it again this evening since CRF added a mill and the new UPs seem to have edited a lot of placed objects.

Been working and busy so I haven't had time to check. Most my posting has been from my phone.

Where do you have MO installed?

This will be checked on later today, hopefully. I've already brought it up in a staff section of the forums.

Sounds like you didn't check the box in TES5Edit to backup the plugin. You have to have that box checked as well as the plugin checked after the cleaning is done and before you close the program.

Anymore luck with the issue?

Yeah, it should be active.

Launchy is nice but takes time and effort to set it up for the first time.

This is for STEP use and for STEP specific discussion. The other is used by Sheson in place of his Nexus thread.

Just leave it on its default value. The Inspector Guide explains in more detail.

Laptops have a limited range of resolutions they can run. That might be one that your laptop cannot run in. Check the Screen Resolution settings in Windows to learn which resolutions your laptop can display.

That looks like a custom weapon that isn't in STEP. Do you have any mods installed which affects weapons beyond what is in STEP? I investigated GSaSR more. It seems like everything is right in the files. The meshes are pointing to vanilla paths except with a custom scabbard was made and those point to the correct path as well. I turned to BSW next. It doesn't even touch that file. I have yet to try it out in game to see if it's working on my STEP setup. EDIT: Mine is fine... You must have something messed up. Comparing mine to yours above, you have the wrong scabbard size installed. Reinstall GSaSR.