Why?

Let's be honest here, the engine did not age well. The renderer is based on now 20 year old DirectX 9, which fails to fit-in with modern GPUs and Windows. It's extremely inefficient and CPU bound, has glaring issues with display modes, memory handling and overall stability.
As for Bethesda's code - it also fails (horribly) to scale well with modern CPUs, something that you can see even in their latest titles.
To make things worse, Fallout New Vegas was compiled without compiler optimizations.

In short most performance issues can be summed with two words: CPU bottleneck.

Even with that fact in mind, there are some tweaks to be done on the GPU and presentation side of things that can help with the overall responsiveness of the game, despite not fixing the performance on its own.

Things You Should Know

• Vertical Synchronization (V-Sync) - technology allowing to keep display's scanout and refresh in phase to eliminate screen tearing, at the cost of higher latency.
  (Latency lowers along with refresh rate)
• G-Sync | Freesync - Variable Refresh Rate (VRR) technologies developed by NVIDIA and AMD respectively. They allow the display to adapt its refresh rate to the framerate, allowing to use V-Sync at arbitrary framerates and reduce its latency^[1] .
• Multiplane Overlays (MPOs) - hardware scanout planes for the GPU. They allow for hardware image composition without any latency or performance penalty (for example displaying windows on top of each other), as well as their hardware scaling and stretching. MPOs are supported since Windows 8.1. Hardware capabilities vary between GPU manufacturers.
• Input Latency (lag) - time between input event (mouse click, keyboard press) and the event being displayed on the screen. The lower the latency, the more responsive the game feels.
  There are multiple sources of latency, varying from GPU/ CPU usage, display mode, framerate count and many more - most of them are covered in this guide.

