vane90 Posted June 19, 2018 Share Posted June 19, 2018 Hi. I'm at a loss here after trying for long hours to fix this, so I must ask for help. I installed NV, set up my ENB and a few texture mods, game was working fine via NVSE launcher. I started adding other mods, including WME, WMX, EVE, etc.. now suddenly NVSE is hell bent on resetting my falloutprefs.ini every single time, no matter how hard I try to stop it. It forcefully overwrites gfx settings to medium, sets my resolution from 2560x1440 to 1176x664 and sets my video adapter to NVIDIA GeForce 7900 GS (no idea where this is pulled from) from what I actually have, which is NVIDIA GeForce 980 GTX. I also got the message that the renderer is invalid and something about a Gamebryo. Specs:https://imgur.com/a/T8AEmmg I hope I provided sufficient information and thanks in advance. Link to comment Share on other sites More sharing options...
Mktavish Posted June 19, 2018 Share Posted June 19, 2018 Sorry I have no clue why it would do that. But here is a hacky work around that might be worth trying. Just move all the default setting .ini configuration files out of the game folder , except the one you want it to use. There is low.ini , medium.ini , high.ini and veryhigh.ini ... in the Fallout New Vegas folder. If it doesn't work , just put them back. Link to comment Share on other sites More sharing options...
dubiousintent Posted June 20, 2018 Share Posted June 20, 2018 The rewriting of the "falloutprefs.ini" is new. There is no reason from NVSE to do that I am aware of. (I suspect an ENB pre-set causing that. Please see the 'Solutions to Post-Processor (ENB/SweetFX et. al.) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for that particular issue.) The "renderer is invalid" has surfaced before related to the NMM update for EU GDPR. Some people are finding that even after updating NMM to v0.65.4 they still get a "script exception" message when installing some mods (such as UIO and MCM). This seems to be resolved by this suggestion from user ElysianMod:* Run NMM as an "Administrator privileges" account.* Go to NMM "Settings".* Enable "Add Shell Extensions for Supported File Types".* Then restart NMM.(Supposedly this fix will be included in the next "unofficial" update to NMM on GitHub.) * Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so. Please take a moment to let us know if this does resolve your problem so we can more confidently suggest it to the next person with the problem. -Dubious- Link to comment Share on other sites More sharing options...
vane90 Posted June 20, 2018 Author Share Posted June 20, 2018 (edited) The rewriting of the "falloutprefs.ini" is new. There is no reason from NVSE to do that I am aware of. (I suspect an ENB pre-set causing that. Please see the 'Solutions to Post-Processor (ENB/SweetFX et. al.) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for that particular issue.) The "renderer is invalid" has surfaced before related to the NMM update for EU GDPR. Some people are finding that even after updating NMM to v0.65.4 they still get a "script exception" message when installing some mods (such as UIO and MCM). This seems to be resolved by this suggestion from user ElysianMod:* Run NMM as an "Administrator privileges" account.* Go to NMM "Settings".* Enable "Add Shell Extensions for Supported File Types".* Then restart NMM.(Supposedly this fix will be included in the next "unofficial" update to NMM on GitHub.) * Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so. Please take a moment to let us know if this does resolve your problem so we can more confidently suggest it to the next person with the problem. -Dubious-Thank you for your reply. I did state, however, that I'm using Mod Organizer (MO), not NMM. MO 2, to be precise. I've also thought about the ENB (Nevada) being the cause of the problem, although I haven't found anything wrong in the ENB ini files. I'm going to try to run without it and see what happens when I get back home, then update the thread with new findings. Edited June 20, 2018 by vane90 Link to comment Share on other sites More sharing options...
dubiousintent Posted June 20, 2018 Share Posted June 20, 2018 Try to get a screenshot of the "renderer is invalid" message if possible. Hopefully that will give some indication of the source. The only known NVSE conflict I am aware of is the following: * If you are suddenly having a "slowdown" or lag; or a lack of sound; or problems getting NVSE to load, or really anything new unexpectedly, please see the 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. This may be due to a Windows Update for the "Meltdown and Spectre Vulnerabilities". All the Windows system updates since then have included some mitigation of those two vulnerabilities, and usually cause problems for older programs. -Dubious- Link to comment Share on other sites More sharing options...
vane90 Posted June 20, 2018 Author Share Posted June 20, 2018 (edited) Reinstalled the ENB. Now at least the launcher detects my gfx card correctly and doesn't reset my inis. But I'm still getting the renderer error. So most probably it's the ENB acting up. https://imgur.com/a/uPCQOxg <- error message Edited June 20, 2018 by vane90 Link to comment Share on other sites More sharing options...
vane90 Posted June 20, 2018 Author Share Posted June 20, 2018 Update: reading the latest comment on the ENB's page revealed my problem. It was the 2 Dx10 files in the folder that caused the mismatch. Weird that the installation instructions didn't specifically point this out. My issue has been resolved, thanks for the effort trying to help me out. Link to comment Share on other sites More sharing options...
dubiousintent Posted June 21, 2018 Share Posted June 21, 2018 Glad to hear you resolved your problem. But despite the hint I was unable to locate the referenced comment to help another user with a similar "render error". Would you be kind enough to provide a link to it, or (preferably as comments tend to scroll out of sight quickly) summarize the solution? -Dubious- Link to comment Share on other sites More sharing options...
vane90 Posted June 21, 2018 Author Share Posted June 21, 2018 I believe that error can be caused by many things. I deleted the dxgi.fx and dxgi.dll files that came with the Nevada ENB (v0249 old version with Nevada Skies mod). They were both inside the install folder, but they caused the render error for me. I removed them and everything was working fine instantly. Link to comment Share on other sites More sharing options...
dubiousintent Posted June 21, 2018 Share Posted June 21, 2018 Thanks for the summary. I've now been able to locate previous reports to better understand the problem. It's been around for awhile. Definitely going into the "Troubleshooting" guide. Edit: Added as 'Issue: Render Error using ENB/SweetFX'. You are correct that many things can cause a particular error message. They are often just a "best guess around here in the code somewhere" response by the programmer, as anything they can specifically anticipate will usually be handled by programming. They're cries for: "Help! I need another human to figure this out!" -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts