Jump to content
  • 0
Rescorla

4GB patch apparently didn't work

Question

I followed the guide and ran the 4GB patcher. I am on my first playthrough of FNV and typically only play for about 60-90 minutes per session. Started getting Out of Memory messages when I play for over 90 minutes. Checked task manager and the FNV executable is still running using 2GBs of memory. Pretty clear indication that the 4GB patcher didn't work.

 

This far into the game (I'm level 22) can I just download the 4GB executable file and start using that or should I rerun the 4GB patcher and try to fix it? Is there some way for me to verify the 4 GB patcher actually worked?

Share this post


Link to post
Share on other sites

14 answers to this question

Recommended Posts

  • 0

Yes, set it to 0. Turn it off completely. It's does NOT work properly. It will cause more problems than it solves.

Share this post


Link to post
Share on other sites
  • 0

The easiest indicator that the 4Gb patch has worked is to call up the console and type:

GetNVSEVersion

Since the new patched game executable will now call NVSE automatically, this will show you that NVSE is running even though you start the game now by running the game, not the launcher or NVSE.

Share this post


Link to post
Share on other sites
  • 0

Just to add: NVSE Memory tweaks got ported over from Skyrim.  \Fallout\Data\NVSE\NVSE.ini and add the Memory tweaks.  There is an Alternative to the old 4GB Patch over at the Nexus.  Recently, like you, I had the same problem.  Purple Textures...running out of memory.  Did both of these and im right as Rain :)  Never had a problem w/ the old 4GB patch.  But if I were you I would def. try the NVSE tweak :) Check the Fear & Loathing Guide under NVSE.

Share this post


Link to post
Share on other sites
  • 0

The easiest indicator that the 4Gb patch has worked is to call up the console and type:

 

GetNVSEVersion
Since the new patched game executable will now call NVSE automatically, this will show you that NVSE is running even though you start the game now by running the game, not the launcher or NVSE.

I get a value of 5 when I run that command.

Share this post


Link to post
Share on other sites
  • 0

If you run the game from the default exe and you can still see the NVSE version this shows you it has been patched. Ordinarily you would need to run the game from the NVSE loader, this new patcher removes that necessity.

Share this post


Link to post
Share on other sites
  • 0

If you run the game from the default exe and you can still see the NVSE version this shows you it has been patched. Ordinarily you would need to run the game from the NVSE loader, this new patcher removes that necessity.

Something screwy is going on then. I reran the 4GB patcher again making sure I ran it as an administrator. Got a message the game had already been patched. Kept on getting "Out of Memory" errors. I downloaded the 4GB .exe and launched the game with it. Still running out of memory around 2GB.

Share this post


Link to post
Share on other sites
  • 0

What are you using to measure memory? Task Manager doesn't really show more than 2GB even if you are at the limit. 

Share this post


Link to post
Share on other sites
  • 0

I'm just using Task Manager.

 

Here is latest example of the problem. I'm on the quest to unearth the Legion spy at Camp McCarron. On fresh computer bootup and launch of the game I exit McCarron airport, go to the control tower, and then go back inside McCarron airport on my way to the monorail. Upon trying to go back inside the airport my game locked up due to being out of memory. I ran out of memory in less than 10 minutes of playing the game.

Share this post


Link to post
Share on other sites
  • 0

Do you have Heap Replacement turned on in the New Vegas Stutter Remover .ini file? If so, this will surely cause crashes and out of memory issues. It's broken. 

Share this post


Link to post
Share on other sites
  • 0

Do you have Heap Replacement turned on in the New Vegas Stutter Remover .ini file? If so, this will surely cause crashes and out of memory issues. It's broken. 

This is what the guide says:

 

bReplaceHeap = 1 <-- Needed for heap replacement, only for advanced users, detailed info in the readme. Modern systems will want to make use of this so it is recommended to enable this.

 

Are you saying I should set this to 0?

Share this post


Link to post
Share on other sites
  • 0

What have you set iHeapSize to? Default is only 250, trying a different number may help.

Share this post


Link to post
Share on other sites
  • 0

What have you set iHeapSize to? Default is only 250, trying a different number may help.

I have it set to 450 like the guide says.

Share this post


Link to post
Share on other sites
  • 0

Yes, set it to 0. Turn it off completely. It's does NOT work properly. It will cause more problems than it solves.

Changed it to 0 last night and stopped getting "Out of Memory" errors even after playing for over an hour. Hopefully that INI setting was the culprit.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Majorman
      Discussion topic:
      FNVLODGen by zilav
      Wiki Link
    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 85 - based on 4.1.4
      Unzip into a dedicated folder outside of any game and Steam folders or special Windows folders like Program Files.
      (Pro users can merge with existing xEdit installation. Make sure to overwrite older LODGen.exe/LODGenx64.exe TexConv.exe/TexConvx64.exe in Edit Scripts. All other files with the same filenames are the same as the latest version of xEdit.)
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder.
      Do not generate into any game or any mod manager folders.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By Majorman
      Discussion topic:
      ShowOff NVSE Plugin by The Dormies - Demorome and Trooper
      Wiki Link
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.