TechAngel85

I would just use the older binary. This should be reported to Boris at enbdev.

It's usually set in the video card driver's.

So you're only crashing with ENBSeries installed? No crashes when it's not installed? Is there a reason Deferred Rendering is off?

Turn off transparency AA.

If you don't know what you're doing, you probably should be doing it, but there's no other way to learn. :: When you open xEdit and load all your plugins, you can right-click on a plugin and choose "Apply Filter for conflict Losers". This will show you what records are conflicting with one another. This is where the advanced part comes into play, because some conflicts are desired and others are not. Knowing the difference takes time and effort. Those that are not desired should be forwarded into a custom patch. You can do this by right-clicking a record and choosing "Copy as Override into...". Then scroll down to the bottom and select "". Give it a name and you're done. Copy all undesired conflicts into this new plugin. This means you'll "Copy as override into..." and then select the plugin that you created for all other records being forwarded. This is really not something that noobies jump into, but if you're willing to learn it's how you're going to get a custom setup that is actually conflict free and stable.

No, not merge. Just check for conflicts between your mods to see if you need to make a patch. It's not complete but here is a pretty good start of a how to use xEdit: https://wiki.step-project.com/Guide:XEdit

Did you run LOOT? You have a lot of mods that I'm unfamiliar with. I would suggest you opening xEdit and check for issues in your load order. It's quite possible you may need to make a custom patch for your install. I'm moving this support to a more appropriate support forum so that it may receive some more attention as this really isn't an issue with STEP.

Yes, that is correct for deactivating dummy plugins and activating all archives at the end of the Guide. The instruction to make the switch is at the end of the Guide (section O). Yes, just make sure the patches are installed directly below. LOOT is only going to alter your plugin order (right pane), not your mod order (left pane).

Are you using an ENB or just ENBoost?

Next, verify your game's local cache using Steam. This will ensure all the files are as they should be. I should have added that above, but forgot about it. Also post your enblocal.ini file.

No, don't untick it yet. That was an instruction we missed. Leave all the dummy plugins ticked until the end of the Guide. This is necessary for running DynDOLOD in the Patches section. I've removed the instruction from the UHRP mod page. You won't be asked if you renamed the patch files when you install them. Mods downloaded from the same Nexus page will attempt to install using the same mod name. In case of ICH, the update file would have tried to install as the same mod name as the ICH file did. This will produce a window that allows you to choose how to install the file. Merging the file only overwrites conflicting files. Replace will delete all the files in the installed mod and replace them with the files in the update file. This is undesired in this case since we want the update file to overwrite the files already contained in the mod. If you rename the patches and install them as separate mods, be sure they are listed below their parent files. Yes. Users who are installing the entire Guide and will be installing the STEP Extended Patch (found in the STEP Compilation mod in section N), can move the plugin to "Optional ESPs". This is done by double-clicking on a mod in the left pane, going to the "Optional ESPs" tab, clicking the plugin in the bottom plane, and move it up to the top pane using the arrow button. This prevents MO from listing the plugin on the plugins tab in MO. Plugins listed in "Optional ESPs" will not be loaded by the game.

How big of a drive are we talking about here? Scratch that. It doesn't matter. I'm gong to assume you know what you are doing and make this simple rather than detailed... Just use Ubuntu and burn a DVD or use a USB stick. Then make sure your BIOS is set to post from the DVD drive or bootable from USB (first boot device). Pop in that DVD or stick and press the key to boot to it. Once it's loaded, choose your language and then select "Try Ubuntu", rather than installing it. You'll have a fully working version of linux running. It should detect your drive. Just open the drive and copy the files to the new partition. Once it's finished, and shut down Ubuntu and boot into Windows 7 to find your files neatly copied over. ::

