Tempest Rising patch notes explained: explore Hotfix #13 campaign fixes, Veti achievements, crash repairs, and the Hotfix #12 changes that still matter.
Jump to
Latest verified facts — Checked October 22, 2026 against the official store listings: Steam
Tempest Rising was released on April 24, 2025.
Platforms: Steam, Windows.
What Changed in the Tempest Rising Patch Notes?
A campaign victory should survive its own ending cutscene, and the October 7, 2026 Tempest Rising patch notes address exactly that problem. Hotfix Update #13 fixes campaign completion issues, Veti achievement tracking, gameplay bugs, and several crash triggers. These Tempest Rising patch notes matter whether you are returning to a blocked mission, tackling Hard difficulty, or trying to finish an achievement run.
Hotfix #13 concentrates heavily on the Veti Campaign, with additional changes affecting the base campaign, skirmish, and player-created maps. Hotfix #12, released July 10, 2026, addressed older saves, multiplayer production queues, and Map Editor problems.
Update
Announcement date
Main changes
Hotfix Update #13
October 7, 2026
Campaign completion, Veti difficulty, achievements, gameplay behavior, and crashes
Hotfix Update #12
July 10, 2026
Loading older saves, multiplayer production queues, missing Tempest Fields, and editor fixes
For returning players, the useful distinction is between a mission blocker and a gameplay correction. An evacuation that could not finish needs another attempt. Missing enemy attacks returning on Hard and Insane, meanwhile, changes what you should prepare to defend against.
Read the Tempest Rising patch notes around the problem that interrupted your run. Campaign players should start with mission completion and difficulty; multiplayer players should check unit behavior, production queues, and the surrender-related crash fix.
Campaign Fixes: Mission Endings, Difficulty, and Map Readability
The base campaign receives a targeted progression fix: Dynasty Mission 10 no longer has the issue that made evacuating Aleks impossible. If that evacuation stopped your campaign, return to the mission and retry the objective after updating.
The Veti Campaign receives a broader set of repairs. Two involve missions failing around their ending cutscenes, while another restores enemy attacks that were missing on higher difficulties.
Campaign or mission
Problem addressed in Hotfix #13
Dynasty Mission 10
Aleks could not be evacuated to finish the mission
Veti Mission 7
The mission could fail after its ending cutscene
Veti Mission 10
The mission could fail during its ending cutscene
Some Veti missions on Hard and Insane
Missing enemy attacks made missions too easy
Veti Mission 10 ending
Heavy blur could obscure the screen
Veti Mission 2 ending
Subtitles did not match the voiceover
Some Veti mission openings
Performance dropped sharply during the opening seconds
Veti Mission 7 and some campaign minimaps
Distorted object textures and inaccurate minimap layouts
Prepare for attacks on Hard and Insane
The difficulty correction deserves attention before you resume a Veti challenge run. Some missions had been easier because enemy attacks were absent. Hotfix #13 fixes that behavior.
Prepare your defenses for incoming attacks instead of relying on the quiet stretches you encountered before the update. If an earlier attempt gave you room to build without pressure, reassess that plan when replaying the affected missions.
This change also matters when interpreting the Tempest Rising patch notes alongside the Veti Warkeeper achievement fix. Hard difficulty now has both a correction to missing attacks in affected missions and a correction to the achievement's difficulty requirement.
Revisit interrupted endings and opening performance
For Veti Missions 7 and 10, retry the affected ending if a cutscene previously turned a completed objective into a failure. Mission 10 also receives the blur fix, addressing a separate visual problem during its outro.
The opening performance fix applies to the first few seconds of some Veti missions. It targets that specific slowdown. Keep the timing in mind when comparing how an affected mission starts after updating.
Map readability receives attention, too. Some Veti campaign minimaps now better match their actual layouts, and Mission 7 has fixes for distorted textures on certain objects.
From Hotfix #12, remember the missing Tempest Fields correction in Dynasty Mission 4 and GDF Mission 10. Revisit those missions if missing fields disrupted your earlier attempt.
Gameplay, Multiplayer Queues, and Custom Map Changes
Outside the campaign, the Tempest Rising patch notes address several situations where units, production orders, or map objects behaved incorrectly.
The Comms Rig fix is especially relevant if you use Intel Mode with autocast disabled. Previously, ordering it to move could switch it into Comms mode. Hotfix #13 removes that unintended mode change.
Area
Update
Fixed behavior
Comms Rig
Hotfix #13
Movement orders could switch Intel Mode to Comms mode with autocast disabled
Caretaker
Hotfix #13
Facilitation mode allowed Ascension Anchor placement without using Enlightened
Veti skirmish AI
Hotfix #13
The bot could build excessive defensive turrets
Player-created maps
Hotfix #13
Neutral buildings were missing from the map or minimap
Multiplayer production
Hotfix #12
Shift+LMB orders were distributed unevenly across selected production buildings
Production queue display
Hotfix #12
Totals displayed incorrectly above 255 queued units of the same type
For the Caretaker, the update closes the Ascension Anchor placement loophole in Facilitation mode. Use Enlightened when placing an Anchor through that mode; the previous behavior allowed placement without it.
The skirmish correction addresses excessive defensive turret construction by the Veti bot. If a previous match became dominated by that behavior, retry the matchup after updating to assess the corrected AI behavior.
Check production orders and queue totals separately
Hotfix #12 includes two distinct production fixes. In multiplayer, adding orders with Shift+LMB while multiple production buildings were selected did not distribute those orders evenly. Separately, queuing more than 255 units of the same type across multiple production buildings could produce an incorrect displayed total.
Use the corrected distribution when managing production across selected buildings, and check the queue total when preparing a large batch. The number 255 describes the display bug's trigger; it is not presented as a production limit.
Another visual fix addresses dead infantry appearing to remain standing when the camera was elsewhere at the moment they were killed.
Recheck custom maps and editor examples
Hotfix #13 restores neutral building visibility on player-created maps and their minimaps. Recheck those buildings when testing a custom level that previously appeared to be missing them.
Hotfix #12 also fixes three Map Editor and Workshop issues:
Seeing the downloaded Workshop version of SetdressingExampleMap in the game.
If your editor test stopped at one of those points, repeat that specific action after updating. These repairs address launching, mod creation behavior, and downloaded content visibility.
Achievement Fixes: What to Retry and What Requires Hard
Achievement hunters have several reasons to revisit the Tempest Rising patch notes. Hotfix #13 repairs Veti-related achievements that either failed to unlock or could unlock under the wrong conditions.
The clearest difficulty correction affects Veti Warkeeper. Completing the Veti Campaign on Normal could previously award it, even though the required difficulty is Hard.
Achievement
Change in Hotfix #13
Veti Warkeeper
Corrects the erroneous award for Normal completion; the requirement is Hard
Deprived
Fixes failure to unlock after completing the Veti Campaign without Doctrines and Armory equipment
Anchorless
Fixes erroneous unlocks in other modes without meeting its requirements
Same-Day Delivery
Fixes an issue preventing Veti Support Powers from unlocking it
Fortress of Solitude
Fixes failure to unlock after building 50 Veti walls
Plan around the corrected requirements
For Veti Warkeeper, complete the Veti Campaign on Hard. A Normal completion was the incorrect trigger addressed by the update.
For Deprived, complete the Veti Campaign without Doctrines and Armory equipment. If you previously met those conditions without receiving the achievement, the hotfix addresses that failure.
Keep both restrictions in view throughout a Deprived attempt. Avoid adding Doctrines or Armory equipment during the run you intend to use for that achievement.
For Fortress of Solitude, the relevant repaired trigger is building 50 Veti walls. Retry that building requirement if your earlier attempt reached it without an unlock.
Separate repaired triggers from corrected false awards
Same-Day Delivery had a problem involving Veti Support Powers: using those powers could fail to unlock the achievement. Hotfix #13 repairs that interaction.
Anchorless had the opposite kind of issue. It could unlock in other game modes without its requirements being fulfilled. The fix corrects those erroneous awards.
That distinction helps you decide what to revisit. Deprived, Same-Day Delivery, and Fortress of Solitude involve unlock failures. Veti Warkeeper and Anchorless involve awards happening under incorrect conditions.
The update also fixes a campaign crash associated with fulfilling an achievement condition. If an achievement attempt ended with a crash, review the stability changes before retrying the affected campaign objective.
Save Loading, Crash Fixes, and Your Return Checklist
The stability changes in the Tempest Rising patch notes cover specific triggers rather than a single broad crash issue. Hotfix #13 addresses achievement conditions, Ascension Anchor relinking, and a match-ending interaction with the superweapon widget.
Hotfix #12 handles a separate loading problem involving saves created before patch 1.9.0.
Trigger or affected content
Update
Repair
Saves created before patch 1.9.0
Hotfix #12
Fixes an endless loading screen when loading affected saves
Meeting a campaign achievement condition
Hotfix #13
Fixes a possible crash
Relinking an Ascension Anchor
Hotfix #13
Fixes a possible crash
Opening the superweapon widget as an opponent leaves or surrenders
Hotfix #13
Fixes a possible crash
If you left an older campaign behind because its save loaded forever, retry that save after updating. The relevant Hotfix #12 change explicitly covers saves made before 1.9.0.
For an Ascension Anchor crash, retry the relinking action that previously caused the problem. For the superweapon widget issue, the repaired situation involves opening the widget when an opponent leaves or surrenders.
Use this checklist to focus your return:
Retry Aleks's evacuation in Dynasty Mission 10.
Revisit failed Veti Mission 7 or Mission 10 endings.
Prepare for restored enemy attacks in affected Hard and Insane missions.
Retry an achievement condition that previously failed to register.
Load an affected pre-1.9.0 save.
Test the specific custom map or editor action that previously failed.
If an issue persists, submit a support ticket describing the action that triggered it. Include an image or video to make the problem easier to assess.
What do the October Tempest Rising patch notes change?
Hotfix Update #13, dated October 7, 2026, fixes campaign completion issues, missing Veti enemy attacks on Hard and Insane, achievement bugs, gameplay behavior, and crashes. It also addresses campaign visuals, minimaps, and opening performance drops.
Can Veti Warkeeper unlock on Normal difficulty?
Veti Warkeeper requires completing the Veti Campaign on Hard. Hotfix #13 fixes a bug that could award it for completing the campaign on Normal.
Which update fixes older saves getting stuck loading?
Hotfix Update #12, released July 10, 2026, fixes the infinite loading issue affecting saves created before patch 1.9.0. Retry an affected older save after updating.
Does Hotfix #13 fix the Aleks evacuation problem?
Yes. Hotfix #13 fixes the issue that prevented evacuating Aleks to finish Dynasty Mission 10. Return to that mission and retry the evacuation if it previously blocked your campaign.