1. Yes, despite popular misinformation, VRR alone doesn't get rid of tearing. It can minimize the rolling tear however, but that varies between displays, and such, it's not a guaranteed feature. Additionally, the latency reduction applies only at framerates below V-Sync window (display's native refresh rate) - if framerate matches the native refresh rate, VRR engages V-Sync emulation.

Rewritten

lStewieAl has made a few of mods focused on improving the engine perfomance in multiple aspects (loading, rendering, AI processing).

Installation

1. If not already downloaded, download lStewieAl's Tweaks and Engine Fixes and install it with your mod manager.

2. If not already downloaded, download Stewie Tweaks Essentials INI and install it with your mod manager.

3. Download lStewieAl's Engine Optimizations and install it with your mod manager.

4. Download Faster Main Menu and install it with your mod manager.

Stutter Remover

New Vegas Tick Fix is a mod by karut that fixes and improves game's internal clocks and memory management, which dramatically reduces stutter. It also allows for playing above 60fps without breaking physics.
Additionally, it has some DirectX changes, which help with performance and greatly reduce memory usage.

Installation

1. If it's not already installed, download NVTF from Nexus and install with your mod manager.

2. Double-click on NVTF in Mod Organizer, then open NVTF.ini in the INI Files tab, and set:

   bModifyDirectXBehavior = 1

   Enables NVTF's DirectX changes.
   It's required for following settings to work:

   • bToggleTripleBuffering = 1

     Enables triple buffer V-Sync, which gets rid of problematic framerate halving on FPS drops/ instability caused by double buffer V-Sync.
     

     This change has no effect if you don't use V-Sync
     The potential latency increase is eliminated by properly capping FPS, which is done later in the guide

   • bUseDefaultPoolForTextures = 1

     Enabled by default
     Disables texture mirroring between VRAM and RAM, which decreases RAM usage. Allows to use high resolution textures.
     It's required if you play at resolutions higher than 1080p.
     

     This change breaks Alt-Tab functionality in Fullscreen Mode.^[6]
     To mitigate that either use DXVK, or Windowed Mode.
     Or just don't Alt-Tab.

6. D3D9 loses the graphics device if it loses the screen ownership (Alt-Tab, Sleep, etc.). To recover, it needs to either have a copy of textures in RAM, or be able to reconstruct the memory from ground up.
   Fallout New Vegas, like most D3D9 games, use the first method. Thus by disabling this behavior, after Alt-Tabbing, game is in a limbo where it doesn't know what to do.
   DXVK fixes this by simply being in place of D3D9, while Windowed mode guarantees the game will never own the screen in the first place.

Driver Updates

Not much to say here - for the best compatibility and performance, you must be using the newest driver for your graphics card.

You can check what GPU you have by opening Task Manager, and going to the Performance tab - the last GPU on the left pane is your main one.
If you don't see any GPU there, that means your GPU is too old to use DXVK.

Select your graphics card to go the driver download page
NVIDIA	AMD	INTEL

Windows Watermark

Make sure your Windows is activated, otherwise the watermark will kick the game into the DWM composition, which leads to increased latency, worse performance and disables VRR.
If you don't have a GPU with MPO (Multiplane Overlay) support, you can mitigate this by disabling Fullscreen Optimizations.
(Keep in mind that this trick won't work on modern, D3D12 games, so it's still recommended to just activate Windows)

How to check if your GPU supports MPOs:

1. Type dxdiag into Windows search
2. Click Save All Information and save the file.
3. Open the DxDiag.txt file, press Ctrl+F and look for MPO MaxPlanes
4. If the number is greater than 1, then your GPU has MPO support.

Virtualization

Windows 11 uses virtualization features to increase system and inter-process security. Unfortunately, this can come at a performance cost, especially on lower-end hardware.
I won't be writing on how to disable them, because... Microsoft already made a tutorial about it.

This step is not mandatory, as when it comes to security, it's up to you to decide. Just letting you know that this exists, and even Microsoft acknowledges the fact that it can degrade perfomance.

Game Mode

Windows 10 introduced a feature called Game Mode, which puts the system in a more gaming-friendly state.

Game Mode features:

• Enables AutoHDR for DXGI based games.
• Enables VRR optimizations for games using Flip Model ^[?].
• Disables Windows Update.
• Disables notifications.
• Disables file indexing, if "Respect Device Power Mode Settings" is enabled in Search settings.
• Sets Game Mode power mode (Requires Balanced power plan to be active).
• Enables CPU scheduling optimizations for Ryzen CPUs.

Game Mode is enabled by default. If you had it disabled for some reason, you can enable it here.

Presentation Problems

Here's a comparison of three display modes you can use in this game. Situation is problematic mainly due to Vulkan and D3D9 using old presentation models.

4. Despite that disabled V-Sync unlocks the framerate, window itself is V-Synced, so you don't get any benefits.
5. While AMD enables Freesync for Fullscreen Windowed BitBlt surfaces, Nvidia allows G-Sync to run with any window.
   This is problematic because refresh rate can get synchronized to wrong windows, framerate may break on other displays and display stutters may occur.
   Enabling it globally is a bad idea, because it disrupts normal desktop usage (e.g. screen can sync to sleeping windows).
   It's recommended to use Nvidia Profile Inspector to set G-Sync Application Mode to "Fullscreen and Windowed" in Fallout - New Vegas profile. This makes Windowed G-Sync run only when the game is running.
   Keep in mind that even with this method, this G-Sync implementation is still buggy - if you get any of the forementioned issues, disable it.
   

   Never enable Windowed G-Sync globally!

Translation Magic

DXVK is an open source Direct3D 9-11 to Vulkan translator project lead by Philip Rebohle (doitsujin) and Joshua Ashton. While created mainly for Linux, works unofficially on Windows.
In short, it allows you to run Fallout using the Vulkan API which has much lower draw call overhead than D3D9, which is one of the main performance limiting factors in this game.

HDR-Mod

HDR-Mod is a DXVK mod made by Lilium (aka EndlesslyFlowering) and me with the intention of adding HDR functionality to D3D9 games. Effectively it does 2 major things:

• Displays the game at bit depth higher than 8.

• Upgrades render targets to 16 bit.

This allows for HDR output and eliminates color banding from the game.
DXVK doesn't perform any HDR tone mapping, so you need to use Pumbo's ReShade AutoHDR or Special K (Nvidia only) for that.

Installation

1. Download the latest DXVK version from Nexus.

   If you have a HDR display, you can select the HDR version.

   GPUs lacking VK 1.3 support or having issues with 2.0, must use the 1.10.3 version.

   Intel GPUs need to use the 1.10.1 version.

2. Extract archive contents into your Fallout New Vegas root folder.

Enabling Flip Model (DXVK with DXGI)

Nvidia's drivers have ability to interop Vulkan to DXGI allowing for Flip Model in Windowed mode, which has HDR and VRR support, and better latency.
Be wary that current implementation of the interop will degrade performance on PCs.

1. Enable Windowed mode in FalloutCustom.ini.

[Display]
bFull Screen=0




It's recommend to use Special K, since it configures the interop automatically and applies other compatiblity fixes.
It also resolves the settings issue mentioned above.

In case you don't want to, or can't use Special K, you can follow the steps below.

2. In Nvidia Control Panel, in 3D Settings, set Vulkan/OpenGL present method to Prefer layered on DXGI Swapchain
   You can use global profile if you want to use Flip Model in all OpenGL and Vulkan titles.

If you don't see those options, then your driver is not up to date!

3. Press Apply changes and exit.
4. Download Nvidia Profile Inspector.
5. Extract the archive and run the program.
6. Enable "Show unknown settings from NVIDIA predefined profiles" in the top bar (penultimate button).
7. Press Ctrl+F and paste OGL_DX_PRESENT_DEBUG.
1. Select the setting and click on Show bit value editor on the top bar (last button).
2. In the first column, check bit #00 and #19.

   These flags enable DXVK support and fix forced promotion to FSE in some games.

3. Click Apply & Close
8. Click Apply changes in the top right and exit.
9. Install OneTweak to disable window borders.

(Not) Pushing the Limits

Limiting framerate is very important for overall stability.
First and foremost, if you are using a good limiter, you'll be implementing correct framepacing, which is the most important think for the overall feel of fluidity.
More advanced limiters can also reduce latency or power consumption (it's difficult to have both).

Recommended Setups

Recommended configurations based on selected display scenarios:

• V-Sync

  • Framerate must be capped slightly below refresh rate to reduce latency.

  V-Sync on its own is NOT a limiter. Using it as one introduces a massive latency penalty.

  This workaround applies only to RTSS and D3D9 Special K.
  (Not needed if you use Special K + DXVK with DXGI)
  
  Driver limiters are not precise enough to pull this off without risking stutter.

• G-Sync | Freesync

  • V-Sync must be enabled, in order to fully get rid of tearing.
  • Framerate must be capped below refresh rate, in order for VRR to not disengage and fallback to V-Sync, as this causes a very big increase in latency.

• No V-Sync

  • No special prerequisites.

So many options...

Limiters presented here are ordered by their precision, from best to acceptable. The better ones are smoother and can provide better latency reductions, but may have some compatibility issues.

Enter your refresh rate here for automatic calculation of FPS limits. You can find your exact refresh rate here.

Click on the cards below to show the instructions for each limiter.

zLag

Game by default uses zLib compression for most things, plugin records included. Unfortunately, zLib is very slow and CPU heavy (especially on modern SSDs), which sadly results in loading stutter, mainly in mods with lots of NPCs or new landscapes.
Luckily, you can very easily decompress any plugin using xEdit and a simple script.

The Process

1. If you don't have xEdit already set up, follow this guide.
2. Press Ctrl+E in MO2 and select the xEdit executable.
3. Add -IKnowIllBreakMyGameWithThis to the Arguments text box.
4. Download the Decompress Records script from Nexus.
5. From the downloaded archive, extract Decompress Records.pas into the Edit Scripts folder contained in the xEdit folder.
6. Run xEdit, then load every plugin.
7. Once the background loader finishes, press Ctrl+A then right-click and Apply script.
8. Type Decompress Records, then apply.

It's recommended to remove the argument line you added in step 3.

Are these questions really frequent?

• I can't use DXVK, and I need to Alt-Tab - am I out of luck?

  Yeah, all you can do is download OneTweak and use the legacy Windowed mode.
  Also enable Windowed mode itself in FalloutCustom.ini (OneTweak itself doesn't change display modes)

  [Display]
  bFull Screen=0

• Why does Special K show D3D11 instead of Vulkan when using DXVK with DXGI?

  The DXGI interop uses D3D11 to display the game, and sometimes Special K can't detect the presence of DXVK due to 3rd party programs.
  It's nothing to worry about, it's purely a visual difference - Special K is running in D3D11 mode regardless of the name you see.

• Any way change brightness in Windowed Mode?

  Use ReShade or Dynavision to change the gamma.

• Do texture mods really have an impact on performance?

  Not directly, no. As long as you don't go over your VRAM budget and use NVTF's memory pool patch you'll be fine. If you run out of VRAM, you'll either crash, or experience massive stutters.
  What is guaranteed from higher resolution textures is increase in their load time. This can translate into longer stutter periods on cell loads.

• You talk about HDR. I thought FNV already had it?

  HDR mentioned in game setting refers to HDR rendering, where game renders lighting passes in 16 bits, instead of 8. This leads to properly glowing lights thanks to the precision of using 65536 colors per channel instead of 256. (Glowing elements won't be clamped anymore, and will glow instead.)
  Due to the old age of the game, this data is later converted to 8 bit SDR (HDR in Windows was added in 2017!). Additionally, D3D9 obviously doesn't support HDR output in the first place, hence the need for the DXGI interop.

• DXVK is breaking HDR after exiting the game!

  Yes, unfortunately due to how FSE works, in addition to lack of native Windows support from DXVK, it doesn't properly handle the HDR API.
  If you have a Nvidia GPU, use DXVK with DXGI (You'll get actual HDR too!). Otherwise, normal Windowed.

• Is dgVoodoo 2 a viable alternative to DXVK?

  No. While it is true that you'd gain Windowed mode with Flip Model and HDR from it, in contrast to DXVK you are guaranteed to get lower perfomance due to the translation overhead.
  If you can handle the performance loss, sure go ahead.

• Is it possible to use D3D9Ex in Fallout New Vegas?

  Technically yes - Fallout New Vegas, oddly enough is the only Bethesda title with native D3D9Ex support. Does it work well? Not really.
  While Special K's D3D9Ex enforcement works far better that NVTF's, it still suffers from CPU perfomance loss and increased GPU usage.
  

The End?

Congratulations! You've made it through! I hope this guide has helped you making Fallout New Vegas a smoother experience.
If you have any issues, questions, critiques or recommendations hit us up on Discord - wall_sogb and VishVadeva.
You can also find us on ModdingLinked, xNVSE, Tale of Two Wastelands servers.

I recommend checking this guide from time to time - We're not done yet.

If you found this guide helpful, share it with others or support me on Ko-Fi or Patreon

Things worth reading

Here are some links to stuff that I recommend checking out:

• Salamand3r's Texture Guide - nice and easy to follow texture guide by Salamand3r that actually doesn't break your game for a nice change of pace.
• PCGamingWiki - Great website, contains really helpful info about games, patches, fixes and other PC gaming related stuff.
• BlurBusters - Amazing website by Mark Rejhon focused on displays, latency and image quality. Really worth checking it out if you are a geek for these things.

Credits

This is the part where I'd like to thank people who have helped me in whatever way making this guide possible.

• Whole xNVSE server for being a great community. Especially:
  • VishVadeva - for testing and helping with benchmarks
  • c6 - for fixing the some engine functions so my testing could be easier
  • LOC (aka ItsMeJesusHChrist) - for making the awesome logo for the guide
  • Nice try karut, but you are not getting credited
• Whole Special K server for also being a superb community with a lot of knowledgeable people. This guide would literally not exist without them.
• Glaceon575 - for helping with benchmarks and providing screenshots for AMD GPUs
• You

Changelog

Changes are documented on the commit history