![]() It is designed for someone who has never played a modded PC game before, so it tries to avoid making any assumptions, is kept "up-to-date", and covers years of "lessons learned" by a retired Technical Support expert. I recommend anyone read the entire " FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with especially if this is your first attempt to play a modded FNV or it's been more than a year since you last set it up. Also see the " Issue - Vanilla game Hangs on startup", "Cause 1" entry regarding the specific DirectX9 driver need. Please read the "Checklist" entry "Item #6" regarding the 32-bit drivers requirement in the wiki " Fallout NV Mod Conflict Troubleshooting" guide. The game simply hasn't needed that much memory as yet. However, to the contrary: less does not mean it is not working. : Alternatively: if the Windows "Task Manager" indicates the "FalloutNV.exe" program has more than 2GB (2,000,000KB) of "Memory (Private Working Set)", then the 4GB Patcher is in effect. Please see the wiki " Installing Games on Windows Vista " article for details. If that is successfull, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on it's folder if you have moved it, as you are going to have other problems down the road. : If "GetIsLAA" is returning code "1", try running the game from a "Local Administrator" account. ![]() :* 2=successfully allocated extra memory from the patch and is fully working. ![]() :* 1=patch was applied to the executable, but extra memory is not being allocated : The has a function which can be run from the game console (): "GetIsLAA" (not case sensitive). Check the "nvse_steam_loader.log" file (in the game root folder with the FalloutNV.EXE file) for errors. : Look for the "Data\NVSE\NVSE_CONFIG.INI" file which for GOG users will otherwise will not get created without the "nvse_steam_loader". How can you tell if the 4GB Patch is working? The patched game automatically detects and launches NVSE. Revert to the backup copy created if you did run an older version.) Run the patcher once (as "Local Administrator" if necessary) and thereafter just use the default game FalloutNV.EXE (preferred) or FalloutNVLauncher.EXE (re-writes your INI files) as a normal user. The latest version (v1.4 ) now supports the GOG version for auto loading NVSE, and the "NVSE_CONFIG.INI" file does not work for the GOG version without RoyBatty's patch. (Older versions of the tool are deprecated. * Are you using the FNV 4GB Patcher (even with the GOG version)? For FNV Steam users (and now for GOG users as well with v1.4 or later) the tool easily solves the problem of the 2GB memory limit and loading NVSE for both the game and GECK. You then (while logged in as an "Administrator Account") need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. If you did move the game out of the "C:\Program Files(x86)" location, then likely any access privilege problem is one of " File and Folder permissions" on the parent "root" folder under which you installed the games. You can manually create it and move all the NVSE files there from the game folder (where the FalloutNV.EXE file resides). NVSE does work with the GOG version, but still needs to be installed into the "Data\NVSE" folder, which you have to create if your install process does not.
0 Comments
Leave a Reply. |