PC · RETAIL RELEASEREVIEWED SEP 29, 2026
A source-backed view of open problems and recent fixes. Official developer notes, cautious status calls, and player reports are kept separate.
Find your save files and Player.log ↓ · Changes in 1.0.2 ↓
SEPTEMBER 24 UPDATE
Match the symptom to the change before trying a workaround. A targeted fix in the notes is not proof that every similar problem is resolved on your installed build.
Update 1.0.2 disables this action in story missions. If that is the option you are looking for, its absence matches the published change. Follow the mission’s displayed objectives; if progression itself is blocked, record the objective and last action instead of treating extraction as the intended escape route.
The update lists fixes for missing Rescue rewards and Joint Operation spawning. If either recurs, preserve the affected save and note the mission name, completion result and whether the reward or mission failed to appear. “All missing missions are fixed” would go beyond the announcement.
The notes address the ability-reset button and specific save/load status bugs. For recurrence, record the ability or status and compare before saving with after loading. Do not assume that a patch repairs an already affected save; keep a separate backup.
These changes are documented in Brightika’s Update 1.0.2 announcement ↗. For the release sequence and new languages, see our patch timeline.
A player reported this symptom in a recent AMD discussion; a reply describes a similar launch failure on a GeForce 960. This does not establish an AMD-only fault or a shared cause.
What to record: The exact stopping point, whether it ever progresses, GPU model, driver version and installed game build. Compare your hardware with the retail requirements; running the demo does not establish that the retail game meets the same conditions.
No reproducible fix is established by the reviewed thread. Use the report checklist and preserve the log rather than applying an unverified save or configuration edit.
CURRENT OFFICIAL STATUS
Hotfix #2 disabled VSync. The reviewed later notes do not state whether it was restored. That absence does not prove the setting is still missing or that it is the only remaining issue.
Symptom: If VSync is missing in your build, compare its version with the August 14 change.
Official context: Hotfix #2 temporarily disabled VSync after some players experienced camera issues. Later notes reviewed through Update 1.0.2 do not confirm its return.
Safe action: Check the setting in the updated client. If it is absent or causes camera trouble, record the build and display setup rather than editing configuration files from an older workaround.
RECENTLY FIXED
These problems appeared in official notes and were subsequently marked fixed. If one still occurs after updating, treat it as a new report and include the exact trigger.
| Issue | Official status | Patch record | If it still happens |
|---|---|---|---|
| Freezes or lost input | Targeted fix published | Hotfix #6, August 31. ↗ | Record the action immediately before input stops and whether it happens after loading a save. |
| Story mission missing | Targeted fix published | Hotfix #6 addresses certain missing story missions. ↗ | Preserve the save and report the last completed objective; do not restart the entire campaign as a guaranteed fix. |
| UI or subtitle language | Updated | Patch #2 adds Simplified Chinese UI/subtitles and UI fixes. ↗ | Record the chosen language and affected screen if text is still wrong. |
| Crash while entering or leaving a missionPerformance / crash | Fixed · monitor | Hotfix #4 addressed the probable cause after a partial fix in #3. ↗ | Record the mission, whether the crash occurred on entry or exit, and your PC specs. |
| Missing cities or soldiers stuck on reconCampaign progression | Fixed | Hotfix #4 addressed both; #5 fixed further missing-city cases. ↗ | Do not overwrite your only save. Note the affected city and recon team. |
| Freeze during double OverwatchCombat | Fixed | Hotfix #4, August 17. ↗ | Capture the unit order, weapons, and actions immediately before the freeze. |
| Barracks blocked after using a playtest saveSave / base progression | Fixed | First hotfix, August 13. ↗ | State clearly that the campaign originated in the playtest build. |
| Mission script freeze after the last soldier dies in extractionMission progression | Fixed | First hotfix, August 13. ↗ | Include the mission and whether the final soldier was inside the evacuation zone. |
Official fix history: Warhounds announcements on Steam . “Fixed · monitor” reflects the developer’s cautious wording—Hotfix #4 calls its crash change a fix for the “probable cause.”
REPORTING CHECKLIST
A useful report describes one problem, the exact moment it occurs, and what changed immediately beforehand. Avoid deleting saves or editing configuration files unless the developer specifically asks.
Allow Steam to finish pending updates. Record the version or build identifier shown by your installed copy, if available; otherwise write “not recorded.” List the official patch note and its date separately. Reading the latest announcement does not establish which build you ran.
Keep both files belonging to the affected save; use the save-folder and log instructions below. Take a screenshot and record the mission, action order and visible error message.
Include Windows version, CPU, GPU, RAM, display resolution, graphics preset, and whether the problem repeats.
COPYABLE REPORT
Issue:
Installed version / build ID (or not recorded):
Official patch note / publication date:
Date the problem occurred:
Windows version:
CPU / GPU / RAM:
Mission or screen:
Steps to reproduce:
Expected result:
Actual result:
Does it repeat:
Save originated in playtest: Yes / No
Screenshot or error text:
New to Warhounds? Read the Warhounds beginner guide before troubleshooting a first-session question.
SAVE FILE LOCATION · WINDOWS
The developer’s reporting instructions put saves in the folder below. Each save has a file in Save and a corresponding file in Save\SaveData; sending only the top-level file leaves out part of the save.
OPEN IN FILE EXPLORER
Paste this into the address bar while signed into the Windows account used to play.
%USERPROFILE%\AppData\LocalLow\EverPlay\Warhounds\SaveClose the game, open the folder and compare file modification times with your last save. Keep the corresponding files in Save and SaveData together. If the folder is absent, check the Windows account and any redirected AppData location; do not create an empty folder as a repair.
Copy the whole Save folder, including SaveData, to a separate dated backup while the game is closed. Leave the original in place. This preserves the pair without requiring you to guess which single file contains the campaign.
Player.log is in the parent Warhounds folder. Include it and both save components through the developer’s support channel when relevant. Review attachments for personal information before sharing them publicly.
The developer’s official bug-reporting instructions ↗ were checked September 17, 2026. Customized Windows folder locations can differ. Backup and restore have not been tested on a local game installation; this is a locate-and-copy procedure, not a recovery guarantee.
EVIDENCE LABELS