Nebulous112

Hi Avatarian, Please use spoiler tags for long strings of text, such as mod lists or .ini file copypasta. [spoiler]text[/spoiler]As for your issue, there are definitely a few redundancies, as shaunlewis mentioned. I would trim back to just STEP Extended and add a few at a time, if I were you. Verify that STEP doesn't already have a mod with the same function, and go from there. The more mods you add on top of STEP, the more custom conflict resolution in xEdit you will have to do, as well. Good luck with your build! :-)

Hi Warlocksg, welcome to STEP. Please use spoiler tags to hide long strings of text. Such as: [spoiler]text[/spoiler]Regarding your issue...shaunlewis has a good idea for narrowing down the issue. Personally, I think it is the lack of FNIS that is crashing your game, but I'm not sure. I've always been told it is necessary, or one will crash. I have never played without it. Edit: You can also try installing Memory Blocks Log and seeing what the log says. This will ensure that your SKSE memory settings are correct, as your heap size may be too small.

Hi spizone, welcome to STEP. 1) I usually merge optional files. There are a few exceptions, like the STEP Optimized Vanilla Textures and the STEP Compilation, which are separate mods and should not be merged. See here: https://wiki.step-project.com/Guide:Mod_Organizer#Installing 2) Install the Optimized Vanilla Textures during part 2.D of the guide. Install the STEP Compilation during part 2.N. of the guide.

Good call on waiting. USLEEP 3.02a released...a hotfix for a hotfix. Apparently a few trainers got messed up when the CK saved data for 3.02. Not sure if this affects the patches or not, but just a heads-up.

See the OP in the STEP Compilation thread: https://forum.step-project.com/topic/9370-step-compilation Edit: Ninja'd, but I think the OP of the Compilation thread may be more up-to-date.

The ENB binary has been updated to v0.303. [spoiler=Default v0.303 enblocal.ini][PROXY]EnableProxyLibrary=falseInitProxyFunctions=trueProxyLibrary=other_d3d9.dll [GLOBAL]UsePatchSpeedhackWithoutGraphics=falseUseDefferedRendering=trueIgnoreCreationKit=true [PERFORMANCE]SpeedHack=trueEnableOcclusionCulling=true [MEMORY]ExpandSystemMemoryX64=falseReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=64VideoMemorySizeMb=2000EnableCompression=falseAutodetectVideoMemorySize=false [THREADS]DataSyncMode=1PriorityMode=0 [MULTIHEAD]ForceVideoAdapterIndex=falseVideoAdapterIndex=0 [WINDOW]ForceBorderless=falseForceBorderlessFullscreen=false [ENGINE]ForceAnisotropicFiltering=trueMaxAnisotropy=16ForceLodBias=falseLodBias=0.0AddDisplaySuperSamplingResolutions=falseEnableVSync=falseVSyncSkipNumFrames=0 [LIMITER]WaitBusyRenderer=falseEnableFPSLimit=falseFPSLimit=10.0 [iNPUT]//shiftKeyCombination=16//f12KeyUseEffect=123//homeKeyFPSLimit=36//num / 106KeyShowFPS=106//print screenKeyScreenshot=44//enterKeyEditor=13//f4KeyFreeVRAM=115//BKeyBruteForce=66 [ADAPTIVEQUALITY]Enable=falseQuality=1DesiredFPS=20.0 [ANTIALIASING]EnableEdgeAA=falseEnableTemporalAA=falseEnableSubPixelAA=false [FIX]FixGameBugs=trueFixParallaxBugs=trueFixParallaxTerrain=falseFixAliasedTextures=trueIgnoreInventory=trueFixTintGamma=trueRemoveBlur=falseFixSubSurfaceScattering=trueFixSkyReflection=trueFixCursorVisibility=trueFixLag=false [LONGEXPOSURE]EnableLongExposureMode=falseTime=1.0BlendMax=0.0 As Rebel47 pointed out in the ENBoost 6.0 Anticrash thread, the .ini lines from the Anticrash file are now included in the new version of the ENB binary itself. That is not the only change...EnableCompression is now defaulted to false. EnableCompression=false [THREADS] DataSyncMode=1 PriorityMode=0Regarding the new .ini lines...this is what Boris says on the ENB download page: And this is what he says on the Crash Fix ENBoost Nexus page description (formatting of middle paragraph by me): This tells me that most users should have these fields set to "0", unless trying to load a save that crashes, or trying to get past some really crash-prone area. For STEP, this should not be an issue. :-) Boris goes on to say on the ENBoost Crash fix page: So, it seems like the values for these fields are whole numbers, from 0-2 and 0-4 respectively. There are some recommended numbers for the new fields, and Boris also recommends not to change any values related to threads in Skyrim.ini or SkyrimPrefs.ini. For STEP, I think it's better to recommend just turning these new fields off (just as everyone else said in the other thread)...STEP users shouldn't be crashing all over the place, anyway. ;-) [THREADS] DataSyncMode=0 PriorityMode=0Also, should STEP recommend that compression is turned back on? Or is this better left off by default for STEP (if we assume most have >2GB VRAM)? Again, the previous recommendation with v0.279 was to keep this at the default value (which was "true"), but the default has now changed to "false". EnableCompression=true

It is a separate guide made by Neovalen, hosted on STEP. See here: https://wiki.step-project.com/User:Neovalen/Skyrim_Revisited_-_Legendary_Edition It is unaffiliated with STEP and it doesn't require STEP to be installed first. SR:LE is constantly updating and changing, while STEP takes a more conservative approach to including mods (Lore-friendly only, mod-testing required, etc.). Naturally, SR:LE has a lot more mods than STEP itself. It also includes using Vividian ENB by default. Edit: Edited post to reflect that SR:LE actually is not a STEP pack of any sort. The SR:LE forum is in the STEP Packs forum, which confused me. Thanks for the info, Tech!

