Red Dead Redemption 2 PC Stutter and Low FPS Explained: Fix the Living Frontier Load First, Then Use Vulkan vs DX12 and DLSS/FSR Correctly

Short answer: If Red Dead Redemption 2 stutters on a good PC, your GPU is rarely the first problem. Rockstar's RAGE engine is streaming a living 1899 frontier at horse speed, running volumetric fog and pre-calculated global illumination on top, and juggling Vulkan vs DirectX 12 plus online sync. Fix storage, frame cap, and API choice first, cut volumetrics and shadows second, then let DLSS or FSR do their real job.

This guide covers PC Windows, Red Dead Redemption 2 after the November 5, 2019 Windows release. It does not cover PlayStation 4 / Xbox One, Stadia, Red Dead Redemption 1, or GTA V Enhanced. Online notes refer to Red Dead Online, not GTA Online.

What RDR2 actually is on PC

Red Dead Redemption 2 is a 2018 action-adventure game developed and published by Rockstar Games, the third entry in the Red Dead series and a prequel to the 2010 Red Dead Redemption. The story follows Arthur Morgan in a fictionalized United States in 1899, played in first- or third-person in an open world with shootouts, robberies, hunting, horseback riding, NPC interaction, and an honor rating plus a bounty system for crimes Red Dead Redemption 2 on Wikipedia.

The release split matters for PC troubleshooting:

• PlayStation 4 and Xbox One on October 26, 2018; Windows and Stadia in November 2019, with Windows on November 5, 2019 and Stadia on November 19, 2019 Red Dead Redemption 2 on Wikipedia.
• Engine is RAGE across those platforms Red Dead Redemption 2 on Wikipedia.
• Red Dead Online lets up to 32 players join cooperative and competitive modes Red Dead Redemption 2 on Wikipedia.
• It is the third-best-selling video game with over 87 million copies shipped Red Dead Redemption 2 on Wikipedia.

RAGE itself explains why the PC version is heavier than its console age suggests. RAGE is Rockstar's proprietary engine from the RAGE Technology Group division of Rockstar San Diego, using Euphoria for character animation and Bullet for physics RAGE engine on Wikipedia. For Red Dead Redemption 2 in 2018 it was refined to support physically based rendering, volumetric clouds and fog, and pre-calculated global illumination, plus a Vulkan renderer in the Windows version in addition to DirectX 12 RAGE engine on Wikipedia. The Euphoria engine was overhauled for advanced AI, physics, and animations, HDR support was added in May 2019, and support for NVIDIA DLSS and AMD FSR were added in July 2021 and September 2022 respectively RAGE engine on Wikipedia.

In other words: RDR2 on PC is not a 2018 console port with a resolution slider. It is a realism-simulation build with two graphics APIs and two upscalers grafted on years after launch.

Why a good PC still stutters: three loads, not one

Most fix guides treat RDR2 like any shooter: lower everything, turn on DLSS, done. That misses the actual stress pattern, which English search suggestions confirm. Players search for red dead redemption 2 stuttering fix, rdr2 stutter fix reddit, red dead redemption 2 best settings pc, red dead redemption 2 pc optimized settings, and crucially red dead redemption 2 vulkan vs dx12, vulkan or dx12, and rdr2 vulkan vs dx12 reddit. Driving-speed complaints in GTA become horse-speed complaints here, plus API-choice arguments.

Here is the order that matches those complaints:

1. Frontier streaming at horse speed

When you gallop from Valentine to Saint Denis, RAGE must stream terrain, trees, towns, wildlife, NPCs, lawmen, and LOD swaps continuously. Walk the same route and stutter often drops. Gallop through Saint Denis at night and it returns. That is streaming and simulation, not shaders.

Rockstar's own minimum PC requirements underline how old the storage assumption is: Windows 10, Intel Core i5-2500K or AMD FX-6300, 8GB memory, NVIDIA GTX 770 or AMD R9 280, and 150GB HDD space Rockstar Support for Red Dead Redemption 2. A 150GB game on HDD that was designed for HDD in 2019 behaves very differently on a modern SSD, and a nearly full SSD behaves like a tired HDD.

Tell: Stutter spikes while galloping, fast-traveling, or spinning the camera fast in towns, but standing still in camp is smooth.

2. Volumetric light and reflection tax