I don't recommend downloading any save games onto your computer regardless of source. STEP recommends a new game for first builds. First, run a malware scan just to be safe. If you're unsure on how to do this I recommend you download and install SUPERAntiSpyware (the page looks sketchy but it's legitimate). Some recommend MalwareBytes, in the end they're about the same, but as a tech I've always used SUPERAntiSpyware. Whichever you choose, don't buy it. Just download it, install it, run it, uninstall it. Next, make sure your antivirus isn't blocking any of the processes (like enbhost.exe, tesv.exe, ect) and then make sure it's not blocking any of the DLL files (d3d9.dll, skse_steam_loader.dll, ect). Now, turn off papyrus logging. It's eats a lot of disk I/O. It's not useful unless your troubleshooting scripts and most of the message are only helpful to the script authors. Now close MO and then download and run BethINI. Select your profile for MO. Once the main menu opens, select the "Default" preset and then select the "High" preset. At this time, don't change anything other than making sure "Grass Diversity" on the "Foliage" tab is set to "7". This gets the basics out of the the way so try your game to see if there is any improvement.

As Greg was speaking about, the STEP Guide is made to be flexible to the immediate and advanced modders while still being fairly easy for newer modders who've taken the time to learn some of the basics. Most newer modders just follow the Guide as is. This is fine and it's the most well tested method. More advanced modders will realize they can do things like install the newer version of SFO, as long as they grab the right billboards for DynDOLOD, use Verdant instead of SFO's grass, so on and so forth. However, for newer modders we do recommend they complete the Guide and confirm a stable game before adding other mods on top.

Are you using any mods that change the weathers or clouds and fogs?

You can install the ENB features along with STEP. There are only a few, such as RWT has a version for ENB. This will only be textures and will not hurt your STEP install. Depends on the screen resolution you're playing at. In most cases, there is no need to install 4K textures since you can't even see the extra detail unless you're right up on the texture. I also want to note that simply because you have the latest video cards doesn't mean you can go out and install all the high-res textures you want. High resolution textures will affect VRAM more than processing power so keep this in mind. 2K should be good for the major of systems. No, just run BethINI. The INI section will be replaced by BethINI in the next release. ENBoost is a utility that 9/10 times, should always be ran on a fully modded system. If you're testing your build as you're building it, you're likely going to need ENBoost to be there. That is personal choice. I prefer manual because I have full control over the files rather than relying on a program that may or may not have bugs. ENB management is not hard. I see ENB manages only useful for those that are switching back and forth between ENBs a lot, not for those that are installing one ENB and sticking with it. Keep in mind that if you're going to install an ENB Preset then there are a couple changes to make to the enblocal.ini file.Your system is similar to mine so there aren't any special things to consider when installing STEP. STEP has been designed to work on the widest range of systems possible. In most cases, as long as you meet the CPU and GPU requirements, then you're good to go.

I'm running out of ideas. Delete your enbseries.ini and your enbseries folder (if there is one) and then run the game to generate a new file.

Not installing Skyrim Enhanced Camera wouldn't have caused this. I'm not familiar with Crash Fixes myself, so I don't know if it has any settings to do with lighting. You shouldn't have been getting any crashes though from STEP. That's a bit of a flag right there. Do you have any missing master errors? I'm guessing you ran LOOT? Did you install the right version of ELE? Did you do any changes in the video drivers other than what's listed in the Guide? Do you have the STEP Patch plugin installed and active? What version of Windows are you running? Do you have MO managing the archives from the Archive tab in MO? Are all the archives checked? Did your Batched Patch run without errors? I'm just reaching for that "ah ha!" moment since I've never before seen this issue produced from a STEP build.

STEP is not designed for the absolute noob. We expect users to have the basics of modding and the tools used for modding. However, we're always willing to help. I'm just going to try to get a baseline on where to start troubleshooting by asking for the basic information we'll need to help. Did you test by running your game periodically while installing the Guide? Did you install all of STEP or did you skip any mods in the Guide? If you skipped mods, please list them. Did you install any mods that weren't in the Guide? If so, what are they? Please post your: Skyrim.ini (from your profile in MO, not the game default one)SkyrimPrefs.ini (also from your profile in MO, not the game default one)enblocal.iniYou can post them in spoiler tags by using the third icon to the right on the top formatting bar.

You don't have any other mods? You're lighting is definitely off. Make sure you're gamma is at 1.0 and you're in-game brightness setting isn't too high.

If you're wanting to use an ENB Preset you need to change this: UsePatchSpeedhackWithoutGraphics=true UseDefferedRendering=false to this: UsePatchSpeedhackWithoutGraphics=false UseDefferedRendering=true

Can you post your enblocal.ini?

I agree with Kesta, the other bodies of water aren't large enough to notice the LOD bug, that includes the marshes. Most of the marsh is so hilly that you can't really see the water LOD anyway. The only other large body of water that you might want to keep as ocean water is the lake at Riften. This one is often covered by fog enough that it can't be seen but during certain weathers, I think I can be. Especially when playing with a weather mod like Vivid Weathers or CoT that is going to put more weather variety in the area. I haven't played much in the Riften area this playthrough, though, so I'll have to check it out some more to see if the LOD bug is present there.

You answered your question yourself here. "Who knows?" I have no idea what the extent of the changes to the water for SSE are going to be. All I know is there will be "new water shaders". I'm assuming it's going to be similar to FO4's water since it's going to be about the same engine running it. No, no. Not two versions. Just one version with world edits to only specific areas. Oceans and Lake can have the same water. Ponds, streams, puddles, rivers, etc would have their own water. This way you still avoid the LOD bug on the big lakes, but the smaller bodies of water are more custom. For me it's about immersion and realism. Without arguing the points of realism in a fantasy game, we pull our ideas of how things should work and look from real life. Water in a game should look and act like water in real life because that is our expectation when we see water in a game. Achieving this turns into "it's not what you notice, but rather "it's what you don't notice". RWT's Riften edit is the perfect example of this type of thing. Do I notice it? No, not really. But that's kind of the point isn't it? The water in the canal should have little to no movement in it due to how it's sheltered from the environment besides maybe a small breeze from time to time. That would be our expectation for that body of water due to real life experiences. Therefore, RWT's version of this is believable to the point that you don't really even notice it unless you go looking for it. What this means is that author has done their job of making water "immersive" to the point that players are drawn into their game rather than being distracted by the unnatural looking water. This is what the goal of most texture mods should be, imo. Not to be noticed, but rather to not be noticed. I hope that clears some things up. Clear as mud, I'm sure. :: No, I do remember something about it. Also, the speed that the water falls looks weird. The water textures make it look like a good amount of water is flowing over them, but the water is falling too slow for that volume of water. It's just one of those distracting things I was talking about above. It's not something that I should notice unless I look for it, but it changes my eye when the camera moves past the effect. I'm glad you mentioned PW waterfalls, because I think they look pretty sweet too. They're probably among the best falls out of all the mods. I just don't care for the calmness of the rest of the waters included. Nor especially for what it does to the shoreline in some weathers (ENBs tends to fix this though).

Why not provide the best of both if you are divided? Keep the big lakes as the ocean water to help avoid the LOD bug, but edit the smaller bodies like ponds. In my honest opinion, I don't feel compatibility is really an issue anymore. We don't see as many posts on the support forums about patching and mod compatibility as we used to. That tells me that either more users are learning and getting used to patching their games or more mod authors are providing patches. My feelings on the LOD bug is that it's never really bothered me that much. You tend to ignore it after several levels of playing.