Warhounds Known Issues and Official Fix Status

Quick Answer

Patch 1.0.1 was released on August 24, 2026. It lists fixes for a VIP rescue failure state, save/load status persistence, double-mission squad rotation, smoke-related FPS drops, delayed camera or control return, Ultrawide gamepad controls, mission scripts and objects, Hangar discounts, Hunter Drone damage display, UI switching, portraits, descriptions, and several presentation issues.

Patch #2 shipped on September 7, 2026. It added Simplified Chinese UI and subtitles and listed several UI fixes without enumerating individual cases.

Major Update 1.0.2 shipped on September 24, 2026. It adds another broad developer-listed fix set across Rescue rewards, Joint Operation spawning, city recon, mission scripts, line-of-sight accuracy calculations, status saving, abilities, smoke interactions, drones/UAVs, UI, presentation, and other named cases. These are release-note claims, not Warhounds.org hands-on PASS results.

Use this as a versioned fix-status hub, not a list of forum rumors or invented workarounds. “Fixed” records the developer’s stated scope; it does not prove that every related symptom, old save, hardware configuration, or adjacent mechanic is resolved. Earlier missing-city, VSync, and crash questions therefore remain cautious where later first-party notes are silent.

A pre-1.0.2 August 25 discussion index contains Grenadier, VIP, Assault, difficulty, line-of-sight, mission-team, Rescue, and il2cpp topics. Those titles are historical community-only research leads, not confirmed bugs or instructions, and that snapshot does not establish post-1.0.2 recurrence.

If an issue still happens, preserve a clean reproduction and report the current build, save history, and exact transition where it occurs.

How to read the status labels

• Further fixes: More than one patch addressed the issue; the newest note does not promise every cause is eliminated.
• Official fix listed: A patch note says a specific issue was fixed. It does not prove that no variant can recur on every save or device.
• Partial / probable-cause fix: The developer explicitly limited the scope or confidence of the fix.
• Current status unknown: An earlier change is documented, but no later first-party source confirms restoration or final behavior.
• Needs live test: The patch note proves the issue and fix scope exist, while current gameplay behavior still needs controlled reproduction.
• Community report only: A current player report is useful enough to track, but no first-party source has confirmed the issue, trigger, or root cause.

Status summary

Issue	Official status	Patch history	What remains unknown
Missing cities	Further fixes	#4 listed a fix; #5 fixed further issues	Whether every save/progression edge case is resolved
Mission enter/exit crashes	Partial, then probable-cause fix	#3 partially fixed crashes; #4 targeted the probable cause	Pre-1.0.2 community recurrence exists; post-1.0.2 recurrence is not verified
VIP rescue false mission failure	Official fix listed	Patch 1.0.1	Other VIP stun, carry, extraction, or failure-state cases
Status persistence after save/load	Further developer-listed fixes	Patch 1.0.1; Major Update 1.0.2	Which statuses were affected and whether older saves self-repair
Double-mission squad rotation	Official fix listed	Patch 1.0.1	Exact former trigger and recurrence on migrated saves
Smoke-particle FPS drops	Official fix listed	Patch 1.0.1	Performance on every hardware and smoke-heavy scene
Delayed camera/control return	Official fix listed	Patch 1.0.1	Unrelated camera or input delays
Ultrawide gamepad controls	Official fix listed	Patch 1.0.1	Complete controller coverage across every screen
Hangar discounts not displayed	Official fix listed	Patch 1.0.1	Discount rules and values
Hunter Drone damage display	Official fix listed	Patch 1.0.1	Actual damage and whether display now matches every upgrade
Double Overwatch freeze	Official fix listed	#4	Definition of “double Overwatch” and recurrence status
Soldiers stuck on recon	Official fix listed	#4	Exact recon rules and whether old saves need special handling
Characters stuck on city missions	Pre-1.0.2 community report only	Aug 23 Steam activity; no official fix note	Trigger, relation to recon, and whether it recurs on 1.0.2
VSync / camera issue	Current status unknown	Hotfix #2 temporarily disabled VSync	Whether/when restored; needs a 1.0.2 settings-menu check
Barracks / crew shortage	Official fix listed	#1	Behavior on unusual or migrated saves outside the named trigger
Evacuation-zone freeze	Official fix listed	#1	Other extraction failures not described by the note
Prisoner movement debuff stacking	Official fix listed	#1	Current numeric penalty and unrelated prisoner behavior
Freeze / loss of input	Developer-listed fix	Hotfix #6	Exact former triggers and recurrence on other freeze families
Gang’s All Here unlock	Developer-listed fix	Hotfix #6	Site has not independently re-tested every existing save
Protection-objective payout	Developer-listed fix	Hotfix #6	Other payout rules and unrelated reward failures
Sniper AP calculation	Developer-listed fix	Hotfix #6	Exact ability combinations and current numeric AP behavior
Used Achilles armor HP bonus	Developer-listed fix	Hotfix #6	Exact item values and unrelated armor variants
Story missions not appearing	Developer-listed fix	Hotfix #6	Other missing-city or progression causes
Subversion explosive objective	Developer-listed fix	Hotfix #6	Other objective-destruction rules
Localization errors	Further developer-listed fixes	Hotfix #6; Major Update 1.0.2	Exact strings/languages not enumerated by the notes
Unspecified UI issues	Further developer-listed fixes	Patch #2; Major Update 1.0.2	Exact affected screens, symptoms, and triggers are not enumerated
Rescue mission rewards	Developer-listed fix	Major Update 1.0.2	Normal reward amounts and recurrence on older saves
Joint Operation spawning	Developer-listed fix	Major Update 1.0.2	Former trigger and recurrence on migrated campaigns
City recon issues	Developer-listed fixes	Major Update 1.0.2	Exact affected recon states and relation to older stuck-recon bug
Line-of-sight accuracy calculation	Developer-listed fix	Major Update 1.0.2	Exact formula and whether every edge case is resolved
Cai Shen squad missing taser	Developer-listed fix	Major Update 1.0.2	Former trigger and current weapon behavior not independently retested
Abilities inside smoke	Developer-listed fix	Major Update 1.0.2	Which abilities and exact former behavior
Story manual extraction	Developer-listed fix	Major Update 1.0.2	Manual extraction is now disabled; scripted story extraction remains separate