RDR2's signature cost is not a single sun shadow. It is volumetric clouds and fog plus pre-calculated global illumination plus water reflections and long tree shadows RAGE engine on Wikipedia. That cost never sleeps, even when you stare at a swamp.

This is why turning down textures alone rarely fixes RDR2. Textures cost VRAM. Volumetrics cost frame pacing.

Tell: Low FPS in swamps, foggy mornings, heavy rain, and Saint Denis at night, fans loud while nothing much moves.

3. API plus VRAM plus Online sync

The Windows version offers both Vulkan and DirectX 12 RAGE engine on Wikipedia. PCGamingWiki documents the consequence directly in its issue headings: a major stuttering and frame-pacing issue with Vulkan on NVIDIA, and a separate Vulkan video-memory leak when ReBAR is enabled RDR2 on PCGamingWiki. Rockstar's support page for RDR2 on PC crashing with ERR_GFX_STATE lists updating drivers, changing graphics API, and disabling fullscreen optimization among the troubleshooting methods Rockstar Support for Red Dead Redemption 2.

Add Red Dead Online's up-to-32-player sync Red Dead Redemption 2 on Wikipedia and a nearly full VRAM pool from Ultra textures, and a good GPU waits on a busy CPU, driver, and SSD.

Tell: Story Mode is smoother than a full Online lobby on the same settings, or Vulkan hitches while DX12 holds on the same NVIDIA card (or vice versa on a different vendor/driver).

Get this order wrong and you will do what many players do: enable DLSS first, keep volumetrics on Ultra, keep Vulkan on a driver that hates it, and wonder why a higher FPS counter still hitches every few seconds.

The fix order that actually works

Do this in order. Stop when smooth enough.

Step 0: Put the game in the right place

• Install on an SSD with 30GB+ free beyond the 150GB footprint Rockstar Support for Red Dead Redemption 2. HDD turns every gallop into a hitch parade.
• Update GPU drivers, then restart. Do this before judging Vulkan vs DX12. An old driver makes the API test meaningless.
• Note your config path for backup: %USERPROFILE%\Documents\Rockstar Games\Red Dead Redemption 2\Settings\ RDR2 on PCGamingWiki. Back it up before hand-editing. Save data lives under Profiles\<user-id>\ in the same parent folder with one autosave plus 15 manual slots RDR2 on PCGamingWiki.

Step 1: Warm up and cap before you judge

• Load into Story Mode, ride one full loop around Valentine plus a Saint Denis pass, then check performance. First-load hitches are not your final result.
• Cap FPS. Use the in-game frame limiter or half-refresh V-Sync if you see micro-tears on 144Hz+ monitors. An uncapped 120 fps camp that collapses to 45 fps in Saint Denis feels worse than a locked 60 fps.
• Turn off extra overlays, browser video, and recording for the test run.

Step 2: Pick Vulkan vs DX12 by test, not by loyalty

Vulkan is a cross-platform industry standard enabling developers to target a wide range of devices with the same graphics API Vulkan home. Direct3D 12 provides an API and platform that allows apps to take advantage of graphics and computing capabilities of PCs equipped with one or more Direct3D 12-compatible GPUs Direct3D 12 graphics.

Practical test for RDR2:

• Try DX12 first on NVIDIA, especially if you see Vulkan frame-pacing hitches. PCGamingWiki's Vulkan-on-NVIDIA stutter heading exists for a reason RDR2 on PCGamingWiki.
• Try Vulkan on AMD or older CPUs if DX12 stutters in towns. Some systems do run smoother on Vulkan.
• If you get ERR_GFX_STATE crashes, Rockstar lists changing graphics API as part of the fix alongside driver updates and disabling fullscreen optimization Rockstar Support for Red Dead Redemption 2. Switch API, re-test the same ride, keep the smoother one.
• If you use ReBAR / Smart Access Memory and see growing VRAM use on Vulkan, test with ReBAR off. PCGamingWiki flags a Vulkan VRAM leak when ReBAR is enabled RDR2 on PCGamingWiki.

Do not copy a Reddit vulkan vs dx12 winner blindly. The winner depends on vendor, driver age, and ReBAR state.

Step 3: Cut frontier costs first

Lower in this order, testing the same gallop after each group:

