z929669

Just use this (I recommend using SMAA, but change EnableProxyLibrary=false if you don't and please don't use any other proxy for the time being). The guide does not define every setting, and I suppose it is possible that your iteration of the file may have some slight differences. If you still get the crashes, then either one of your other setup parameters is different from what we recommend, or there are settings or environment diffs in your setup that we are not accounting for. enblocal.ini

We are working to arrive at a consensus. So far, there is no solid evidence either way, so we will need to systematically test the effects of all of these settings. For the moment, I would go with Tech's advice, since setting iPresentInterval=1 is the most prevalent advice from various sources. We will update the guide accordingly unless someone presents evidence that turning on this feature interferes with ENB vsync. I will look into it at some point, but as I said, I recall that turning this feature on was detrimental to my setup at one point ... but there are three potentially interacting mechanisms here, and I do not remember the details of my findings (just that I wrote the current STEP recommendations based on my rather extensive testing ... notes would have been really helpful though!): Driver vsync/AA/AF settingsENB vsync/AA/AF (other?) setting(s)SkyrimPrefs.ini vsync/AA/AF settings

ditto to last post

Hardware system busexpansion cardsdisplay adapterslots of other stuff software: drivers (tons of them)services (tons of them)There are literally thousands of differences in each system, and many of these variations can affect other things indirectly. You are simplifying too much, and this is why one prescriptive will not work for everyone, especially considering that we are talking about a custom app that plays around with Windows memory management (not just vsync). All of this may or may not be related to whether or not ENB settings and INI settings have same effects across systems. EDIT: and I did not even mention sortware/firmware versioning diffs and interactions. EDIT2: in my personal testing iPresentInterval did have an impact on performance relating to vsync, stutter and FPS. This impact may have been due to combinations of other settings or it may have been due to my own unique system (or perhaps I had not exhausted all possibilities or sources of variation). There is no consensus on whether or not that INI setting is even a little important, because there are likely other variables in play.

... and Chrome has some issues that other browsers don't have. Firefox is probably the most trouble-free browser, and it has a ton of functionality beyond that offered by Chrome I think (via add-ons)

Agree that Boris' info may be outdated, but there are so many variations of hardware and software that I think even Boris will not always know all outcomes and behaviors. this is why we may want to develop a flow chart beginning with 'best' recommendationsverification of functionality'best' alternativeverification of functionalityyada-yadaNothing too complicated, but a simple method of landing on the best possible solution for all users, regardless of hardware/software.

What browser? What are your Edit Preferences? From the page history, all of your edits look normal and fine, so I am thinking that you are having some kind of an issue that may be related to your preferences and/or your browser such that you are not getting the page refresh ... if you close the site and re-open, do you see your edits? Also, give your edits some time. Some pages are quite large, so give them plenty of time to save and refresh. Headertabs could be an issue as well ...

iPresentInterval on negates the ENB vsync behavior as I recall, but this post (and following) has some useful info for investigation to confirm. I'll put it on my to-do list. Unfortunately, this kind of thing is really hardware (and software) specific, so I think we may need to offer up (by updating the STEP guide) a couple of different viable scenarios for users to cycle through to settle on a "best fit" for almost any user. ... but I need more Nvidia feedback like we have here. AMD drivers/software do not dominate control as I recall, because I run with iPresentInterval=0 and ENB vsync=true and AMD vsync forced off, and my FPS are effectively limited (see specs in sig).

Details of behavior for AMD users are well covered in the STEP guide, including the AA and AF behavior (I tested ENBoost extensively under AMD CCC and wrote those instructions), but I never had much input from Nvidia users, so now is better than never ... ... details?

I cannot verify (AMD user here) that NVIDIA Inspector vsync settings have any influence on ENB vsync. (what is Control Panel?) Can anyone corroborate that this is the case? How do you know that ENB vsync is not working?

OK, I have to chime in again at this point after now realizing that you had set VideoMemorySizeMb=16384 (!) ... you told enbhost.exe to take all available memory regardless of the requirements of all other competing processes (at least that's what we think). Rule #1: Don't go changing INI settings for ENB, SKSE or even Skyrim based on any information you get on some forum ... We have defined all of the recommended INI settings --that should even be considered-- in the STEP guide. Other guides on this site similarly define settings that can be changed and what they should be changed to. Don't experiment or take any advice from those who spout off recommendations outside the context of a well tested guide like STEP or Skyrim Revisited et al. ... if you DO, then please, please post such details in your posts for assistance.Rule #2: Never forget Rule #1!Now, in the OP, you mentioned that you followed the STEP Guide ... I respectfully disagree ;) ... if you had, then your game would very likely be running without said errors Persons wanting to install a guided mod build and play the game: I don't understand why these people don't follow the advice we have outlined in the guide based on thousands of man hours of testing and input from very reliable sources in the modding community (and even that input is not totally trusted prior to validating ourselves). The vast majority of modding "problems" that people post about are a result of not following the guide(s). My advice? Please consider the following: Uninstall everything related to Skyrim (including Steam) go the the STEP wiki guide (or one of the other mature guides on this site), carefully read it and follow all advice exactly Don't do anything extra that is not explicitly directed in the guide and associated notes Don't skip anything you think seems unnecessary that is explicitly stated in the guide and associated notes Be sure to follow links within the STEP guide to the ancillary guides and mod pages Unless you already know everything, read everything!! Report anything incomplete, confusing, or suspect about the guide in the bug thread (this helps us to improve the guide) Play and have fun or use the valuable lessons learned by taking the preceding advice to tweak to your heart's content --and report your findings ;)EDIT: This post addresses only those persons that are trying to mod the game to play the game and not those persons that just want to tweak and test the limits (but this latter group will almost never post for help, because they generally know full well what craziness they are toying with at any given time, causing their game or their box to "blow up")

s4n will need to address then.

Yes, I saw that, but assumed it was from Improved Combat Sounds.

My guess is that any future updates will not change the installer, and I would wager that it is stable enough now at 3.6. The patch should get updated I would guess. Need to check if EBT plugin is a master for the STEP patch. EDIT: Extended Patch does not require any of the EBT plugins, and the Patch instructions do not mention any EBT plugins, so the current patches seem unaffected by the EBT update.

If you use the default values for SKSE.ini and the STEP-recommended ENBoost setup, you should be good. With your RAM, you could set SKSE memory settings to 1024/512 (I do; default is 768/256 I think). This probably does need to go up just one step under a very taxing VRAM load.

you have plenty of RAM then, and the default SKSE settings should be fine. The checkerboard thing makes me wonder if you don't have some GPU (or other hardware) compatibility issue. Very hard to say. Definitely something to Google or go onto the ENB forums to investigate.

I dropped everything and fixed :P EBT notes updated

OK, thanks for confirming. That makes it easy. I am not in a position to install it right now, would you or someone want to provide the detailed instructions for installing analogous to the OP? I am not sure what the option names and order of selection are in the FOMOD.

Did you follow the STEP guide? If you do, then all of the instructions tell you exactly what to do. If the guide and related info do not provide necessary details, please report in support area or on the bug thread. If more general issues not relating to STEP, then you should post under Skyrim forum or General support. In other words, please only ask for help with a specific mod build once you have followed the relevant guide (or if the relevant guide fails to provide specific info needed). Otherwise, post in Skyrim forums (or general support) to see if you can fish for general modding help.

I mentioned disabling the previous for suspicions that SKSE mem patch 3.0 and/or enbhost.exe causing some issue with TESV.exe. My guess is that's it and maybe try changing the mempatch settings (assuming default now?) in SKSE (with and without ENB memory fixes running). How much RAM do you have?

I would just install 3.6 using default options for now or just disable until we have more info if you want.

Try disabling ENB and SKSE to see if that resolves the error (just checking for source)

Moved Enhanced Blood Textures thread from F - Conflicting Graphics to proper subforum. I did not update the notes though. Still need to verify source options. EDIT: it looks like the mod has been updated to 3.6: No mention of DLC compat or Blurry Screen Blood option, so this will need to be tested again for 'best' config for STEP. EDIT2: I posted on the Nexus thread asking for some detail regarding the missing options.

Download the optimized textures from STEP or Tony671 on the Nexus. There is no need to use DDSopt on the vanilla textures any longer. If you just want to learn how to use DDSopt, use it for custom work or mods that need it.

No worries. I will trust you guys. Just mentioning that the screens were all far distance and that there may be more to it than that. Vanilla Mountains undoubtedly has the better normals anyway.