Major Update 1.0.2 fix status

The September 24 release note names a large set of fixes, but the wording is still a developer changelog rather than an independent recurrence test. Use the narrowest named scope:

• missions: Rescue rewards, Joint Operation spawning, random events, regular/story mission scripts, objects and grid cells, city recon, and story-mission manual extraction;
• combat and abilities: line-of-sight accuracy discrepancies, scanning, specific named abilities, ability behavior inside smoke, knife-fight death behavior, the missing taser weapon for the player-controlled Cai Shen squad, and zone highlights;
• drones and UAVs: meta-mode drone ability display, drone self-destruct VFX, and UAV cargo-hold filtering;
• state/UI/presentation: status saving, tutorial re-triggering, ability reset, pop-ups, Character Editor colors, Ultrawide global-map cursor, Julia lines, interface layout/display, enemy behavior, animation, SFX, and localization cases.

The release note says manual extraction on story missions is now disabled. That does not erase scripted story objectives that involve an extraction sequence; it removes the manual extraction path the developer identified as erroneous.

Patch #2 UI-fix scope

Patch #2 shipped on September 7 with Simplified Chinese UI and subtitle localization. The same official announcement says several UI issues were fixed, but it does not publish a bug-by-bug list.

Because that scope is not enumerated, no existing issue on this page is upgraded to Official fix listed solely because of Patch #2. Major Update 1.0.2 is now the current release baseline; re-test any recurring symptom against 1.0.2 before changing a specific status row.

Hotfix #6 fix status

The August 31 note adds several developer-listed fixes that should not be collapsed into broader claims:

• Freeze / loss of input: a specific freeze-and-input-loss problem is listed as fixed; unrelated crashes, driver failures, or other freeze families are not automatically covered.
• Gang’s All Here: the failure to unlock after recruiting all veterans is listed as fixed. The public achievement condition remains “Hire all veterans.”
• Protection payout: failing to receive a payout after protecting an objective is listed as fixed; the note does not publish a reward table.
• Sniper AP calculation: the calculation problem when combining Sniper abilities is listed as fixed; the note does not document every ability combination or AP value.
• Used Achilles armor: missing HP bonuses on used Achilles armor are listed as fixed; this does not establish a complete armor-stat table.
• Story-mission visibility: story missions occasionally failing to appear is listed as fixed. This is narrower than claiming every missing city, blocked map, or progression case is resolved.
• Subversion objective: accidental destruction of an explosive objective in Subversion missions is listed as fixed; other objective rules remain separate.
• Localization: localization errors were fixed without an exhaustive public list of affected strings.

This site records these as developer-listed fixes, not hands-on verification.

Patch 1.0.1 fix status

The official note supports the following direct conclusions:

• A specific VIP rescue mission could incorrectly fail if all soldiers died after the rescue; that case is listed as fixed.
• Certain statuses could fail to persist across save/load cycles; that persistence case is listed as fixed.
• Squad rotation between double missions could produce errors; the listed case is fixed.
• Smoke particles could cause FPS drops; that listed performance issue is fixed.
• Camera return after a shot and player-control return after cutscenes or dialogue could be delayed; both listed cases are fixed.
• An Ultrawide-specific gamepad-control issue is listed as fixed.
• Hangar item discounts and Hunter Drone damage could display incorrectly; both are display fixes, not documentation of their underlying values.
• Mission scripts, mission objects, rapid meta-screen switching, portraits, descriptions, VFX, SFX, and animations received specific fixes without a public list of every trigger.

Do not use this list to infer mechanics the announcement does not state. In particular, the VIP note is not a stun/capture guide, the Hunter Drone note is not a damage table, and the gamepad note is not proof of complete controller support.

Missing cities

Hotfix #4 listed a fix for missing cities. Hotfix #5 then announced “further fixes for missing cities,” which confirms that additional cases existed after the earlier patch.

