Nebulous112

Ding ding ding! I think we have a winner. Plugin limit in Skyrim is 255. The one mod you added broke the camel's back. I'm not sure how the new game started with 256 though... Edit: Actually, thinking about it now, if you included the base game, 256 is the limit. 2^8. Which makes sense, since the new game worked.

Leave them all ticked, same as you were when checking your save games.

Just try a brand new game. Whether you get the "Wild ride" bug for the intro cart ride is irrelevant. If it loads and starts to that point without that error, that will help with the diagnosis.

What happens when you start a new game?

Thanks for the updated version, Ess and Tech! :-)

What is shown in the left and right panes is always for the profile that is open. When you run SKSE from the MO window, the profile that is open will be the profile loaded. Are you sure you didn't remove a mod at any time in that save? That you are only adding a mod?

That error means that you have unticked items in MO. Verify that everything present on that save is ticked. You may have accidentally created a new profile, which means that everything is unticked to start.

The DX9 VRamSizeTest is correct. The advantage of the ENB memory workaround is that it can utilize your system RAM as well as VRAM, so the higher number makes sense...something would be wrong if it was lower than the actual videocard VRAM amount. The value given by the test is limited to 4064MB due to the fact that you are using Windows 10. Windows 8 and up are capped at 4GB of VRAM use in DX9, due to a Microsoft bug that they don't seem in a hurry to fix. However, for VideoMemorySizeMb it looks like you forgot to subtract the amount for background processes based on your OS. Try using 3714 instead. Also, for ReservedMemorySizeMb, did you try turning around 360-degrees in-game until you experienced stutter, per Neo's recommendation? If you can lower this amount without experiencing stutter, it will be beneficial, as that value is VRAM that cannot be used for anything else. Besides that, I am not sure. I didn't even look at the load order, as I am not very familiar with SR:LE.

Lol my mistake. Sorry about that. Your username did look familiar, I just failed to put two and two together. MBL is my autopilot response for CTDs or ILSs if it isn't mentioned in the OP. It could be something such as an incorrect ENB memory setting. It couldn't hurt to post more info such as your enblocal.ini, Skyrim.ini, and SkyrimPrefs.ini. Use spoiler tags if pasting directly in your response. [spoiler]text[/spoiler]

Your memory blocks may be completely filling up. You may need to adjust the values in skse.ini. Try Memory Blocks Log...install it, and then play until you crash. The log will show your current setting (numbers at the top of the log), and you can see what the memory blocks fill to when you crash (the numbers at the very bottom). If the first block fills up, you will crash. Note that MBL will always show 256MB less than what the setting is in skse.ini. (If first block is set to 768, it will show 512, etc.)

I saw this browsing through the SR:LE guide. I am going to add it to my game and I will report back later with my thoughts. This seems like a neat addition, especially because it looks like most options are configurable.

I have edited the topic title to include the author's name.

I have edited the topic title to add the author's name.

I'm guessing because it is closer to vanilla. Using the Dawnguard version instead won't cause any problems, if that is the one you prefer.

Looks like you fell upon the Nexus page before the actual guide. Follow the STEP guide from top to bottom. It will tell you all the steps in order for a proper STEP installation. In the guide, you'll see instructions for both the STEP optimized textures and the vanilla High Res Texture Packs. You will need both. Also, the STEP Compilation is one of the last things installed in the STEP guide, not the first. The list of mods installed in the compilation is on the STEP Wiki page for the compilation, linked to from the main STEP guide.

What ENB are you running? For VideoMemorySizeMb, try using Boris' VRamTestTool, and subtract an amount based on your version of Windows. Instructions here. As it looks like you are using graphical ENB, obviously other settings recommended on that page will be different, but the memory values should be the same. Also, try setting ReservedMemorySizeMb to 512, and reduce from there until you get stuttering. Edit: Also, please keep long strings of text like .ini values in a spoiler tag. Like this: [spoiler]text[/spoiler].

ENBoost may not be set up correctly. Do you get a message in the tip left corner when you first start up Skyrim? What is your enblocal.ini set to?

The mods forum is restricted to one thread per mod, so that all discussion gets preserved. Please post here: https://forum.step-project.com/topic/481-open-cities-skyrim

??? You say above that you only removed SkyTweak and Vividian ENB. Do you mean you added those to the game? Those are not a part of a standard STEP install. If you added graphical ENB such as Vividian, you need to change settings in Skyrim.ini / SkyrimPrefs.ini, enblocal.ini, and re-install a few mods with the correct settings for ENB.

No need to "run" the .exe file. Just make sure you extracted the files to the right place, and configured enblocal.ini per instructions. Whenever you run Skyrim, ENB will work automatically (assuming you're using the files from the "Wrapper" version). You should see some text in the top left corner when Skyrim starts. If following STEP Core, it should say in red something like this (paraphrasing), "ENB Graphics disabled, only using memory settings". That text is the best way to know whether ENB is working.

The performance pack will have less visual quality than the standard pack. Whether you will notice the difference or not...I couldn't tell you.

For enblocal.ini "VideoMemorySizeMb" number, STEP recommends to download Boris' VRamSizeTest tool, and subtract an amount depending on your version of Windows. Instructions on this page. Note that other items on the page will obviously be wrong for you, since you are using graphical ENB, but the memory size values should be the same. Also, ExpandSystemMemoryX64 can be dangerous depending on your SKSE memory block sizes. See this. Use Memory Blocks Log to check if you need to adjust your skse.ini memory blocks. That may also be the cause of your crashes.

Regarding DynDOLOD: I use STEP Extended, which includes the vanilla High Res Texture Packs as well as the STEP Optimized Vanilla Textures. I've questioned in the past whether I needed to have the dummy plugins for the High Res Textures ticked for DynDOLOD generation, and at the time I was given conflicting answers. I was first told that yes, dummy plugins needed to be ticked, as TES5Edit wouldn't load them otherwise. Later, I was told that in fact I did not need them ticked for a pure STEP install, as Sheson had included the relevant High Res files in a DynDOLOD update, and the Unofficial High Res Patch wasn't relevant to LOD generation. Thinking about it now, as the STEP Optimized Vanilla Textures don't have a plugin to begin with, I'm not sure if they are being input into TexGen or not. Alternatively I assume it would be the High Resolution Texture Pack files which Sheson included that would be loaded in place, but I've never really looked too closely at the results. As long as I didn't get an error, I was happy. :-P I should play around a bit with TES5Edit; this is interesting, and it's a good excuse for me to learn more about xEdit (of which I know very little).

Main file comes later in the Patches section of the guide.

Yeah, the performance textures are fine, just a little less quality and a little more performance. PapyrusUtil doesn't matter where it is for priority order (left pane), as long as it is after SKSE.