The game simply hasn't needed that much memory as yet.New Vegas Stutter Remover: Irreparably broken by Windows 10 due to relying on undefined behavior. However, to the contrary: less does not mean it is not working. Please see the wiki " Installing Games on Windows Vista+" article for details.Īlternatively: 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. If that is successful, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on the folder you moved it to, 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 How can you tell if the 4GB Patch (for Steam) is working? The JIP LN NVSE Plugin (recommended for everyone) has a function which can be run from the console: "GetIsLAA" (not case sensitive). But being below that threshold doesn't mean it isn't.) (If the Windows ("Task Manager" | Processes) tab entry for the game process has more than 2GB (2,097,152KB) "Memory(Private Working Set)" used, then the 4GB patch is definitely in effect. Won't hurt and it will tell you if it is already patched. If you aren't sure if it was installed or working, just re-run the Patcher again. If not using the 4GB Patcher, please see the ' Maximizing use of memory' section of the " FNV General Mod Use Advice" article. (In which case you can just set the "game" link to use CM.) Revert to the backup copy created if you did run it.) Then it (the 4GB patched game executable) will take care of starting NVSE automatically for you.
* Are you using the 4GB Patcher with the Steam version? (DO NOT use it with the GOG version, which is already patched. (If the manager uses a shortcut for the game, then you can configure the shortcut to use CM.) Then launch the game from a shortcut or "mod manager".) If instead you are launching the game from within a "mod manager", then that manager has to be in CM or it's method of starting the game has to use it. You have to run the Steam Client, but do so in "offline" mode. If you are starting the game from within the Steam Client, then that Client has to be in CM. How you launch the game determines the "client shell" environment for all the related programs (such as NVSE) working with it. But let's assume for some reason you still need to use it. They resolved that problem with an update last year.
An "up-to-date" Win10 should not need "compatibility mode" (CM).
0 kommentar(er)
