fallout new vegas script extender steam workshop

It definitely does not create a configuration file or automatically enable it's log files (which will be found in the game's root folder). However, just unpacking the NVSE archive package to the 'Fallout New Vegas' folder may not create a 'DataNVSE' folder or the 'DataNVSEPlugins' sub-folder upon installation unless you tell it to include sub-folders when doing so. 'steamappscommonFallout New Vegas'), so it's along with the FalloutNV.exe file. A plain text editor like Windows Notepad.ĭetail When installing New Vegas Script Extender (NVSE), the nvse_loader.exe file should be in the game root folder: i.e.This procedure a template so it may be included in several instances in the article 'Fallout NV Mod Conflict Troubleshooting'. I also tried to do the changes in all of the 3 different. I already manually turned of Steam Cloud function in Steam and have the latest patch installed, no changes. Since the FalloutPrefs.ini is the only place where I can change the hotkey keys, the changes don't stay, as the Falloutprefs.ini always reverts back to default. inis, but somehow that totally messed up my customized hotkey remapping. The new patch somehow solved the problem with adjusting your.

Anyone have luck modding the fallout.ini and having it stick? I have the write permissions to the remote folder disabled and the fallout prefs there were deleted so that's not where it's overwriting from. It doesn't like bUseThreadedAI=0 so I'm trying to change that to 1 and add inumHWThreads=2 but the file reverts back to the default settings upon playing and it's still crashing. The crashes seem consistent with what I saw in fallout 3 with my i7 920. Hey guys, having lots of crashes now with the latest update pushed out.

Fallout new vegas script extender steam workshop