Deleted5210271User Posted September 13, 2017 Share Posted September 13, 2017 I have an issue with ENB where any time the lighting conditions change (Pip Boy, parts of the opening scene with Doc Mitchel) the entire screen is consumed by extreme blurriness and darkness, making it almost impossible to see anything. It stays that way until the game is relaunched. I've narrowed it down to being an issue with ENB itself, as I have no other mods installed and am using the base wrapper ENB, with no presets. I've done thorough research through the various ENB troubleshooting websites as well as searching for this specific issue, but it seems I'm the only one that has it. Demonstration of the bug: https://a.pomf.cat/alixpk.mp4 -This issue occurs when launched through MO, when launched through Steam, and when launched through the game's folder. It occurs with NVSE, the regular .exe and the .exe patched to 4GB. -I have double and triple checked that the necessary values are disabled in the Fallout.ini and FalloutPrefs.ini files, in both the Documents and MO's profile folders, and that the files are set to read-only afterward. -I have disabled any settings in my Nvidia control panel that could interfere with ENB. -I am using the v278 ENB binary, wrapper version. The injector version wouldn't function at all. -Again, I have no other mods installed, and only test on a new save file. The only other plugins I have are the official DLCs. -For the 4GB patch, I am using the version that modifies the standard .exe, NOT the version that requires placing things in an "exe" folder. -I have installed all the ENB files in the correct locations. Nothing misplaced into the Data folder. -I am using Windows 10. fallout.ini: https://pastebin.com/cZuHG319 falloutprefs.ini: https://pastebin.com/Qtj3f1G7 load order: https://pastebin.com/MEjRdVLC enblocal.ini: https://pastebin.com/upXr7Ep9 Nvidia control panel settings: https://i.imgur.com/qkxG3tR.png Fallout New Vegas main folder: https://i.imgur.com/CSwEJgn.png Any help would be greatly appreciated. Link to comment Share on other sites More sharing options...
dubiousintent Posted September 13, 2017 Share Posted September 13, 2017 (edited) I know you said you checked the MO profiles, but did you compare them for differences using a "diff" program like "WinDiff" or "ExamDiff"? They can catch things you might not spot just eyeballing it. Otherwise, all I can suggest is seeing it there is anything in the 'Solutions to Post-Processor (ENB/SweetFX et. al.) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide you might have missed (though it certainly sounds like you covered all the bases). -Dubious- Edited September 13, 2017 by dubiousintent Link to comment Share on other sites More sharing options...
Deleted5210271User Posted September 15, 2017 Author Share Posted September 15, 2017 (edited) Well I reinstalled the game and updated my graphics drivers, just added ENB back in with nothing else and everything is working so far. Going to slowly add mods back in and see how it does. Edited September 15, 2017 by Guest Link to comment Share on other sites More sharing options...
Wittz8 Posted February 18, 2020 Share Posted February 18, 2020 I know itâs been a while, but I had this exact same issue and I think I have the fix. In the ENB in-game menu, one of the variables, which is usually set to 1, was set to -1. I set it back to 1, and voila, it works perfectly. Link to comment Share on other sites More sharing options...
dubiousintent Posted February 18, 2020 Share Posted February 18, 2020 That's helpful, but which setting? Was "-1" a valid possibility (though inappropriate at the time) or never valid? Do you have any idea as to how if got set to "-1"? (This is one of the few examples of a reasonable "necromancy". Thank you.) -Dubious- Link to comment Share on other sites More sharing options...
dragbody Posted May 18, 2020 Share Posted May 18, 2020 Hate to necro, but I was experiencing this. Found this thread looking for a solution. Turning down my AmbientLightingCurveInterior from the basic settings fixed it. Maybe this helps someone in January 2021. Link to comment Share on other sites More sharing options...
Recommended Posts