Jafin16

There isn't anything official about GSync from Boris yet, but from my knowledge of ENB and GSync Technology I would say to turn of Vsync in enblocal.ini and enable Gsync in NV Control Panel (if you want to use Gsync). Vsync disabled in the drivers is recommended simply because you can have Vsync enabled in ENB and have all your graphic settings for Skyrim in one place - ENB. Boris recently said that Vsync enabled in drivers or in ENB makes no difference. What I don't know is how Gsync interacts with the skyrimprefs.ini setting iPresentInterval. This parameter is Skyrim's own built-in Vsync. My guess is that you should make that =0 and drivers will override and apply Gsync but I'm not sure.

Not a bad idea. I'm sure everyone is kinda just busy with their own projects and could use a reminder.

I just added a number of notes to the EFFECTS section of the guide, generally clarifying the more specific uses of an effect and/or whether it's something best left to the preset author or not to decide. I didn't make notes on all the effects, but a number of them.

Hey there, just wanted to let you know I'm still around and I check this thread occasionally. I've been very busy since before the holidays so I haven't added anything new to the guide in quite some time. I haven't even really had much time for Skyrim or my own ENB lately. Anyways, I'll look at the guide, see what we're still working on and make additions sometime soon-ish. I've settled into my new job fairly well so I'll likely have a little less stress and a little more free time in the coming weeks. Next week will be busy, but should die down a little after that. I hope others are still working on or planning to work on this! I know you're on it, Tech ;)

Hi all, sorry for a long silence. I'm still trying to keep up with this but real life has hit me like a train lately with a new job, holidays, getting sick twice, etc. and my free time was absorbed with DA:I. I'll try to add what I can over the next week or so. Still here, just occupied :)

Just wanted to update and say I've added a little explanatory info to a number of the Water entries. I'll keep filling in more as I have time and add a little more information about some of the entries I already made.

That is freaking awesome :) Got it up on my description page.

Matso, if you want good examples of volumetric rays done right, I'd recommend taking a look at Confidence Man's NLA or prod's Serenity (Serenity at least used to have really good rays... haven't tried the latest version). Done right, they're excellent.

Ok, I'm glad I'm not the only one that feels that maybe my technical knowledge is wrong and someone could say it better. I'll look at some things again since you've been doing some significant changes, but I hope a little today and more this weekend, based on looking at the guide last night, to hit Water and Procedural Sun as I think I have a pretty good handle on and recent experience working with those. Anyway, I guess the point is to start working on the guide, get the information there, sort through it, curate it and finish it. Some of us have better technical knowledge (here's lookin' at you JawZ! ), others have practical application information. So we just do it then... got it. -Jafin EDIT: As an after-thought, to avoid overlapping too much at this early stage, it might be a good idea to state, as I did, any particular areas you would like to work on and, when you've added what you can, say so as well. This way I think we could get more covered and some of us might feel a little less overwhelmed by the entirety of the .ini file. Once we're done, others can go in and clarify and fact check until we have it right. Thoughts?

Sorry to go a little off-topic, but just wanted to let you guys know I finally released my preset! I has excite =P It's here if you wanna take a look: https://www.nexusmods.com/skyrim/mods/59901/? Now I finally have some time to help with the guide!

Can you be a little more specific as to what you mean by "not working"? If you're trying to make changes and then they don't change properly OR they revert when you start the game then it's as simple as hitting "Save Configuration" in the GUI. Sometimes you need to do that and then hit "Apply Changes" for it to show in game. I could be misunderstanding your problem though.

I run AMD, always have and so does my brother... with older versions of ENBoost, we both had to set DisableDriverMemoryManager=true but with more recent versions and/or drivers that is no longer necesssary. Make sure you're using the latest beta drivers from AMD and latest ENBseries binaries and you should have no problem. I've never needed to use the injector either.

Not possible with Mod Organizer. ENB FXAA SweetFX Manager from the Nexus can do this though.

Others have said similar but with more words... don't run ANY external game boosting programs. At all. Terminate them before starting the game and don't run them before starting the game. They might messing something up in some weird way you don't know. If you need to free up memory, use Task Manager and do it manually. Update your video drivers (or downgrade. I'm not an Nvidia user but I know 314.22 drivers have always worked well with ENB, even though they're old.) Also, even though it worked before, do this - make sure DirectX 9.0c is installed properly. Even though you may have DirectX 11, it doesn't mean you have DX9. Here's the link: https://www.microsoft.com/en-us/download/details.aspx?id=34429 Then, try running the game. Remember NO GAME BOOSTERS of ANY sort. 99% of the time it's an external program causing issues. If it's STILL not working, try using the injector version of ENB and see if that works. The problem is always fixable... it's just annoying sometimes.

If I remember correctly, volumetric rays have something to do with light reflecting off the clouds and shadows created (uber-oversimplification). So yes, it's different types of godrays shooting from the clouds as well as the shadows in the clouds. As an aside, if you use the ENB weather system, you can get very different looks for the sky using them effectively with higher and lower densities based on the amount and density of the clouds. I'm still struggling with getting them right in my almost done preset. However, as you said, they can definitely cause what I wouldn't call a quality drop but more of a "bleaching" of the entire sky. Increase density obviously makes them scatter less and give you bluer skies (or whatever the color may be) as you've found. And of course you can just turn them off if you don't like the effect =P -Jafin

The enbseries.ini is kind of a monster when you start getting down to it. I'm going to have more time to help out with this after this weekend too (I hope), so I'll be able to do some additions here and there. I'll have to take a look again and see exactly what's been done so far.

