TechAngel85

It's a bit of a complicated process for anyone that hasn't done much with TES5Edit. https://ck.uesp.net/wiki/TES5Edit_Documentation https://www.nexusmods.com/newvegas/mods/38413/?

No, those values wouldn't cause a CTD. A lower value, as Phazer11 pointed out would be better because you'll never need that much RAM for ENBoost. Would need more information to troubleshoot this. First make sure that the CTD either happens or doesn't happen when you don't have ENBoost installed as it could be something else entirely.

Link? I don't have these saved. lol

The profiles for Nvidia used to be stored in an XML file; however, they've moved on from that a few years back. They are now integrated into the API from what I understand. If you've exported them using Inspector, the default location of the exported profiles is in the Inspector folder. You can import them again using Inspector. If you didn't export them, I don't know of any way to retrieve the profile from the Control Panel itself. Searching on Google will be your best bet if you didn't export the profiles using Inspector.

Make sure AO is set to be enabled or app controlled in the drivers. I don't know how AMD drivers are, but I know Nvidia has two options for AO. One sets it to enabled so that games can use it (if the game doesn't use AO, it won't be forced just by enabling it). The other setting actually forces AO on via the drivers. So look for some settings in your drivers to make sure you're not forcing it off.

I'm not sure what this issue could be then. All the Nvidia Control Panel stuff is for the drivers which have nothing to do with MO. They should be forced regardless of what application you're using to launch the game unless that utility overrides those settings in the driver. MO does not do this. The INI in MO could do this; however, those is not MO per se. That's just the game using the INIs as it normally would (which the drivers can override or stack onto). ENBSeries is one thing that could override the driver settings. If you have ENBoost set up properly, this shouldn't be an issue though. I personally use a combination of ENB settings and SMAA to provide my AA solution. The drivers are set to App Controlled and AA is disabled in my INIs. When ENBSeries isn't installed, I just simply use SMAA.

Switch to the InjectorVersion of ENBSeries and the add in the proxy as normal without changing the name of the dll.

Using the ENB side is more desirable than drivers due to Boris's special filtering out of textures that should not be put through AF. The quality is the same either way.

Thanks for this! Indeed it was very annoying!

Guides should still be good since you offloaded most of the ENBoost stuff.

You have to rename the d3d9.dll of Helix, not ENB and update your enblocal.ini: [PROXY] EnableProxyLibrary=true InitProxyFunctions=true ProxyLibrary=d3d9_Helix.dllJust a disclaimer...I've never used Helix and don't know if this will work, but it is the proper procedure.

Cool! Thanks for going out of the way to verify that. I'll update the recommendations. EDIT: I updated the recommendations on the Guides: https://wiki.step-project.com/STEP:2.2.9#1.E.1.2._Nvidia_Users https://wiki.step-project.com/Guide:NVIDIA_Inspector#Texture_Filtering

There's two different recommendations. For ENBoost users, driver. For full ENB users, enblocal.ini.

I don't mess with water cooling.

Do believe you need to read it again: [ENGINE] ForceAnisotropicFiltering=true MaxAnisotropy=16 ForceLodBias=false LodBias=0.0 AddDisplaySuperSamplingResolutions=false EnableVSync=false VSyncSkipNumFrames=0 Also see my previous post.

No it's enabled by default, but I'm pretty sure AF is disabled with you disable the graphics modication (running only ENBoost). I'd have to verify that though. EDIT: Why are we providing the default INI as a reference? Seems like a maintenance nuisance because Boris changes the defaults from time to time with little notification and without updating versions.

Seen this the other day and have watched the few that exist. He's doing a good job. I'm still doing them myself as I'd like them to the consistent. As for the rush, I'm not in one. The Guide is far from being finished in both comparisons and having the parameters properly defined. I was giving everyone a break since the holidays usually take up most of people's time. Planning on annoying these guys again very soon to see if they're still interested or not.

Where are you seeing it set in both? https://wiki.step-project.com/ENBoost#Recommendations

Aiyen is right, you're just lacking raw power with the GPU. The 970 is where it's at if you have the money. The 960 only performs slightly better than the 760 (which is the card I have). 4GB of VRAM is also a must, imo, for any serious modder. The extra VRAM makes a difference to both performance and textures because you're offloading less data to system RAM. As for the enblocal.ini settings, you need to set them to the lowest values that you do not experience any stuttering or negative effects with. Reserved memory is going to take up precious VRAM so that needs to be as low as possible where no issue arise. The other setting tells the enbhost.exe process (ENBoost) how much system RAM it can potentially use. This will rarely be any higher than 2-3GBs but setting the value higher can help performance. However, setting it too high has caused performance issues in some systems. So it's a balancing to find the right values for your system and you can only do that with testing.

It's your GPU. It's not powerful enough to run a full on ENB preset. You're going to have to choose lighter weight ENB preset (or performance version), turn off some ENB effects, or forgo it altogether. If you stick with an ENB preset, you should probably tone down your memory settings in your enblocal.ini. I've never seen them needing to be set that high.

I've added the Skyrim, Fallout 3, and Fallout NV tags to the Post Processor forum. They should be available for selection now in that forum.

You have vsync enabled and running properly?

Re-install DirectX 9 manually. This solution worked on another thread so lets try it here as well to run it out.

I find that solution mind blowing! Though I had thought about it being DirectX, the fact that the game ran fine ruled it out for me. Guess I'm going to have to start suggesting it regardless.

It's been known for quite some time that the driver forced AA doesn't work in Skyrim (can't say for FNV). I don't think it's ever been linked directly to MO though.