What is confirmed: two official patches addressed the issue, and the August 19 note narrows its scope to further missing-city cases.

What is not confirmed: the developer did not say that all affected saves are repaired, define normal map-unlock progression, or explain how to distinguish a progression gate from the bug. Do not use a forum sequence as a universal map-unlock rule without a current-build test.

Mission enter and exit crashes

Hotfix #3 said it partially fixed crashes when entering and leaving missions and improved loading. The accompanying technical explanation connected one crash family to memory corruption around a water-plugin shader and said the patch replaced water in heavily affected locations.

Hotfix #4 then listed a fix for the probable cause of crashes while loading into or exiting a mission. Both qualifiers matter. The notes show progressive work on a known crash family; they do not guarantee that every mission transition, driver state, corrupted save, or unrelated crash is eliminated.

A pre-1.0.2 August 23 active-discussion snapshot also includes Full PC Crash, Impossible to play. It is a community recurrence signal from before Major Update 1.0.2, not evidence that the water/shader crash family returned and not proof of a current 1.0.2 recurrence. Without hardware details, a reliable trigger, logs, or a developer response, keep the forum report separate from the official root-cause history.

Double Overwatch freeze

Hotfix #4 lists a fix for a freeze during “double Overwatch.” This confirms an official fix and the phrase used by the developer, but the patch note does not define the triggering sequence or the underlying Overwatch rule.

If a similar freeze occurs, record the acting units, reaction sequence, target, camera state, and whether the save reproduces it. Keep mechanics guidance separate from the dated Overwatch patch evidence.

Soldiers stuck on recon

Hotfix #4 lists a fix for soldiers getting stuck on recon missions. It does not document recon success factors, duration, failure outcomes, or the correct map-progression sequence.

Those rules remain needs live test. A soldier appearing delayed or unavailable is not automatically proof that the original bug returned; capture the recon screen, timer/state, affected soldier, and map context before classifying it.

Characters stuck on city missions

A pre-1.0.2 August 23 Steam community activity snapshot includes Characters are stuck in city mission, describing multiple troops that remain unavailable after a city mission. No official patch note currently confirms this as a known issue, and the snapshot does not establish that the symptom recurs on Major Update 1.0.2.

Do not automatically classify it as the Hotfix #4 recon bug. The official fix names recon missions, while the current community report names a city mission; those may share a symptom without sharing a trigger or root cause. For a useful reproduction, capture the city and mission name, assigned characters, mission completion state, timers, return-to-base behavior, save origin, and whether a new clean save can reproduce the same stuck state.

Status: pre-1.0.2 community report only — not officially confirmed as current on 1.0.2.

VSync and camera behavior

Hotfix #2 temporarily disabled VSync because some players experienced camera issues. No later first-party note reviewed through September 28, including Major Update 1.0.2, explicitly confirms whether VSync was restored.

Current status: unknown pending a Major Update 1.0.2 live settings-menu check. Do not claim that VSync is currently available or permanently removed. A useful capture should include the video settings menu, build/patch context, display mode, refresh rate, and camera behavior.

Barracks construction and crew shortage

The first hotfix fixed a Barracks construction bug caused by a crew shortage after using saves from the playtest version. The trigger is part of the official scope: this was not a general statement about every Barracks prerequisite or every “cannot build” state.

If construction still fails, record whether the save originated in the playtest, the displayed crew count, prerequisites, construction message, and current patch before treating it as the same bug.

Evacuation-zone mission freeze

The first hotfix fixed a mission-script freeze when the last soldier died inside the evacuation zone. The same patch also corrected a voice line related to individual evacuation, confirming that individual evacuation exists as a named retail context.

The note does not establish every extraction-zone trigger, icon, rescue objective, or failure state. Exact evacuation guidance belongs in a hands-on mission test rather than an inferred workaround.

Prisoner movement-debuff stacking

The first hotfix fixed the movement debuff from carrying a prisoner stacking repeatedly. This confirms the affected prisoner-carry state and the repeated-stacking bug.

It does not publish the normal movement penalty, duration, removal condition, reward, or wider prisoner system. Those values should come from the current interface or controlled gameplay, not from another game or an old build.

If an issue still happens

Use a clean, evidence-preserving process:

1. Confirm Steam has finished updating and note the visible version/build information.
2. Verify installation files through Steam before reproducing on an unmodified setup.
3. Disable unsupported file edits, trainers, overlays, and launch options that could change the test.
4. Keep the affected save and a separate backup; do not repeatedly overwrite the only reproduction state.
5. Capture the complete UI, transition, and error rather than only the final frozen screen.
6. Record whether the problem reproduces after restarting and whether a new clean save behaves differently.
7. Report the result through an official Warhounds support or Steam community channel with the current patch and clear steps.

Do not delete a save, edit progression flags, or install an unknown “fix” merely because a community post uses the same symptom name.

Related status pages

• Official patch history
• Platforms, languages, controller evidence, and system requirements
• Trainer, cheats, console commands, and save-location status
• Mods and Workshop support
• Mission types and objectives
• Warhounds FAQ