TechAngel85

In my opinion, FRAPS. Forget Steam whatever you decide. It will not capture ENBs properly. If nothing else you can simply use the ENB included function to capture screens.

There is a really old one on Nexus that is really outdated by the author Jawz (same author as Enhanced Lighting for ENB). STEP is putting a Guide for this together but it will be a while before it's complete.

We'll need to keep an eye on this since STEP doesn't use parallax mods. They generally look bad without ENBs.

Same here. In fact, I'm still running v1.2.9 of MO. Still haven't updated it and have seen no real reason too since I'm not experiencing any of the bugs. I'll get around to MO and this mod eventually.

There has been quite a bit of debate over the available Nightingale retexures in general. We're mainly waiting for CaBaL to finally retexture this one. Once he does, this will most likely be dropped.

Normally if we refer to STEP:Extended as it is written, "STEP:Extended". Just as Core is written as STEP:Core. So you might have been looking at details; however, failed to noticed that detail. Haha! Of course and against popular belief we are, in fact, human...so there might be some instances where we forgot the prefix "STEP:".

Leather version, not carbon fiber version.

I'm more than willing to backtrack and revisit pages as needed. I've actually been thinking of making an ENBoost section as that is easily one of the most important parts of ENBSeries to get right, as well as, one of the most confusing for a lot of users. I'm thinking that would be the best way to handle ENBoost and basically remove it from other sections besides the Quickstart section. It will ensure all the information regarding ENBoost is all in one place and allow us to get much more detailed if need be. As for the rest of the ENBlocal INI section, you are correct. We're tried to keep it short and to the point without providing a bunch of tech speak that most users simply wouldn't care about or don't need to know. We've basically tried to narrow it down to what it is, what is does, and what the affect will be on the game. With that said, if any point needs to be more detailed then we can get more detailed to provide the basic information. Once your Guide is finished, which I'm sure will go into the enblocal.ini file in more depth, I can provide a link to it for users wanting the more in-depth information. I'm already doing this with the enbseries.ini file. @Tony, I'll check out SkyrimTuner's FAQ.

You have to expand the first directory and then right-click on Data and choose "Set as data directory". Then you'll be good to click OK to install and move to Step 3.

You're not looking at TESV.exe in task manager. Look for enbhost.exe which is ENBoost. There could be multiple even. However much enbhost.exe is using is how much extra the ENBoost feature is using.

What Aiyen said. Basically download the generic ENBSeries, set up the memory part of the enblocal.ini file, turn off just about everything else but parallax in both INI files and there you would have ENBoost with Parallax enabled. There is obviously a bit more to it than that, but that's basically what you'd need to do.

Because there aren't any that fit the vanilla female body. This is the reason for the STEP Female Overhaul.

Okay, it's time to move on again. We're skipping the Advanced Editing section since there is nothing there but some text and a link. Also, for know, we skipping over the Addons section since I'm not done with it yet. This lands us on the Troubleshooting section of the Guide. I know there is a LOT more info that can be added to this page and I plan on browsing the ENB Support forum to add to this information, but for now, I just need to know if the information presented on the page is accurate. If not, we need to address it. The AMD section was added a really long time ago and since I'm running Nvidia, I have no idea if it's accurate or not. For those of you that are helping, please review and let me know of anything that is off.