Your Memory Blocks log confirms the settings are fine, and your skse.ini and the Memory section of enblocal.ini is fine. The forcesteamloader argument is not necessary for you. It just comes down to what Greg mentioned...you'll never fight 100 enemies at the same time. What Greg is saying is 100% correct. Edit: Didn't see your last comment. I think you are probably just fine!

Try Memory Blocks Log. Install it, and do the test again. You may need to increase the heap size in skse.ini, but the log will tell you.

If I were you, I would go for the full STEP Extended list. Install all textures at STEP baseline, as the difference between 2k and 4k isn't huge, for most things. If you want to kick things up, install an ENB, like Vividian. You will definitely have the FPS room. Or you can also try DynDOLOD on high, but I'm not sure whether that'll be worth it to you.

It'll be quite a long time. It's a far-off goal, not a near one. Pick up STEP now. It's pretty darn good as it is.

USLEEP has been updated to 3.02. A few major regressions slipped in to 3.01, so this is more of a hotfix than a whole new patch version. It looks like they threw in all the other fixes they already had completed, though, so there are a more fixes than just the few regressions. Changelog here.

Nice! A 900-series would be perfect. The more VRAM on the videocard, the better. 2GB on the card is OK, 3 is good, 4 is great. Good luck with your build!

I think you are misunderstanding Grant. FNIS absolutely needs to be run from within MO. Grant is mentioning MO (and therefore FNIS) should be outside of Program Files, because of UAC issues. Same could be said for Steam itself. However, the most important thing is what does FNIS say when you run GenerateFNISforUsers? Do any error messages pop up?

How many years ago did you install STEP? Do you remember what version of the guide it was? I think I understand you are meaning the "High" graphics settings in the Skyrim menu (or from the Skyrim Launcher). I only started with STEP a little over 6 months ago, but the assumption is that graphics would be set to "Ultra" from the Skyrim Launcher, and all the texture mods which STEP adds brings it way past the vanilla Ultra settings. STEP includes an absolute ton of texture mods. You may be OK with just a handful of gameplay mods. However, I wouldn't install any texture mods if I were you. Try a lower resolution, as that makes a huge difference. Try borderless fullscreen, from the ENB settings. Also, you will absolutely need to make the Reserved Memory Size in the ENB settings as small as possible, try 64MB. The 512MB that STEP recommends to try first is literally half of your VRAM (although the purpose of ENBoost is to also use RAM in place of VRAM).

Hi PCNinja, welcome to STEP. I think the main problem is the videocard. I didn't recognize the name, but a quick Google search told me that it is 7 years old (from March 2009), and came with 512MB or 1GB VRAM options. Unfortunately, modding may be out of the question for that system... You can try installing all the lowest quality texture options, etc., but I don't think it will be enough. Honestly, you may be better off uninstalling almost every mod, and just running Skyrim vanilla with USLEEP. Either that, or upgrading the video card. Maybe someone with more experience playing on a lower end system might have some ideas...?

There are non-Immersive Citizens options in the STEP Compilation installer.

Thanks for the info, and the mod update (!), I2edShift. :-) I really look forward to trying Deadly Dragons out (definitely the Loremonger edition for me).

The first sign is much better looking, IMO. I also like the name: Mojave Patch Outpost. Cool stuff, Ess.

Legacy is basically a DLC-sized mod. It includes a ton of other mods, some of which are already in SR:LE. There will be major compatibility issues, unless a lot of CR work is done and some swapping of mods. Check the articles tab on the Legacy Nexus page. Cccow got a fairly decent build on (mostly STEP Extended, some SR:LE mods), and there is info on the CR methods he took. However, this was before v15, Legacy's biggest update ever. So you probably would have to start from scratch. That being said, I absolutely love the look of Legacy, so in the next month or two I may try and have a go at the CR. My skills are lacking though, so we will see. It would be an awesome pack, if it could actually happen. But so much would have to be changed that it would probably have to be a pack on it's own.

I'm pretty sure NetImmerse Override is included in RaceMenu. XPMSE requires it as well, but RaceMenu was all I needed for it.

I haven't messed about with Merge Plugins much, but GamerPoets did put out an awesome tutorial video. Not sure if you've seen it or not, but if you havent: https://forum.step-project.com/topic/9845-gamerpoets-merge-plugins-video-tutorial/

Sheson just updated DynDOLOD to v1.47. It looks like the new version requires the xEdit 3.13 Experimental version. Should the link to xEdit in the TES5Edit wiki page be changed to the Experimental Version? https://www.nexusmods.com/fallout4/mods/2737/? Also, I noticed the link to TES5Edit on the DynDOLOD wiki page is quite outdated, it currently points to the TES5Edit 3.11 GitHub page. Lastly, I noticed Sheson introduced a new feature that affects Lanterns of Skyrim. From the manual: Is this something STEP should recommend?

I always search for the mod in the search bar, which will bring it up. If I want to see it juxtaposed with the other mods, I note the priority number and exit the search, then scroll to the position. Same deal with the search bar in the right pane, for plugins or downloads.

Can't distribute stuff without the author's consent, unfortunately. If the author(s) give consent, that would be fantastic. Definite time saver, for sure. Like the STEP Compilation for Skyrim. Edit: Lengthened response.