Aiyen

You can use any ENB version for any preset.. but if one is made for a different version it will not look as the author intended since certain features etc might be disabled. Same goes the other way.. if you try to use one made without newer features and those become enabled then it will also look off, since the default values are almost never a good match. Also the older the versions the more bugs and lack of optimization is present.

Wooo feedback! :) Yes interiors are getting a major overhaul for the next update... was just not good in a rather large amount of locations. The bloom was a bit too intense which caused washout of the details. But found an .... error in my shader which I just fixed. And already things are a little better overall I think. Halde: The default settings are set for the best performance/quality ratio ENB can bring. If you want more performance then that then you are going to have to disable effects manually specifically SSAO. I have not tested interiors without ELE image spaces installed as a minimum, but feel free to try out just using without. Also both the description page and the installation guide says to always get the latest version unless otherwise stated! 261 will work just fine at least I am using it atm. Edit: Ever since Gopher did a review ages ago where he somehow managed to read "Will not work well with ENB versions before 236" as ... use v.236" which then caused everything to just look wrong I only explicitly say that people should use the latest version! :)

While I agree with most of what you are saying then I also think that we at some point is going to have to think about being user friendly. Monitor calibration is almost an art in itself since it highly depends on the monitor type in question.. as well as the locale that said monitor is in. There is no point in calibrating a monitor in pitch black if your general lighting while you use the monitor is always going to be entirely different from this. Just because you have the best settings in the dark does not mean it is the best settings during other scenarios. Lagom is a great guide and most who do a quick search for monitor calibration will find it. However it is like the name says for LCD monitor, people with other panel types will get different results. (I know this since I am on a 99% perfect factory calibrated IPS panel and it does not agree entirely with all of the lagom tests anymore.) It would perhaps be worth it to mention Spyder, but people who are that into it most likely are going to buy a proper monitor to begin with. At least I like to think that any color enthusiast would know not to just get the most cheap panel on the market and expect it to be able to compete with the more (much more) expensive and detailed models. Another issue that many people have is that they are not aware that their monitor have some weird profile enabled which is most likely going to skew the results of any test since they are focused on highlighting something else. Also most new monitors have multiple profiles which each are aimed at something different. Movie viewing profiles are rather popular since the shift in the color spectrum and contrast can really help make movie details look better. However they are not good for gaming. Oh well enough ranting. I guess we will have to look over that particular part of the guide again since it could most certainly be better!

So another fullscreen/window mode annoyance... good to know and nice catch!

Looking around sounds like you have mouse acceleration on .. which does just that. Also as for the lag.. does this happen without any mods ? Almost all types of lag, stuttering, etc. is always due to there being too little bandwidth in your hardware to handle the texture, mesh, extra object details you are asking of it. As for ini changes, then try to set all the resolutions to just 1024 and then see if it helps. It is the main performance related set of entries in the ini files.

So would the better solution not be to alter the vanilla meshes with proper ones then ? It is not like the change would be globally bad... assuming the meshes have all the proper values.

So you are saying it does not happen if you run... but only when you walk ? That would be a first

I believe that the physical used is the only one that really matters.. since as I understood it then that is what the game + enbhost is actively using at any one point. I have never seen a use higher then this on my system (16Gb RAM, 2Gb VRAM ).... I have seen that the game and ENB reserve more (Your system commit), but I assume this is simply buffer which just helps speed up loading. (Which is in fact what I see... once the game is loaded up into memory it will start up a whole lot faster then when loading the first time.). Which also makes sense.. if there is plenty of free physical memory available then there is no need to clear up memory for new data. Hence I have never seen a need to go higher then 8192 in memoryreserved.. since that is the max used ever... even when the value was set higher. I have not been able to go much higher since then I get into the area where the VRAM becomes the limiting factor and loading on more 4k textures start to really increase load time and eventually just CTD the game. But yeah ENB can give you much... assuming you have hardware with the bandwidth to support it.

in /textures/landscape/grass or /textures/plants. They will all have tundra in the name.

I remember trying out the switch but found it just too annoying.. when playing on larger monitors you really notice drops to lower resolutions quite a bit. Also since it apparently still does not have proper support for the latest ENB versions then it is just not attractive at all... ENB offers too much in comparison. Some people seem to make it work if only ENBoost is active however... which is something I guess. But well if you want parallax or shadow fixes as well then you need the graphics part and then its a no go from what I understand.