I actually have the same problem. I've never actually followed a STEP install (I'm more of a DIY kind of guy ;) ) and have the same problem with the same mod. I've noticed that using the numpad keys does NOT have the same problem though.

I didn't realize that about the palette either... I might have to rethink using it too. Does an increased resolution palette help or is the size limited to 256x256? Obviously, procedural color correction is probably all around the better way to go, but if an increased size does help, it might be good to add that to the guide as well.

I think using an ENB that's more or less a vanilla enhancement would be the best way to go. I know MTichenor's SkyRealism ENB Evolved has a vanilla color version that looks quite good. It is, however, a bit behind on updates IIRC. I think the latest is for v0.221? The shaders are also far from default. I'm not a big fan of just using ENB out of the box because it kinda looks bad, IMO. If that's what you all decide to do, that's fine with me and I'll go along with it, but I think something that's actually configured to look decent without altering vanilla colors much or at all will in the end be more helpful so people can actually see what it looks like in practice.

Just wanted to note that I made a very small change but didn't add it as an addition. In [sHADOWS] for DetailedShadowQuality, it previously listed the quality settings as 0, 1, and 2. I added -1 as well since that is a viable variable for that parameter. -1 does indeed function. That's all so far! I've been a bit busy in RL lately so my time has been limited... and on top of that I'm trying to get my preset finished, tested and released in a little over a week. Yay! Anyways, hope that's alright I made that change! I'll follow the requested format for changes for the rest of the guide. -Jafin

I'd be happy to help with this project. I'll take a look at the guide soon and make some additions where necessary. Just to clarify, is this guide specifically related to the enbseries.ini only or is it to ENBSeries as a whole, including shaders and such? -Jafin

1. If I remember correctly, yes, except it's implemented by ENB which is nice for keeping everything in one place. 2. That totally depends on the ATI/AMD card and the driver version for it. Basically, if you have a buggy driver that doesn't handle memory management properly for ENB set this to true. Then dx9 and a variety of other factors will manage memory. For my R9 290 with latest 14.3 beta drivers, I have no problems. However, when I used a HD 7870 around 13.10 and early 13.11 beta driver builds I had to set it to true. Others with similar cards have had different experiences too. The thing is, Skyrim is SO BAD at handling memory that there's no sure-fire way to go. I haven't heard of anyone having problems with the 13.12 WHQL drivers from AMD at all or and of the 14.x beta drivers, nor have I had any issues since then either. Test it with both for stability and responsiveness and use what works best. Anything that still holds the actual ATI branding (HD 5xxx series and lower) will probably need it set to true. The thing with ENBoost features is there is no certain 100%-this-is-how-to-do-things-to-make-it-work because of the nature of varying systems. Everything we have are guidelines (albeit good ones) and so each person needs to make things work best for their system. However, by sticking to the guidelines and then making variations within those guidelines is the best way to go. Hope that helps :)

Hi there, I usually don't lurk around here too much (maybe I should more, lots of good stuff), but I just happened to run across this thread and I just want to clarify that the information I've given and was quoted here is simpky a lot of information Boris has shared about ENBoost since its inception that I've distilled into the short post there. There is a lot more involved of course, but for the general user, that's the info you need. I'm curious what might seem to convey some misinformation. If you look at the thread Boris commented 2 comments after me, addressed the person who inspired the original post and said this in regards to it: Original Post Regarding the formula for setting VideoMemorySizeMb, the VRAM+RAM-2048 is for a 64-bit OS running at least 8GB of VRAM. What some of you have seen around recently about setting the value to VRAM minus a little bit (like 128MB) is intended for a 32-bit OS or 64-bit OS with less than 8GB of RAM. Regarding ExpandSystemMemoryX64 I can't say in regards to SKSE 1.7. As of yet, it's still alpha, it is not required for any mods I have or am aware of, and SSME works fine for Sheson's Memory Patch with SKSE 1.6.16 so I don't see a reason to switch to an alpha build at this time. I believe Boris did a fix in one of the 0.250 (or just before 0.250, can't remember) builds to help compatibility with SKSE but I don't know exactly what he did there or how effective it's been. Those complaining (one person mostly) simply left and haven't posted at enbdev since. @keithinhanoi The recent increase to allowed memory at 128 GB applies to enbhost.exe, not VideoMemorySizeMb. I do find it interesting that auto-detect showed 15-17GB of VRAM, however, according to Boris most recent information, the limit for that setting is still 10240. You can set it higher, and it will show higher, but ENB will not use more than 10GB, regardless of what that shows. However, for all of this, there are a lot of variables to consider, such as your motherboard, RAM speed, even Graphics Card bus speed. These are all the values to START at, and then tweak based on what works on YOUR system, hence the reason the implementing of the enblocal.ini file - it's specific to YOUR system and is meant to stay there. For reference I'll post my relevant system specs here and my ENB memory settings. Happy modding/tweaking/gaming! -Jafin16 PC Specs: AMD FX-8120 @3.3GHz,4.4GHz boost 12GB DDR3 1600MHz AMD Radeon R9 290 w/ custom OC Gigabyte GA-970A-UD3 Mobo ENBoost Memory settings: [MEMORY]ExpandSystemMemoryX64=trueReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=512VideoMemorySizeMb=6144 //8192, 10240 work just as well. Set to 6144 to free sys ram for other needs.EnableCompression=falseAutodetectVideoMemorySize=false