Sir We Have an Orc Problem Troubleshooting

Start here before reinstalling

Steam discussions already include “The game doesnt start” threads during launch week. Sir, We Have an Orc Problem is a small install (~200 MB) built around Vulkan 1.3 and large particle/explosion loads later in the campaign. Most launch failures are driver or API related, not missing disk space. Keep System Requirements open beside this checklist.

Symptom: game does not start / instant close

1. Update GPU drivers from AMD, NVIDIA, or Intel - not only Windows Update.
2. Confirm the GPU reports Vulkan 1.3 (GPU-Z, vulkaninfo, or vendor control panels).
3. Disable aggressive overlays (Discord, GeForce Experience, RGB suites) for one test launch.
4. Verify Steam game files.
5. Launch once without recording software (OBS, ReLive, Game Bar).
6. On laptops, force the discrete GPU for Steam and the game executable.

If Vulkan is missing entirely, integrated-only machines on older APIs will fail even though CPU requirements say “any x86_64”.

Symptom: starts, then stutters on huge waves

Late maps and nukes push GPU explosion simulation (moved to GPU in the June demo patch). Mitigations:

• Close Chrome tabs and hardware-accelerated browsers.
• Lower recording bitrate or disable shadowplay.
• Prefer a dedicated GPU when the store recommends it.
• Avoid resizing the window mid-battle - earlier builds had orc/shadow offset bugs when resizing (patched in demo notes).

Performance history: Patch Notes.

Symptom: black screen or wrong resolution

Try borderless windowed if exclusive fullscreen fails after alt-tab. On multi-monitor setups, move the window to the primary display before pressing Space into a dense wave. Camera Comfort options on Steam may help players sensitive to shake - see Controls.

Steam Deck / SteamOS checklist

Steam lists SteamOS 3.8 or similar with the same Vulkan 1.3 and 4 GB RAM bar. On Deck:

1. Update SteamOS.
2. Use a Performance profile for late maps.
3. Prefer trackpad or mouse for long Gunner drag lines.
4. Keep Proton/SteamOS current if the build is Proton-routed; native Linux builds should still expose Vulkan.

Mouse Only Option and Playable without Timed Input help handheld play, but precise choke rebuilds still benefit from a mouse.

Audio stuck above zero

Community feedback during the demo asked for a true mute below the previous 25% floor. Launch builds should expose Custom Volume Controls - verify in settings. If audio cannot reach zero, set Windows per-app volume as a temporary workaround and watch patch notes.

Save / progress worries

Meta purchases are persistent on your save. Cloud behaviour follows Steam Cloud for the title when enabled - confirm in Steam properties. Losing a run does not wipe the tree; that is intentional. Farm rules for Bonus Resources still require finishing battles for the flat payout - Bonus Resources.

Ability / pause quirks

Older clips that spam multiple strafing runs from the pause menu are outdated. June 12 fixed that exploit. If abilities feel wrong, update to the latest Steam build before assuming balance broke your layout.

When to ask for help

Collect: OS version, GPU model, Vulkan version string, whether demo or full build, and whether verify files was tried. Post on Steam discussions or the developer Discord linked from mumpitzgames.com / the Steam hub. This fan wiki cannot remote-debug every PC.

Related reading

• System Requirements - official minimums
• FAQ Hub - non-technical launch questions
• Launch Day Notes - unlock timing context
• Controls - input and accessibility
• Getting Started - first successful session after it launches