Jump to content
  • 0

Awuful performance in New Vegas


Hey Guys, Audley here! This is going to be a bit of a long post due to me having to explain what I have worked through. So please bear with me. And I would like to thank you in advance for any help in this matter.


First off, let me get my specs out of the way:


i5 4670 @ 3.4 (Stock; no OC)

GTX 760 SC (No further OC)


60hz 1920x1080 Monitor

Windows 8.1 64 bit


So in a nutshell: I get frame drops nearly constantly throughout the game. This makes the game very uncomfortable to play. I have spent a lot of time trying to play the game and trying to mod it but I have never actually played the game all the way through. I follow F&L pretty much down to the letter. With a few exceptions for personal taste. However, I have tried to play the game completely vanilla and I keep having the same bad performance. I have spent about 50 hours trying to play in short bursts but I always end up getting frustrated over the performance issues. So right now I am stuck after you leave Goodsprings because I am about ready to give up on trying. I have spent a lot of time testing some mods and stuff but sitting down to enjoy the game for an hour or more at a time is a nightmare. I used to own the game on my Xbox and even at 30 fps it was much more fun to play than on my computer. I would probably just play it on there if I hadn't have sold it.


So let me go into a bit more detail. In several locations in the game my FPS goes from a solid and smooth 60 FPS to around 40. Sometimes even dipping to around 30. But only for about five seconds or so. Then the game goes back up to 60 again. This would probably be more accurately described as "hitching" or "jerking" or maybe even "macro-stuttering" but not micro-stuttering. When the game does decide to be smooth, it is fine. But when I walk around and the game is loading into another cell, or when I am around NPC's, my fps goes all wack. It's almost as though my rig isn't quite powerful enough to run the game. But in theory I should be fine.


Now, the obvious solution would be to turn down my settings or cap my frame rate. However, regardless of visual detail this happens. Even on the lowest settings, with all the sliders set to the lowest they will go, I still have slowdowns. With AA off, with AF off, with or without HDR, even with V-Sync off this still occurs. Even capping my frame rate to 30 this still happens. Regardless of settings, this hitching issue still occurs.


I was beginning to think it was my hardware. But I have been able to run several games at 1080p 60 fps with zero issues. The only known solution I have to somewhat solving this problem is to set my resolution to 720p. But it doesn't get rid of it completely. It only lessens the drop. But the jerkiness is still there; when your game goes suddenly from 60 to 40 and back again all in about 5 seconds.


I got to tell you it is a real bummer. So let us recap: Vanilla game, default .ini files, default settings, I get FPS drops all around. Fully modded game following F&L I get fps drops. This makes me think I have some sort of bottleneck going on with the game but I have no idea what it could be. I have scoured forums like a maniac trying to find a solution. I have posted similar posts on the bethsoft and Nexus forums but with little success.


If I cannot find a solution for this then I may give up on modding and just save up to buy another Xbox. If anyone has any ideas about what might be causing my performance issues then I am all ears.


Cheers, audley


Share this post

Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0

It will always be difficult to diagnose without having the computer in front of me, but I'll try giving it a go.

  • Have you gone through NVidia inspector and added FalloutMO.exe and FNV4GB.exe to your profile, and set Multi-display/mixed-GPU acceleration: Single display performance mode and set Power Managment Mode: Prefer amximum performance  ?
  • Have you tried MultithreadedAI=1? I have found it adds no instability and the author of FNV4GB.exe finds the same.  This should help with AI heavy areas
  • Have you tried switching from v2.0a to v3.0 shaders? Open Renderinfo.txt in your my documents\my games\falloutnv\ folder.  There will be a line for Shader Package: [Number]  Now go to you Data/Shaders/ folder, and renambe shaderpackage[number].sdp to shaderpackage[number].sdp_backup.  Make a copy of shaderpackage019.sdp and rename it to shaderpackage[number].sdp In your inis. set bAllow30Shaders=1.
  • When the FPS drops occur is there alot of noise? Have you tried upgrading the Vorbis engine?

Also, do you have NVidia Geforce Experience? It has been known to cause issues with certain games including both Fallouts.


Also 2, when you say vanilla, is that still with the utilizties such as 4GB, NVAC, NVSR?


EDIT: Added 3.0 shaders tweak ini line.

Edited by Adonis_VII
  • Upvote 1

Share this post

Link to post
Share on other sites
  • 0

hey Adonis! Thanks for the reply. Sorry I couldn't get back to you earlier; had a busy day. 


Anyways, I noticed that I did indeed have Geforce Experience still installed from when I was using it to do some recording. However, since I did not use it anymore I went ahead and uninstalled it. And you were definitely right on that one. I was startled at just how much of a performance boost I got from uninstalling it! A significant amount of hitching went away. While it is still not perfect, the game went from being barely playable to being a lot more comfortable. 


I suppose it did make a substantial difference as I was able to play for about an hour. While the frame drops can be annoying at times, the game is a lot more playable for certain. I think that the Geforce Experience was causing me most of my issues. 


Then, while I was skulking around on some forums wondering if I could perhaps boost my performance anymore, I saw that one guy was having problems with the Full Scene Reflections option turned on. Even near areas without water. So me not wanting to rule anything out, I turned it off. And to my amazement about 90% of the fps problems went away. I never thought to check this option since I didn't think it would affect areas without water. 


My game is running at a smooth 50-60 fps with Adaptive V-sync turned on and I only get frame drops in a few areas of the game like the strip. I even managed to get Enhanced Shaders up and running. Overall I am pretty happy with the performance. 


Thanks a lot for the help Adonis. Hopefully someone can find this thread in the future and perhaps see that Geforce Experience was causing their game issues. I did try your suggestions and none of them made a real difference except the first one; which I now run with.


