{"id":76467,"date":"2026-08-26T04:26:00","date_gmt":"2026-08-26T08:26:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=76467"},"modified":"2026-08-16T08:05:10","modified_gmt":"2026-08-16T12:05:10","slug":"death-stranding-2-dx11-launch-option","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/death-stranding-2-dx11-launch-option\/","title":{"rendered":"How to Set Death Stranding 2 Launch Options in Steam with -dx11 for Better Stability"},"content":{"rendered":"\n

Play Death Stranding 2: On the Beach<\/em> on PC for the first time, and you might hit a crash before you even see the title screen. A black window, then nothing. Or the game<\/a> loads, runs for ten minutes, and freezes. This isn’t your hardware failing. It’s a conflict between the engine, your GPU driver, and the default rendering API.<\/p>\n\n\n\n

The fix is simpler than most guides admit: force DirectX 11 through a Steam<\/a> launch option. Specifically, the -dx11<\/code>codecodecodecodecodecode flag.<\/p>\n\n\n\n

Most troubleshooting advice throws a dozen methods at you \u2014 clean boots, SFC scans, reinstalling Visual C++ runtimes. Those matter, but they treat the symptom, not the root cause. The root cause is almost always the DirectX 12 path being unstable on certain driver versions or hardware configurations. Switching to DX11 bypasses that instability with a single text edit.<\/p>\n\n\n\n

Here is how you do it, why it works, and when it might not.<\/p>\n\n\n\n

Setting the -dx11 Launch Option in Steam<\/h2>\n\n\n\n

The process takes about twenty seconds.<\/p>\n\n\n\n

Open your Steam library. Locate Death Stranding 2: On the Beach<\/em>. Right-click the title and select Properties<\/strong>. Under the General<\/strong> tab, you will see a text field labeled “Launch Options.” Type exactly this:<\/p>\n\n\n\n

-dx11<\/p>\n\n\n\n

Close the window. Launch the game.<\/p>\n\n\n\n

That is the entire fix for a large portion of crash-on-startup issues.<\/p>\n\n\n\n

If you still get a crash, try the alternative flags -dx12<\/code>codecodecodecodecodecode or -d3d11<\/code>codecodecodecodecodecode in the same field. But start with -dx11<\/code>codecodecodecodecodecode. Most system configurations \u2014 especially those running Nvidia GTX 16-series, RTX 20-series, or any AMD Radeon RX 5000\/6000 \u2014 show significantly fewer crashes with the older API.<\/p>\n\n\n\n

What If the Game Still Crashes?<\/h3>\n\n\n\n

The launch option alone might not be enough if your install has corrupted files or missing runtimes. Run a file verification first.<\/p>\n\n\n\n

Back in Steam, right-click the game, select Properties<\/strong>, go to Installed Files<\/strong>, and click Verify integrity of game files<\/strong>. Steam will scan every file and replace any that are damaged. This step is essential even after setting -dx11<\/code>codecodecodecodecodecode. Corrupt data can cause a hang regardless of which API you use.<\/p>\n\n\n\n

After verification, launch again. If the crash persists, update your GPU driver directly from Nvidia or AMD \u2014 not through Windows Device Manager, which often serves outdated versions. A clean driver install using Display Driver Uninstaller (DDU) in Safe Mode removes leftover shader caches that can interfere with DX11.<\/p>\n\n\n\n

Why -dx11 Delivers Better Stability<\/h2>\n\n\n\n

DirectX 12 is designed for low-level hardware access. The game engine talks directly to the GPU, bypassing many driver abstractions. This can boost frame rates on perfectly optimized systems. It can also expose every flaw in your driver, your Windows schedule, and the game’s own code.<\/p>\n\n\n\n

Death Stranding 2<\/em> uses a modified version of the<\/a> Decima Engine. The original Death Stranding<\/em> launched on PC with known D3D12 stability problems \u2014 random stutters, texture corruption, complete lockups during cutscenes. Kojima Productions patched many of these over time, but the DX12 path remained less reliable than DX11 for a large segment of players, especially those with mid-range cards and older CPUs.<\/p>\n\n\n\n

Forcing -dx11<\/code>codecodecodecodecodecode tells the engine to use the older API, which has been battle-tested on thousands of hardware combinations over a decade. Microsoft’s DX11 driver model is more forgiving. If a draw call fails, the driver handles it gracefully. In DX12, the same failure can take down the entire render thread.<\/p>\n\n\n\n

This is not a matter of “DX11 is better.” It is a matter of reliability. When your game crashes at startup, you don’t need maximum theoretical throughput. You need the software to start and stay running.<\/p>\n\n\n\n

The Strongest Counterargument: Use -dx12 for Better Performance<\/h2>\n\n\n\n

Some players argue that forcing DX11 leaves performance on the table. They are correct in principle. DX12’s reduced CPU overhead can improve frame pacing, especially on multi-core processors. The game can<\/em> run smoother with -dx12<\/code>codecodecodecodecodecode \u2014 if everything aligns: the right GPU driver version, no background overlays, a clean Windows install without conflicting services.<\/p>\n\n\n\n

But here is the problem: “can” is not “will.”<\/p>\n\n\n\n

For many users, -dx12<\/code>codecodecodecodecodecode introduces microstutter and periodic freezes that no amount of driver reinstallation fixes. The instability comes from the game’s shader compilation pipeline. On DX12, shaders are compiled at the driver level, and if the driver cache is incomplete or corrupted, every new effect forces a just-in-time compilation that stalls the frame. DX11 handles this more predictably because it relies on a standard UMD (user-mode driver) process that Microsoft<\/a> has optimized across every Windows version since 7.<\/p>\n\n\n\n

You gain 10\u201315% more frames with DX12 if the stars align. You lose 100% of frames when the game crashes. A crash means zero performance. A stable DX11 session at 60 frames per second beats an unstable DX12 session that freezes every six minutes.<\/p>\n\n\n\n

If you have an RTX 4060 or higher and are willing to tweak settings for an hour, try -dx12<\/code>codecodecodecodecodecode at your own risk. For everyone else \u2014 especially users with GPU usage under 90% at 1080p \u2014 -dx11<\/code>codecodecodecodecodecode is the defensible choice. You can always switch back.<\/p>\n\n\n\n

Additional Tweaks That Reinforce Stability<\/h2>\n\n\n\n

The -dx11<\/code>codecodecodecodecodecode flag works best when combined with a few other adjustments. Do not skip these.<\/p>\n\n\n\n

Disable Steam Overlay<\/strong> \u2014 Steam’s in-game<\/a> overlay can intercept DX calls and cause a hang on older APIs. Open Steam Settings > In-Game<\/strong> and uncheck “Enable the Steam Overlay while in-game.” Same for Discord overlay: in User Settings under Game Overlay, turn it off. GeForce<\/a> Experience overlay also has a dedicated toggle. Disable all three before launching.<\/p>\n\n\n\n

Turn Off Real-Time Antivirus<\/strong> \u2014 Windows Defender, if it decides to scan the game executable while it is running, can trigger a crash. Open Windows Security, go to Virus & threat protection > Manage settings<\/strong>, and toggle off real-time protection. Launch the game. After you’re done playing, turn it back on. Do not leave it disabled.<\/p>\n\n\n\n

Remove Overclocks<\/strong> \u2014 If you have overclocked your CPU or GPU, reset them to stock. Unstable overclocks produce artifacts that look like game crashes. DX11 is more tolerant than DX12, but it cannot compensate for a CPU that feeds bad data at 5.3 GHz. Use MSI Afterburner or your motherboard UEFI to revert to base clocks. Test the game. If stable, you can slowly reapply the overclock later.<\/p>\n\n\n\n

Change Power Plan to High Performance<\/strong> \u2014 Windows likes to throttle the CPU to save energy. Go to Control Panel > Power Options<\/strong> and select High performance<\/strong>. This prevents the scheduler from lowering clock speeds during low-intensity moments, which can cause a hitch when the game suddenly demands full power.<\/p>\n\n\n\n

What to Do If -dx11 Also Crashes<\/h2>\n\n\n\n

Sometimes the engine itself is broken, not the API. You run the game with -dx11<\/code>codecodecodecodecodecode and still get a black screen on launch. Try the -d3d11<\/code>codecodecodecodecodecode flag instead. It forces the same DirectX 11 path but bypasses some Steam wrapper logic that can interfere with the renderer initialization.<\/p>\n\n\n\n

If that also fails, open the game’s executable directly from the installation folder. In Steam, right-click the game, choose Manage > Browse local files<\/strong>. Find the .exe<\/code>codecodecodecodecodecode, right-click it, go to Properties > Compatibility<\/strong>, and check “Run this program as an administrator.” Also check “Disable full-screen optimizations.” These two options prevent Windows from injecting its own optimization layer \u2014 a known cause of hangs on Decima Engine titles.<\/p>\n\n\n\n

One more rare edge: certain systems cannot handle DX11 if the GPU driver lacks the necessary feature level. Check your GPU’s feature level using dxdiag<\/strong> (Win + R, type dxdiag<\/code>codecodecodecodecodecode, look under the Display tab). If it shows 11_0 or higher, you are fine. If it shows 10_0, your card is too old for this game regardless of API.<\/p>\n\n\n\n

The Limits of This Approach<\/h2>\n\n\n\n

A scenario where -dx11<\/code>codecodecodecodecodecode fails entirely: the game relies on mesh shaders or ray tracing features that DX11 does not support. Death Stranding 2<\/em> uses some optional RT reflections. With -dx11<\/code>codecodecodecodecodecode, those reflections default to screen-space methods. Visual quality drops slightly. You lose the glossy, accurate reflections on wet surfaces and vehicle windows. If you bought the game specifically for ray-traced visuals, you will be disappointed. In that case, accept the risk of DX12 crashes, limit the frame rate to 60 via RTSS (not in-game V-Sync), and try again.<\/p>\n\n\n\n

There is also the rare scenario where DX12 is actually more<\/em> stable than DX11 \u2014 usually on high-end Nvidia cards (RTX 4080\/4090) paired with the latest driver. If you have that hardware and still get crashes, update your BIOS to the latest version. But most crashing players do not own $1,500 GPUs. They own mid-range machines where DX11 remains the safest bet.<\/p>\n\n\n\n

For those users, the -dx11<\/code>codecodecodecodecodecode launch option is not a compromise. It is the difference between playing the game and alt-F4-ing in frustration. Type it, launch it, and get back to delivering cargo through a fractured America.<\/p>\n","protected":false},"excerpt":{"rendered":"

Play Death Stranding 2: On the Beach on PC for the first time, and you might hit a crash before you even see the title screen. A black window, then nothing. Or the game loads, runs for ten minutes, and freezes. This isn’t your hardware failing. It’s a conflict between the engine, your GPU driver, […]<\/p>\n","protected":false},"author":7,"featured_media":83690,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/76467.png","fifu_image_alt":"How to Set Death Stranding 2 Launch Options in Steam with -dx11","footnotes":""},"categories":[2],"tags":[],"class_list":["post-76467","post","type-post","status-publish","format-standard","has-post-thumbnail","category-videogames"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/76467.png","fifu_image_alt":"How to Set Death Stranding 2 Launch Options in Steam with -dx11","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/76467","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=76467"}],"version-history":[{"count":0,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/76467\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/83690"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=76467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=76467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=76467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}