Official fix status · Hotfix #8 reviewed October 9, 2026
Warhounds Fixes and Latest Patch Status
Find the official shader-compilation workaround and dated fixes for freezes, missing missions, smoke-related FPS drops or broken achievements.
Official announcements reviewed October 9, 2026
What is the latest Warhounds update?
Hotfix #8 was announced on October 8, 2026 (UTC). It provides a temporary way past shader compilation when the game fails to launch at that stage. The developer is still working on a permanent solution; skipping compilation can cause in-game stutters.
Check whether the shader workaround fits your symptom · Official Hotfix #8 announcement
Earlier, Hotfix #7 on September 30 fixed a civilian-turn freeze triggered by a simultaneous mine explosion and added automatic downloading of Microsoft Visual C++ Redistributable. Major Update 1.0.2 on September 24 added rookie class selection and campaign changes.
Official 1.0.2 release notes · Rookie class selection · Base and recovery changes
Warhounds will not launch during shader compilation
Use this only if launch fails at the shader compilation stage. Hotfix #8 documents the following temporary bypass. It is not a general FPS setting or a confirmed permanent fix.
- Open Warhounds in your Steam Library and select Properties.
- In the General tab, find Launch Options.
- Enter
--skipShaderWarmUpand launch the game.
The developer advises against this option if compilation works normally because it may cause stutters during play. If the same launch failure continues, collect your build, GPU and error details for the official bug-report route.
What about the October 2 shader test branch?
The earlier test announcement offered the unstable shaders_warmup_fix branch under Steam Properties → Game Versions & Betas. This is a separate optional test, not the launch option above. The October 8 announcement still describes the permanent solution as work in progress.
October 2 test-branch announcement · October 8 bypass instructions and limitation
Match the symptom to an official fix
These entries record the developer’s stated fixes. Update before retesting; this does not guarantee every similar symptom or old save is resolved.
| Symptom | Developer-listed change | Released update |
|---|---|---|
| Launch fails during shader compilation | Temporary launch-option bypass; possible in-game stutters. Check the conditions above. | Hotfix #8 · Oct 8 |
| Civilian turn freezes when a mine explodes simultaneously | Fix for this specific freeze; automatic Microsoft Visual C++ Redistributable download also added. | Hotfix #7 · Sep 30 |
| Rescue reward missing or Joint Operation not spawning | Fixes for missing Rescue rewards and Joint Operation mission generation. | 1.0.2 · Sep 24 |
| Named abilities, reset button or behavior inside smoke | Fixes for Bullet in the knee, Health Check, Medical Practice, Double shot, I’m covering, the ability reset button and some abilities inside smoke. | 1.0.2 · Sep 24 |
| Shot accuracy display or save/load statuses | Improved shot-accuracy window, corrected line-of-sight calculation discrepancies and specific status-persistence bugs. | 1.0.2 · Sep 24 |
| Freeze or loss of input | Fixes for specific cases. | Hotfix #6 · Aug 31 |
| Story mission missing or Subversion objective destroyed | Fixes for occasional mission visibility and accidental explosive-objective destruction. | Hotfix #6 |
| All-veterans achievement, protection payout, Sniper AP or used Achilles armor HP | Fixes for these named achievement, reward and calculation bugs. | Hotfix #6 |
| FPS drops around smoke | Fix for smoke-particle performance drops. | Patch 1.0.1 · Aug 24 |
| Camera delay after shooting or late return of control | Fixes for camera delay and control after cutscenes/dialogue. | Patch 1.0.1 |
| Save/load statuses or double-mission squad rotation | Fixes for status persistence and rotation errors. | Patch 1.0.1 |
| Missing cities or soldiers stuck on recon | #4 addressed these cases; #5 added missing-city fixes. | #4 · Aug 17; #5 · Aug 19 |
| Crash entering or leaving a mission | #3 introduced a partial fix and faster loading; #4 addressed the probable cause. | #3 · Aug 16; #4 · Aug 17 |
For a missing drone, see the Workshop unlock correction. For a repeatable freeze after updating, use the reporting steps below.
Where did the VSync option go?
Hotfix #2 temporarily disabled VSync because of camera issues. No restoration was announced in the subsequent notes checked through September 7. This records published notes, not a new in-game setting test. Read Hotfix #2.
Current Steam system requirements
| Component | Minimum | Recommended |
|---|---|---|
| OS | Windows 10/11, 64-bit | Windows 10/11, 64-bit |
| CPU | Intel i5-9600 / AMD Ryzen 5 3600X | Intel i5-12600K / AMD Ryzen 7 5700X |
| Memory | 8 GB RAM | 16 GB RAM |
| GPU | 8 GB VRAM, GeForce GTX 1070 Ti / AMD RX 5700 | 8 GB VRAM, NVIDIA RTX 3070 / AMD Radeon RX 6800 |
| DirectX | Version 11 | Version 11 |
| Storage | 85 GB available | 85 GB available |
These values reflect the English Steam page checked on September 8, 2026. Store requirements can change, so compare the live page before purchasing or diagnosing borderline hardware.
Classify the symptom before changing anything
A useful first step is to identify where the failure occurs and whether it repeats. This does not diagnose the cause; it narrows the evidence you need to collect.
| Symptom | Record first | Safe next route |
|---|---|---|
| Will not launch | Error text, Steam state, last successful launch and recent system changes | Restart, compare requirements, verify installed files |
| Crash or freeze | Mission or screen, repeatability, driver version and hardware | Restart, update through official vendor routes, verify files |
| Slow or unstable performance | Resolution, current settings, RAM/VRAM and when the slowdown begins | Compare current requirements and test one reversible setting change at a time |
| Mission progression block | Objective wording, last completed action, save state and exact version | Search official notes and discussions for the exact objective; do not delete saves |
For a mission-specific block, consult the walkthrough evidence standard. A forum post can help reproduce the issue but does not by itself prove a safe fix.
Safe first-line steps
Record the symptom
Note the error text, mission or screen, whether it repeats, and any recent patch or driver change.
Restart Windows and Steam
This clears temporary process and file-lock state without changing game data.
Update Windows and graphics drivers
Use the official operating-system and GPU-vendor update routes.
Verify installed files
Steam Support says to open Library → Warhounds → Properties → Installed Files → Verify integrity of game files.
Compare with requirements
Check RAM, VRAM, storage and the supported Windows platform against the current store page.
Where to send a Warhounds bug report
The developer directs players to support@warhounds.game or the Discord #release-bug-reports channel linked from its official Support & Bug Reporting post.
Include the mission or screen, steps to reproduce, installed build and affected save name. The official post requests:
- Saves: the Save folder inside
C:\Users\USERNAME\AppData\LocalLow\EverPlay\Warhounds. - Logs:
Player.logandPlayer-prev.logbeside the Save folder. - Crash dumps:
C:\Users\USERNAME\AppData\Local\Temp\EverPlay\Warhounds\Crashes.
Replace USERNAME with your Windows account folder. Copy or archive the requested files for the developer’s support route and keep the originals. Do not post private logs or save archives in a public comment.
What this page does not promise
Launch-week posts mention crashes, freezes, long loading and mission blocks. A report proves that a player experienced a symptom; it does not prove one root cause or a universal workaround. This guide does not recommend deleting saves, editing the registry, using unknown launch options or downloading third-party “fix” tools.
Stop before a troubleshooting step becomes destructive
Pause if a proposed fix asks you to delete saves, replace unknown files, disable security controls, edit the registry, install an unofficial executable or expose account information. Preserve the original data and use the game’s official support destinations when available. If a file-verification or update operation reports an error, capture the exact result instead of repeatedly escalating to stronger changes.
When submitting a correction to this guide, include the official source or a reproducible sequence and leave out personal paths, account identifiers and private logs.