1. Volumetrics / volumetric lighting and fog to Medium or Low. This is the biggest RDR2 lever because of those volumetric clouds and fog values RAGE engine on Wikipedia.
2. Water reflections and water physics down one notch. Rivers and swamps punish this disproportionately.
3. Grass, trees, and distant shadows down one notch. Forest gallops and town approaches stream these constantly.
4. Shadow quality and ambient occlusion to High instead of Ultra. Shadows double work during crowded Saint Denis scenes.
5. Particle quality and TAA sharpening down if gunfights in smoke still hitch.

Keep textures at High if you have 8GB+ VRAM. Blurry textures hide nothing about stutter and can increase streaming churn if the game swaps mips aggressively.

Step 4: Pick DLSS or FSR by GPU, not by hype

RDR2 added DLSS in July 2021 and FSR in September 2022 RAGE engine on Wikipedia. Use them correctly:

NVIDIA describes DLSS Super Resolution as boosting performance by using AI to output higher-resolution frames from lower-resolution input, sampling multiple lower-resolution images and using motion data and feedback from prior frames, with a second-generation Transformer model for stability and clarity NVIDIA DLSS Technology.

AMD describes FidelityFX Super Resolution as an open-source high-quality solution for producing high-resolution frames from lower-resolution inputs, with emphasis on high-quality edges AMD FSR on GPUOpen. It exposes four quality modes — Ultra Quality, Quality, Balanced, Performance — varying the scaling ratio AMD FSR on GPUOpen, and supports DirectX 12, DirectX 11, and Vulkan AMD FSR on GPUOpen.

Use it like this for RDR2:

• RTX GPU: DLSS Super Resolution Quality at 1440p, Balanced at 4K. DLSS runs on RTX 20/30/40/50 for Super Resolution NVIDIA DLSS Technology.
• AMD / Intel / older NVIDIA: FSR Quality. Avoid Performance unless you must, because it softens distant riders and pelts you need to read while hunting.
• 1080p: Prefer Quality over Balanced. Ultra Performance at 1080p looks soft on Arthur's coat and horse manes.
• RDR2 has no native Frame Generation or Reflex toggle. Do not hunt for them. If you force frame generation in driver software, treat it as an experiment, not a fix. Fix SSD, API, and volumetrics first.

Do not use an upscaler to hide streaming hitches. It helps GPU-bound vistas, but a storage hitch becomes a smoother-looking freeze.

Step 5: Fix the two special RDR2 stutters

• ERR_GFX_STATE crash on launch or in missions: Update drivers, switch Vulkan/DX12, disable fullscreen optimization per Rockstar's troubleshooting list Rockstar Support for Red Dead Redemption 2. Test Story Mode before Online to isolate lobby load.
• Online-only stutter: Test a solo / invite-only session. If solo is smooth and a crowded lobby is not, your settings are fine — the 32-player sync load is the difference Red Dead Redemption 2 on Wikipedia. Lower population-sensitive settings rather than textures.
• HDR washed-out plus hitch: RDR2 gained HDR support in May 2019 RAGE engine on Wikipedia. If Windows HDR plus in-game HDR double-tonemap, test with one off. A wrong HDR chain looks like a performance bug but is really a color pipeline bug.

My take: RDR2 is a ledger, not a painting — and your horse is a graphics setting

Here is where I depart from most optimization guides, and I label this as interpretation, not Rockstar fact.

Most guides describe RDR2 like wall paint: prettier walls cost more paint. I think RDR2 is better understood as a frontier ledger. Every rabbit, carcass, pelt, horse bond level, honor tick, bounty poster, camp supply, and shop stock is background bookkeeping that charges CPU and SSD even when you stare at the sky. Volumetrics and shadows are the visible paint, but the ledger is why Saint Denis hitches while an empty desert vista holds.

That explains the most common paradox in the search data: stuttering on high end pc. A high-end GPU pays the paint bill easily but still queues at the ledger — streaming new ledger pages at gallop speed while lighting them volumetrically.

Three corollaries I have not seen stated clearly elsewhere:

