Aiyen

phazer : Only 1440p on my 660 GTX 2Gb... with 25-30 avg FPS in most locations. Some heavily forested ones go down to 20. On 1080p then it is 40-50 more or less consistently. The TI is a better card so it should be able to perform better. Transition issues are tricky, since it is most likely due to how stuff is loaded or how much is loaded. I would first try the disable/enable ENB to see if it is an ENB effect that cause the slowdown or if it is just generic skyrim. Depending on your shadow and grass ini settings then ENB shadows can cause these huge slow down during transitions. Also like root says.. do not accidentally press the limiter keys! :) Ofc. it is also a good idea to just check using only the default ENB files.

Wrapper is always what you want to use if possible. The Injector is there to solve a few compatibility issues with other 3rd party software that some people like to run with. So if wrapper fails then try the injector. And if that fails you most likely have something else preventing .dll hooking from happening in general. NLA comes with its own weather .esp hence why it is not compatible with other weathers mods without patching. ENB helper is most often included in presets that require it...it is mainly required for making multiple weathers functions and time of day functions work. There is not really any downside to having it on even if a preset does not use it. But in general you should always clear out the enbseries folder when you change preset so best to just delete it if you change to a preset that does not use it.

Scaling should not be an issue.. at least it is not an issue up till 1600p and from what I have heard about people who do multi monitor setups then it is still able to scale nicely. Main issue is ofc. performance...

The guides are in the download section. As for he fps drop... then this have been an issue for years as I recall with nobody really figuring out why. Most often it tends to be related to using windowed mode mods etc. at least that is what I recall. I have not heard about the issue for a long time so kinda thought it had phased out or people found ways to deal with it.

You should only ever have one bashed patch.

Process of elimination ?

There is always an ini file uses... all ini files should have the same interior values on everything or you will experience issues with interiors suddenly looking off. When you open the weathers tab you will be able to see the name of the .ini file currently used. If you where in an exterior cell and then went inside the weather still works. However during certain dungeons there aint any weather, and the ini file reverts to use enbseries.ini values. Also as long as you follow the SRLE guide then you can disregard what mangaclub says about Relighting skyrim and ELFX. The reason both are used in SRLE is because ELFX does not cover everywhere.. and Relighting skyrim does. However Relighting skyrim only affects all the locations that ELFX does not. When you throw ELE on top then you have every single interior handled, and you really only need to make sure a few locations look good and you can be sure they all will.

Simple... when weather system is enabled then the values under Environment is set for each individual weather .ini. And in the case of vividan.. there are a lot of them! :) The reason it works when you disable the helper is because then you disable the weather system part of ENB. You go to the weathers tab of ENB and then you adjust the Environment values there for one weather.. then you can go out of game and adjust it in notepad for all the rest. The reason you need to do it for all the rest is because weathers are also used for interiors. Hope that helps.

So at this point it is most likely some weird issue when you have too many proxy things going on at the same time. I am not sure how shadowplay does its thing, but I guess it also does some directx calls to capture screen frames for recordings. I guess this would be something worth asking about on the nvidia support forums for shadowplay. Just curious that MO have any influence at all...

Yes I did read the OP. If you say you have constant load after you close MO then which process is this load attributed to ? The GPU or CPU does not just run at 100% without some process calling for it, and you should be able to look at your running processes afterwards to figure out which. That said then good thing that you had a second card to test with. Guess that more or less exclude bad memory on the cards. I would be most inclined to suspect shadowplay at this point. Does this still happen if shadowplay is entirely disabled ?

Verify that the given profile is actually used ingame.. you can try to force AA and then start the game. If ENB acts up and says deffered rendering is disabled then the profile works. If it does not then something is wrong with a settings somewhere in the inspector. Try to force it though the global profile since there it should work without a doubt. If it still does not then just get rid of inspector and use the control panel. Unless you play many many different games that absolutely cannot play on the same settings then there is not much point in using the inspector anyways. At least I have yet to see a compelling reason to use it at all.

Glad that you found some color settings you enjoy. As for the effect... then it is there.. but not on every single shadow. And in general I have made sure the effect is not super strong since it would get really annoying if it triggers for every little shadow. However if you really want it to trigger then the most easy way is to just enable skylighting. It will cost 15% performance give or take, and there will be certain locations where you will have a few brightness bugs... mainly in the form of the screen getting really really bright at certain angles. The more difficult way is to adjust the Toe Numerator and Denominator (Under enbeffect.fx shader in the GUI ) to make low brightness pixels even darker... This effectively increases the contrast but you can fine tune it until you have the shadow intensity you want. You can also adjust the AdaptationSensitivity under Adaptation in enbseries.ini... this values determine when the effect will trigger. Hence you can make adaptation trigger on smaller shadows. These are the most "easy" way of doing it, and if you play a little bit with it you will be able to get adaptation kicking in as much or as little as you want it too. By default I have just made sure it is not as overwhelming as in pure vanilla since many people including myself find that rather annoying. Hope that helps more... If you want more indepth details just let me know!

Driver settings is the only thing that can override ENB.. assuming you do not have any other weird 3rd party software that controls drivers or directx features installed. As long as your driver settings are set to application controlled then ENB´s value should be used if enabled.

You want the meshes from this mod... since the gems are the main attraction. The reason they differ is because of different shader settings on those specific parts of the meshes. In general if a mod you want to use offers meshes you always want the meshes from the mod to win any conflict or they wont be used ingame.