Yes, merge away! It's better for "noobs" to learn the differences in the options and learn when to use which option rather than us spelling it out. All modders should be familiar with the tools involved in modding, in this instance MO. Merge = overwrite conflicting files. Non-conflicted files will remain in place and untouched. Replace = delete the mod and all its files and "replace" the mod with the new installation. Old mod is deleted entirely and new more replaces it. Rename = rename the mod so both installations are kept. Merged is used for instances like this when installing addons or updates that will require the main mod to remain intact. The addon or update will simply overwrite some of the files from the main mod but not completely replace it. Replace is used when the entire mod is being replaced, such as, when updating the main file of a mod which would completely overwrite the old version. Rename is used to simply rename the mod to a different name in order to not merge or replace the file. This can be desirable in certain situations or for personal preference... Say for example you have a profile in MO that you don't want to have Dawnguard active during the play-through. If a mod in your profile as a "Dawnguard addon", instead of merging it you'd want to rename it from "ModXYZ" to "ModXYZ - Dawnguard Addon". This would allow to you to keep the Dawnguard addon active in all your profiles and deactivate it for just the single profile that excludes the Dawnguard DLC in the play-through. Another example to use Rename is if you have different mods installed for different play-throughs that require different patches for each profile. Consistent Older People is a good example. In one profile you main have Bring Out Your Dead active and in another profile you may not. This would require two different installations of Consistent Older People or the game would crash at startup due to missing masters. Therefore, you could name it on installation "Consistent Older People" for the profile without Bring Out Your Dead active and for the other installation "Consistent Older People - BOYD" for the profile with Bring Out Your Dead active. As you can see, we can't really explain this on every mod page. The Guide would double in length! That is why we encourage users to take the time to learn the tools they're using.

It is but you might see a bit more of a drop in FPS because to do that, some of the ENB graphical code will have to run and process.

The install order (left pane) and load order (right pane) are kept independent from one another in all the mod managers. It's not just a MO thing. So install the mods in a specific order to address conflicts properly and then run LOOT. Both lists will be maintained as they should be without you needing to worry about things like that.

I've expanded on the explanations of autodect, reserved memory (and reworded to be more clear), and video memory size. I've also added a sentence to the notice in the FPS Limiter section to include it not working at all. As for the recommendations, they're going to stay. They're just like any other recommendation on the STEP Guide...a "recommendation". Users are under no obligation to follow it. For Anisotropic specifically, I did a test run between the driver 16x, ENB 16x and ENB 4x. Between the drive and ENB there was no FPS difference. Between ENB 16x and 4x there was a .5FPS (yes, 0.5) gain which just confirms what I've known all along. The FPS difference between Anisotropic settings is really a non-issue.

I too use a Xbox 360 controller, but only for the games that are nearly impossible to play without one. Like Witcher 2....you need a third hand to play that game with a keyboard and mouse.

Mod Order: STEP PatchBashed PatchDSRDSR PatchBetter Shaped WeaponsFNIS BehaviorFNIS PatchNever hurts to run LOOT. Tags must be added in WB during patching. BSW can be installed after you've installed DSR. It's mentioned because some users might mess up the install order...it's happened already...it'll happen again. LOL!

Nothing I've read states that it is reliant on deferred rendering; however, Boris doesn't document very well. Best to just ask on the ENB Dev forums.

This will nearly impossible to troubleshoot with what you provided. I'd suggest getting STEP installed and working 100% before adding in anything extra (which from your description you have at least a few non-STEP mods). If you're missing masters MO will tell you with a big red warning icon that is hard to miss in the plugin pane.

Superman capes would be so much more awesome....just saying.

We're not recommending to use the auto detection anywhere. In fact, we provide examples on how to set the memory settings manual everywhere that these parameters are mentioned. As for the Reserved memory parameter, we give users a general starting point, but we also state that users will have to test to find the best value for their system. Anisotropy has very minimal performance hit so lowering it from the default 16, will have very little affect performance wise. Actually, not to be blunt, but what's the problem here? Most of what you posted is what's already in the Guide...just not worded in the exactly same way. Also, the Guide isn't a, "set this to this and your done" type of Guide. It's a, "this is what this does, this is the effect it'll have, set it however you like" type of Guide in order to teach users. This way they can make the best decisions for their setups. That is the nature of ENBSeries, no one setup will work for all users. EDIT: I've contacted Keith asking for him to look it over if he has the time and want.

I'm almost 100% sure those are the vanilla vampire face textures and that is where the issue is. None of them look like the one included with the overhaul. The texture path could be wrong so I'll look into that. Edit: Nope, those are from the overhaul. There just seems to be a tint applied that is messing with it. I'll test more later.

VideoMemorySizeMb 32bit system = size of VRAM 64bit system = (VRAM + System RAM) - 2048