Cheers, Audley

  • Upvote 1

Share this post

Link to post
Share on other sites
  • 0

Yea, it really depends on what your bottleneck as to which of those changes will effect your game.  I'm glad I could help though.  I plan on making a FAQ/Troubleshooting page at some point for FNV with some of these as different people have issues with different parts of the engine.

  • Upvote 1

Share this post

Link to post
Share on other sites
  • 0


  • Have you tried switching from v2.0a to v3.0 shaders? Open Renderinfo.txt in your my documents\my games\falloutnv\ folder.  There will be a line for Shader Package: [Number]  Now go to you Data/Shaders/ folder, and renambe shaderpackage[number].sdp to shaderpackage[number].sdp_backup.  Make a copy of shaderpackage019.sdp and rename it to shaderpackage[number].sdp

Is this required also in one of the .ini files?: bAllow30Shaders=1


EDIT: And are you suggesting that you are supposed to change the "[Number]" in Renderinfo.txt from "13" (that's what my number says) to "19" (will doing that actually affect anything)?  Or are you supposed to change the shaderpackage019.sdp filename to "shaderpackage013.sdp" (or whatever number was listed in the Renderinfo.txt file)?  I'm confused with your instructions.


EDIT2: I've read that the game engine does not support v3 shaders and that it's not a good idea to try to enable them because it will end up with missing textures: https://www.techpowerup.com/forums/threads/fallout-new-vegas.122096/page-21#post-2071871  Is this true or not?

Share this post

Link to post
Share on other sites
  • 0

Also, do you have NVidia Geforce Experience? It has been known to cause issues with certain games including both Fallouts.


Would simply exiting the program, GE Force Experience (GEFE), before running the game suffice?  Also, does this affect the game even if you have GEFE installed and running in the background, but don't launch the game through GEFE or select to optimize the game through GEFE (I have a message in GEFE for FNV that says "Game is not optimized").  I had assumed that GEFE was thus not doing anything to the game.  Same goes for Skyrim, which is also recognized by GEFE.

Share this post

Link to post
Share on other sites
  • 0

Yes, I missed that important part about changing the ini file. I suggest changing the number of the actual shader package, not in renderinfo.txt as renderinfo.txt can be rewritten.  Those d3d9.dll fixes for New Vegas that used to be all the rage were actually hard codding the shaderpackage path to choose 19. Again though, it depends on your computer, as some people get large improvements in fps, and some don't.


I have not tested exiting the process vs uninstalling in regards to performance.  The hit for me is much smaller than for others, as again its rather hit or miss if it wrecks a game or not, which makes it difficult to convince them to fix.

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 Drak
      Hello There,
      I did a fresh install following STEP recommandations (FNV not in program files, modding directory neither, I started FNV after installing it).
      I can start the game with all mods from STEP except Step Patch - Conflict Resolution.

      I tryied to pinpoint my problem and as soon as I add the Step patch (then LOOT order dirladada) I get the following error in 
      nvac.log :
      23190643 _ NewVegasAntiCrash FalloutNV.exe
      23190643 _ 17E90000 07050000 nvac.dll
      23190643 i 008BFBC1 0441B60F FalloutNV.exe
      23190643 _ 17AE0000 06020050 nvse_1_4.dll
      23190643 _ 77170000 0A004A64 ntdll.dll
      23190646 a 0072607A 0048A1DF FalloutNV.exe
      23190647 h 181A42EB 8B48088B nvse_stewie_tweaks.dll (100342EB)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42EE 8B01FF10 nvse_stewie_tweaks.dll (100342EE)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 h 181A42F0 FF1068F0 nvse_stewie_tweaks.dll (100342F0)
      23190647 ^ 0076E223 00000004 FalloutNV.exe
      23190647 m 000003EC 219C46E0
      23190647 r 10001432 00000009 d3dx9_38.dll (10001432)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E0 834104FF d3dx9_38.dll (100034E0)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 h 100034E6 C7010000 d3dx9_38.dll (100034E6)
      23190647 ^ 0045CEF5 0000000D FalloutNV.exe
      23190647 u 00F0B4FA C0000409 FalloutNV.exe
      23190647 ! CRASHSAV E_FAIL_0 FalloutNV.exe
      23190648 q 00F0B4FA C0000409 FalloutNV.exe
      23190648 ! CRASHSAV E_FAIL_0 FalloutNV.exe
      I also tryed to use Cobb Crash Logger 
      Cobb Crash Logger Version 3.0.0, build 0.
      If this file is empty, then your game didn't crash! Probably!
      Exception C0000409 caught!
      0x00F0B4FA ==> EntryPoint+0xFFFFFFFF in FalloutNV (0x0019F138) 
      0x771F88B4 ==> RtlInterlockedCompareExchange64+0x1B4 in ntdll (0x0019F204) 
      0x771E4EE6 ==> KiUserExceptionDispatcher+0x26 in ntdll (0x0019F208) 
      0x0019F21C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F20C)
      0x0019F26C ==> ¯\(°_o)/¯ (Corrupt stack or heap?)  (0x0019F21C)
      GAME CRASHED AT INSTRUCTION Base+0x00B0B4FA IN MODULE: C:\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
      Please note that this does not automatically mean that that module is responsible. 
      It may have been supplied bad data or program state as the result of an issue in 
      the base game or a different DLL.
      Help welcome, I am at a loss..
    • By z929669
      Step Fallout: New Vegas Guide 1.0.0 released!

      Guide Link | Changelog | Feedback & Bug Reports
      Nexus Link
      Many thanks to @Majorman for working on this guide for the past 6 weeks as our official FNV guide Curator!
    • 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
      xLODGen beta 86 - based on 4.1.4b
      Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.
      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.
      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.
      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.
      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.
  • 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.