Sir We Have an Orc Problem System Requirements

Official Steam requirements

Sir, We Have an Orc Problem is a lightweight incremental tower defense, but late maps spawn enormous crowds and GPU-simulated explosions. Meet the store minimums before blaming balance for stutter.

Windows - Minimum

• OS: Windows 10 (64-bit)
• Processor: Any x86_64 CPU
• Memory: 4 GB RAM
• Graphics: Vulkan 1.3 support
• Storage: 200 MB available space

Windows - Recommended

• OS: Windows 11 (64-bit)
• Processor: Any x86_64 CPU
• Memory: 4 GB RAM
• Graphics: Dedicated GPU with Vulkan 1.3 support
• Storage: 200 MB available space

SteamOS / Linux - Minimum

• OS: SteamOS 3.8 or similar
• Processor: Any x86_64 CPU
• Memory: 4 GB RAM
• Graphics: Vulkan 1.3 support
• Storage: 200 MB available space

SteamOS / Linux - Recommended

• OS: SteamOS 3.8 or similar
• Processor: Any x86_64 CPU
• Memory: 4 GB RAM
• Graphics: Dedicated GPU with Vulkan 1.3 support
• Storage: 200 MB available space

What those numbers mean in practice

Four gigabytes of RAM and a two-hundred-megabyte install make this friendlier than most modern strategy titles. The hard gate is Vulkan 1.3. Integrated graphics that only expose older Vulkan or DirectX-only stacks may fail even if CPU benchmarks look fine. Prefer a dedicated GPU on recommended settings when late waves and nukes fill the screen - demo notes moved explosion simulation to the GPU specifically to keep huge blasts smoother.

If the game does not start, community threads often point to driver updates or overlay conflicts rather than missing CPU horsepower. Verify the Steam install, disable aggressive overlays, and confirm Vulkan-capable drivers before reinstalling.

Steam Deck and handheld notes

SteamOS 3.8-class devices sit inside the Linux column. Mouse-only and no-timed-input accessibility options help on handhelds, but precise drag placement still benefits from trackpads or a paired mouse. Read Controls for shortcuts that reduce rebuild friction on smaller screens.

Thermal throttling during 100k-orc spectacles is more likely than failing the storage check. Close background downloads, use a performance profile, and avoid stacking recording software during first clears.

Accessibility features listed on Steam

• Camera Comfort
• Custom Volume Controls
• Mouse Only Option
• Playable without Timed Input

These do not replace learning build versus battle phases, but they lower barriers for players who need simpler input or calmer camera behaviour. Combine them with the short campaign length (about four to six hours) described in Demo vs Full Game.

Languages and platform scope

The Steam page lists thirteen interface languages (English, French, Italian, German, Spanish, Dutch, Japanese, Korean, Polish, Brazilian Portuguese, Russian, Simplified Chinese, Traditional Chinese). This fan wiki covers English, French, German, and Spanish guides - see the language switcher. Single-player only; no multiplayer session bandwidth to worry about.

Performance tips tied to patches

June demo work moved explosions to the GPU and improved big-blast performance. If you still hitch on orbital lasers or nukes, lower recording bitrate, update GPU drivers, and avoid forced software rendering. Visual glitches with orc shadows after window resizes were patched - update to the latest Steam build before reporting regressions.

Related pages

• Controls - input and shortcuts
• Patch Notes - performance and QoL history
• Getting Started - first session checklist
• Game Review - whether the campaign fits your hardware time budget