1. Horse speed is a graphics setting. Dropping from a full gallop to a canter through Saint Denis on the same Ultra settings often improves frame pacing more than dropping one shadow notch, because you lower ledger-page arrival rate. If you must gallop, budget one extra volumetrics notch down.
2. Hunting taxes more than shooting. A gunfight reuses the same block. Hunting adds animal AI, carcass persistence, pelt-quality rolls tied to weapon and shot placement, rot timers, and predators attracted to the carcass. If hunting hitches but Valentine shootouts do not, you found ledger load, not aim load.
3. Vulkan vs DX12 is a dialect, not a winner. The same RDR2 build speaks two driver dialects RAGE engine on Wikipedia. NVIDIA drivers historically stutter more on the Vulkan dialect in this game RDR2 on PCGamingWiki, but that does not make DX12 universally better. Test both on your vendor and driver, with ReBAR noted.

I leave three open questions I cannot resolve without frame-time captures and Rockstar telemetry, and I will not fake them:

• How much of the Saint Denis gallop hitch is SSD streaming vs volumetric lighting vs Online script events?
• Does ReBAR on/off change the optimal Vulkan vs DX12 pick on current NVIDIA drivers versus launch-era drivers?
• Does capping to 60 fps beat uncapped DLSS for Dead Eye timing consistency in full Online lobbies?

You do not need those answers to get smooth today. Fix storage, cap, API, then volumetrics, then upscale.

Practice gunfights without paying the ledger

While you tune RDR2, you can isolate trigger and melee timing in a browser so you are not learning aim during a stutter test.

If your weakness is cover shooting — peeking late, overexposing, losing track of multiple angles — Hazmob FPS: Online Shooter is the cleaner drill. It is a browser FPS with Quick Battle matchmaking and Custom Match private lobbies, seven documented modes from Team Deathmatch to Gun Race, and standard WASD plus G to pick up dropped guns and P for settings Hazmob FPS: Online Shooter. Its arsenal covers 55+ customizable weapons across SMG, assault, shotgun, sniper, and LMG categories. Those same habits — trade kills with a teammate, take cover after each fight, avoid running into the middle at low health — transfer to RDR2 gang hideouts without touching your RDR2 settings.

If your fights fail up close in saloons and camps, the issue is often melee rhythm, not guns. Iron Snout puts you centered as a martial-arts pig with wolves rushing from left and right, attacking with arrow keys for left/right punches, up for jump and uppercut, and down for duck and low kicks Iron Snout. Its guide stresses staying centered, alternating left-right rhythm instead of mashing one side, and dealing with thrown projectiles first before cleaning up the nearest wolf Iron Snout. Ten minutes there before an RDR2 session is a better warm-up than staring at a settings menu.

Neither replaces RDR2. They let you separate aim and timing practice from PC troubleshooting.

Quick settings cheat sheet

• SSD with headroom + updated drivers + Story Mode warm-up ride
• Cap FPS to monitor / 60 fps if towns collapse from high camp FPS
• Test Vulkan vs DX12 on your GPU, note ReBAR state, keep the smoother API
• Volumetrics down first, then water, grass/trees, shadows
• DLSS Quality (RTX) or FSR Quality (others), no native Frame Generation to rescue a 30 fps base
• Test night Saint Denis gallop plus full Online lobby before calling it fixed
• Backup Red Dead Redemption 2\Settings\, remember 1 autosave + 15 manual slots

FAQ

Should I use Vulkan or DX12 in RDR2? Test both on the same ride. RDR2 Windows supports both RAGE engine on Wikipedia. PCGamingWiki flags Vulkan stutter on NVIDIA and a Vulkan VRAM leak with ReBAR RDR2 on PCGamingWiki, while Rockstar lists changing API as an ERR_GFX_STATE fix Rockstar Support for Red Dead Redemption 2. There is no universal winner.

Does DLSS fix stutter? DLSS Super Resolution raises FPS by reconstructing higher-resolution frames from lower-resolution input with motion data NVIDIA DLSS Technology. It helps GPU-bound vistas. It does not fix SSD, CPU ledger, API, or audio-device hitches. Use it after streaming and volumetrics are budgeted.

Why is Online worse than Story Mode? Up to 32 players share one evolving session Red Dead Redemption 2 on Wikipedia. More riders means more networked horses, physics, and script events. Test solo to isolate this.

Why does galloping cause more stutter than shooting on foot? Galloping increases streaming arrival rate. RAGE must load new frontier blocks continuously, while on foot you reuse the same block longer. Horse speed works like a graphics setting.

References

Evidence for release, engine, and features above comes from the linked primaries. Performance order and the ledger interpretation are the author's synthesis unless otherwise noted.