BlackBirdLT Posted March 13, 2015 Share Posted March 13, 2015 I get problems when my heavily modified FNV reaches up to 3.2-3.3GB, according to the Task Manager. Most of it probably comes from the Increased Wasteland Spawns. It freezes, crashes or crashes and gives "Out of memory" error. I am using a 4GB Loader, which, I assume should give me a little bit more usage. Using cell purging helps but just a little. Is there any way to squeeze more memory from the game or should I tone down with mods? My memory should not be an issue as I have 16GB RAM. Link to comment Share on other sites More sharing options...
RoyBatterian Posted March 13, 2015 Share Posted March 13, 2015 IWS is known to be buggy and cause crashes, it may have nothing to do with ram limits. Try NVSE's version of Sheson's initial heap replacer, there's instructions in the read me how to enable it. Link to comment Share on other sites More sharing options...
Athelbras Posted March 13, 2015 Share Posted March 13, 2015 (edited) You are probably at the point where you need to remove less important mods and/or choose less demanding (lower resolution) texture mods. But try Roy's suggestion - it may help you squeeze out a bit more. Since crashes usually occur at around 1.4 GB and above for normal game play, your 3+ when using the 4 GB Loader is much better than "a little bit more usage". You are actually doing quite well. If you are not yet using NVAC, that can potentially keep you going in situations where you would otherwise experience a crash. See: NVAC - New Vegas Anti Crash by Queue. Note that physical memory (RAM) isn't relevant. The issues involve "virtual memory" usage, which for a 32-bit game like FNV is strictly limited to 4 GB max. Meaning what you are experiencing with regard to crashes would be the same whether you had 2 GB of RAM or 24 GB of RAM; the amount of RAM influences game play performance. Also note that Task Manager does not present a complete picture with regard to the game's currently active memory usage, so you won't ever actually see a full 4 GB in use; various underlying system services are not taken into account in the display even though they are consuming portions of that 4 GB of virtual memory. Edited March 13, 2015 by Athelbras Link to comment Share on other sites More sharing options...
Recommended Posts