WARDOGS DX11: Steam Launch Options and -dx11 Status

No Team17 or BULKHEAD source found for this page tells Windows players to use -dx11. A player report in the WARDOGS Steam Community says the parameter produced the message: Unable to launch with RHI ‘D3D11’ since the project is not configured to support it.

That is a player-recorded result, not a published Team17 product specification. It is still sufficient evidence not to present -dx11 as a WARDOGS FPS fix or a supported Steam startup command. Leave it out unless Team17 or BULKHEAD publishes a different instruction.

Read the Steam player report.

For a specific performance report, Team17 instructed the player to add -nogpucrashdebugging. This is the only WARDOGS Steam launch option this page lists because it is the only one found in a Team17 reply.

1. Open Steam → Library → WARDOGS → Properties → General → Launch Options.
2. Enter -nogpucrashdebugging.
3. Start WARDOGS again and check whether the reported issue remains.

Team17 described this as something the player could try; it did not call it a universal performance command or promise an FPS increase. Treat it as targeted troubleshooting, not a permanent optimization preset.

Read Team17's launch-option instruction.

In the same reply, Team17 gave one related configuration step: open %LOCALAPPDATA%\Wardogs\Saved\Config\Windows\GameUserSettings.ini, set both NvidiaDLSSMode and FSR3QualityMode to 0, then try the game again.

This is a support instruction for that reported performance case. It is not evidence that either setting improves every system, so no broader DLSS, FSR, frame-generation, resolution, or graphics-option claims are added here.

-dx11: not listed as a fix because the available WARDOGS player report recorded a D3D11-not-configured message.

Launcher-bypass commands: not listed because Team17 says Linux / Proton support is not officially supported yet. Community posts ask whether commands that bypass the launcher are safe with anti-cheat, but there is no Team17 confirmation here that such commands are safe for normal WARDOGS play.

Generic Unreal Engine parameters: not listed because this page did not find a Team17 or BULKHEAD instruction for them. A command can exist in another game without being a documented WARDOGS launch option.

Read Team17's Linux compatibility statement.

Use the Team17 support path that matches the symptom rather than adding more unverified launch parameters. For a WARDOGS performance issue, Team17's published checks include lowering the graphics preset, updating GPU drivers, closing background applications and overlays, capping the frame rate to the monitor, lowering resolution, and temporarily disabling DLSS, FSR, NIS, frame generation, HAGS, and Windows Game Optimizations as relevant to the system.

For a start-up problem, Team17's published troubleshooting includes verifying game files through Steam, repairing Elytra from the WARDOGS installation folder, restarting the PC, and checking whether security software blocks WARDOGS or Elytra. Those are separate support instructions, not launch options.

Read Team17's FPS guidance · Read Team17's launch troubleshooting.

If the issue is a join timeout instead, use the WARDOGS Error 1628505091 guide. For current development context, see the WARDOGS roadmap and the Early Access guide.