Enbseries v0.194 for fallout new vegas install#
There are apps that can do that like cff explorer, but the easiest way is to install the latest NVSE, it automatically patches the exe for you when it runs. The second thing that is majorly important when you use a 64-bit OS is to make sure the FalloutNV.exe is set to be able to use more then 2gb, You need to insert the line iNumHWThreads=2 under the section all the way at the bottom of that section. To solve that problem you need to insert a line in all three of your ini files.įallout.ini and Falloutprefs.ini you can find them in documents/my games/falloutNVĪnd in Fallout_default.ini in your Fallout install dir (cause Fallout NV tends to use this file a lot after each game crash to rewrite the Falloutprefs.ini in the above mentioned directory) The main problem why Fallout tends to crash a lot is that it is not optimized properly for use with more then 2 CPU cores. But ffs, be up front and honest with us about it at the very least.īoris is not pushing the blame off imo, it's just hard to know everything about every game, i for one think you should configure Fallout properly. You don't owe us a damn thing, and none of us are expecting anything. If you have no plans on looking into it/fixing it, tell us. But the evidence strongly suggests otherwise, and continuing to pretend it's an issue that doesn't exist insults our intelligence. V0.173 - Works fine with all driver versions.Įvery time you respond to this issue, you push the blame off on unknown software/faulty drivers/bad settings/etc. Crashes on loading screen after selecting continue on all driver versions. V0.194 - Doesn't work with any driver versions. V0.216 - Doesn't work with any driver versions.
Enbseries v0.194 for fallout new vegas drivers#
Tested on a fresh install of Windows 7 圆4, having only installed drivers and updates, steam, and new vegas. Tested using 12.6, 13.8, and 13.10, upgrading each sequentially. I just tested this today after seeing the new fallout enb update. ENBSeries wrote:Other software do this or bad drivers/forced antialiasing
0 kommentar(er)