There are quite a few issues with vanilla water, since it was never high on the priority list of stuff to do... like in Oblivion. You already found the mod that I was thinking of would solve it. Also there is DoF in the game by default. Already in the Into they make heavy use of this and other blur effects. This is also what the mod dynavision utilize to get DoF without using other post processing software. Anyways.. I digress again.

What are your shadow resolution settings in the ini ? This is normally what cause issues with lighting.

Are you running anything like precision X, rivertuner, or any other OC/monitor software. If you are then disable them, and then it should hopefully work. When ENB entirely fails to load up then it is almost always because some other program is being injected, or because of some safety setting in windows that prevents it.

When you first start in the intro... then you can sometimes hear a "thump" sound from all the stuff falling down after it is spawned during the first few seconds of black screen before you can see anything. Since there is a drop there is physics calculations being done... If they are going crazy then all sorts of weird stuff can happen. Also as the carts are moving around they do some tiny bumps etc.. which I guess it also picks up. Not pure science.. but that is how I imagine it is going on.

The helmets have bad/lacking mesh settings which cause them to not display properly. Here is an illustration. The current one in the mod is on the left and a working one on the right. This happened because the author converted his new mesh back to a nif file and that converter did not do it right. Hence the helmets will be much brigter ingame, and will really stand out when you compare them to the armor and to helmets on the ground etc.

Okay I was mistaken It also disables the GUI.... Guess it sort of makes sense that he would do it like that. Good to learn by failing in forums! :D Guess if you want VRAM showing etc you will need to get performance monitor

Even with only ENBoost the GUI should work.. it is a hardcoded feature of the d3d9.dll that makes all of ENB happen to begin with.

If you cannot open the GUI (graphical user interface) of ENB then it is not working properly. Shift + Enter will open it up by default with default enblocal.ini files. Once there you can find a tab called statistics and profiler which has all that info. Also you could have just posted this in the previous thread :)

Okay update time is near! :o The next major update is underway... I have currently more or less finished overhauling the interiors in terms of bloom, since it was just too inconsistent as it was. Also I have added a new weather group for CoT since it had a selection of clear weahers that just had too many visual artifacts with the sun relative to the majority. Also finished up a weather for blackreach. Currently I am in the process of making my own DoF shader... since I have realized that the general image when using skylight is a bit of a mess between the soft glow of the bloom and the super sharpness of not having it. A faint DoF would help smooth out those differences a bit. Ofc. it is going to be super performance freindly and not really as fancy and advanced as some of the others out there, since I essentially only want a really faint blur on the parts not in focus to help smooth out the transitions, and fix a few flickering issues with the bloom (That are sadly outside of my scope to fix other then reducing intensity which would remove the effect entirely.) I am also in the process of making all the fancy stuff for the description page so that it will finally look attractive. Trying to make some screenarcher screenshots etc. Since it is my impression that a lot of people check out the page, but not that many download it. Guessing they just look at the shots and then move on! So I want to do something about that. That was it for now! If anyone has any further suggestions then I am all ears! Other then that, then have a good day!

Screenshots and the relevant load orders etc. please

Yes it will always auto generate when ENB launches with the default values.

Okay going to make a little announcement for this one. Since the mod actually have some issues with helments you are wearing not having any normal maps applied and excessive reflections and specular then I went ahead and investigated in order to find a solution. The issue is that when he made the new meshes then his nif converter did not put all the proper settings back on, and he also carried over some white vertex colors. These in combination prevents the shader from applying the normal map to the helmets, which cause them to just look... bad and almost glow due to really high specular and reflective properties. I have sent the solution to the author, but he has so far not responded... so if he dont in the near future I will just finish up the rest of his helmets and upload the meshes here for people to grab in the mean time.

Sure here ya go https://www.dropbox.com/s/tve11wmvzejyw87/ModOrganizerWorking.txt

It wont... since everyone have different systems with different chips and overall bandwidth. for example a laptop can have 2Gb memory.. but a really low bandwidth hence you will most likely not be able to get away with what a desktop based 2Gb card can do anyways. Hence when you push the values to the limit you will run into massive stuttering issues CTD´s etc.

Well it can only be one of three settings you need to enable/disable.. Normally when you have your driver set to application controlled then it will be the setting in enblocal.ini that decides if you have vsync on or not. Followed by whatever you have in your .ini since ENB should overwrite that.