You should sort your mod list before creating the bashed patch. Since the mod order does matter when creating the leveled lists. As I understand the LOOT rules then you just need to set them up as the mods say and let LOOT sort your list and then create your bashed patch as I outlined above. I just assumed that you already had a sorted list to work on! So sorry about not mentioning that earlier. Hope that it is clear now.

As I recall it then all you need to do is the following Run WB which will create the bashed patch .esp for ya. (as I recall.. it has been over a year since I did a fresh install last someone correct me if I am wrong!) Right click it and select rebuild patch. Just use the settings it suggest and create the patch. This is what you do every time you add a new .esp until you are experienced enough to know when to not do it. All the other stuff is just technical stuff for the people who really want to understand what is going on under the hood.

In cases of constant load you should be able to locate which processes are using the resources, and hence failing to shutdown properly. Also the fact that you get graphical artifacts most like means that it is a video memory issue on your card. I would RMA it now since even running at full peak capacity there should not be any graphical artifacts of that type.

For by far most users the only thing they need to change is the VideoMemorySize and ReservedMemorysize. Autodetect will always put in your VRAM amount since that is what you should use as a baseline value. Is it the best and most optimal value? Perhaps not since it depends on how much total memory you have to throw at the game. If you have 12Gb+ RAM you can use values for videomemorysize up to 8Gb. if you got more you can increase it further but not much point since it is almost impossible to get skyrim to use much more without starting to getting massive slowdowns due to bandwidth issues anyways. The reservedmemorysize is either 256 or 512 for just about all computers. If one does not work try the other. As for all the rest.. unless you start getting performance drops during panning the camera or during transitions you do not need to worry about changing them from the nexus default value for your card. In general the values suggested to you are a very good starting point. As you add more stuff to your game and you start getting into CTD and slowdown issues you can return and try to change the values. Hope that helps otherwise just ask which parts you want clarified.

Yes you only create one for every mod list. The easy way to think of the bashed patch is the following. You have mod A and B. Both add new items to the game. Mod A´s .esp is earlier then mod B. In this case only the changes of Mod B would be visible in the game since it is later in the load order. Now what the bashed patch does is to take the changes from mod A and B and create a new .esp that makes sure that the items from both mods are in the game. A more technical way of saying it is that the bashed patch makes sure your leveled lists contain all the items from your mod list.. so they all appear ingame. It can also contain other things.. but 95% of what it does is making sure the leveled lists contain everything. Since it is a patch then you only need to remake it if mods contain an .esp. (Once you get more experienced you will know which mod types contain records that go into it. Starting out just remake it every time you add a new .esp). The last 5% are various small changes... that depend on your list. The bashed patch is almost always the last mod on your list. When in doubt place it there. I say almost since if you use skyproc patchers then they come later. For STEP just place it last.

Thanks for pointing that out for me! The readme is rather outdated... I guess I should have that removed since the actual guide contain all the information and more anyways. Actually thought I did that already... In short there are only four values Exposure Scale Exposure Threshold Adap Min Adap Max Between those you can control overall brightness very accurately. The first two are the most simple to adjust, and I would suggest that one tweak those before the others. However as you make stuff brighter then you will also alter how when adaptation kicks in, hence it might be required to adjust the other two as well. I guess I overall should make a much more rephrased section in the guide about how to do this next time I write a revision of it. Thanks again, and I hope I helped you out in an understandable way! :)

Yeah first complete STEP and make sure it works, then you can play with lighting overhauls. ELE image spaces are only required for the reasons mentioned earlier.. they will make sure you wont have a million different weird interior issues while using ENB presets. As for where you place them....if in doubt then just place them near the end of your list. They only need to overwrite any mods that alter interiors... ie any lighting overhaul mods, house mods, and mods like that. None of which are in STEP atm as I recall.

North :P

Oh missed this one it seems. The saturation is very easy to adjust (Lower vibrance either via the GUI under enbeffect.fx from 0.15 to 0.0 or lower) and you will get an overall more realistic color theme. As for not noticing the effect then that is just weird since the effect is rather strong. It ofc. depends on the weather and the location since you need a certain brightness for it to trigger. I did remove it so it does not trigger all the time like in vanilla.. since that just gets annoying. However if you during the night just throw flames you will see it working very well. And if you find a really dark shadow during a bright day then it will brighten ever so slightly. If you want the effect to be even more pronounced then I can also provide the instructions for doing that. But since this is a rather old post by now I will wait and see if it is still relevant.

Moving this to ENB support instead... I am guessing this is just yet another issue with the ENB manager where it somehow fails to copy in and/or delete the right files. This is why I always suggest that one does not use it and just copy in the files manually. You can compare what you have with the screenshots that are up on the vividian page... if they look similar then you got the right look. However it might also be some monitor calibration issue etc if it is not. First order of business should be to make sure that only the right files are used.

First just try to alter the Exposure Scale and threshold values.. they work very intuitively, and are set to work with computer monitors. Increasing the scale will make everything brighter. And is probably the better solutions for TV´s... sadly I do not have a TV myself to test on so I have never updated the guide for people with that kind of setup. If it starts to get too washed out then reduce the Scale a bit and then alter the Adap Max and Min values. The reason they work sort of counter intuitively is because they work a bit differently depending on if it is day or night/interior. However if you just scale them up to extreme values you should not be in doubt about which way to go. In all cases you will see the changes as you alter them.. when you are happy you just hit save and close the GUI, and the values will be used from that point onward. Hope that helps otherwise just post again and I will help some more. Also thanks for making me aware that stuff is still a bit confusing!