• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Status
Not open for further replies.

DavyDavy

Community Developer
Paradox Staff
Sep 25, 2019
67
50
Greetings, Survivors!

We just deployed a hotfix for Surviving the Aftermath on Xbox and PC. This update will bring your game Version to 1.1.5128 on PC, and 1.1.1.28 on Xbox.

General
  • (PC Only) Implemented a fix that solves the mod installation issues with the Paradox Launcher.
  • Improved the performance of colonist simulation.
  • Improved the performance of Work Areas
  • Fixed an issue that caused the World Map actions to get stuck after killing a bandit.

Gameplay
  • Colonists will now correctly enter the Medical Tent instead of going to the corner of the building.
  • Specialists can no longer die instantly in the most hazardous locations.
  • Unused Vaccine resource removed from the Warehouse input list.
  • Reduced the trading costs of the Wandering Merchant event, and removed rare resources from the payment options.
 
Just a couple of minor things post-hotfix: on Xbox, tabbing bewtween specialists with LB/RB all the specialists have the same name. I renamed one of them, don't know if that's related. Moving over them manually without using LB/RB shows their names correctly. Also the comma between the name and the specialist's function looks weird - it's below the final letter of their name, not to the right of the final letter. Very minor, I know, it just looks...weird :)
 
Survivors did not reset after Quit and a Save reload.
Prior to this happening, the worker in the Medical Tent died from exhaustion and hunger; even after I unassigned him from the Tent (after I noticed the red skull icon), he continued working there until his death. Dedicated little bugger. :rolleyes:
 

Attachments

  • sta-stuck runners.jpg
    sta-stuck runners.jpg
    414,5 KB · Views: 16
Well, I don't know if this is a different issue - still having stuck runners, but the output log shows a different error. Hope it helps you guys troubleshoot.

I'm gonna shut down my pc and call it a night. All the gameplay so far has just had a game reload. Let's see if there's some memory remnants in some corner of my machine that would release those pesky gremlins that got the survivors stuck. Fingers crossed. Because the current state is I cannot do my modding projects and cannot play the game. I wish I had backup the program files to revert to and play offline...
 

Attachments

  • output_log.txt
    14,6 MB · Views: 4
  • Autosave-NewCaledonia.save
    322,9 KB · Views: 2
Colonist get stuck running in place - Not sure if I can trace it to placing new buildings in later stage colonies.

Not sure if it's related but I notice stuck colonist running in place and that prompts me to try to do a quick save/load, because after this or the patch before, saving unstick colonists. Though the game must have figured it out, because now manual, quick and autosave all stop working, have to load or restart the game to allow saving for a while again, it does seem to allow going past the old stuck point.
 
On xbox one x, bottom of the map right before the border, everytime I try to scout the area it locks everything up as soon as they do the scout animation. The area reveals the resource but doesn't light up then everything stops working. This happened about a couple days back but I just stayed away from the area. But running out of map so I tried again. I will be restarting the game on a new save.
 
All,

Could you please attach the game save (for Windows this is typically in your My Documents\Paradox Interactive\Surviving the Aftermath\SaveGamesand Folder) and the output_log.txt (typically in your AppData\LocalLow\Iceflake Studios\Surviving the Aftermath) files to your postings to help the dev's..

Thanks..
 
I'm experiencing the same running in place and unable to save the game. I haven't found a pattern for how many or which actions cause the problem after loading a savegame. Running on Windows with the build mentioned in OP, no mods (never DL'd any).

Interestingly, one time, after the problem happened: Random clicking of unassign workers from buildings and re-assign workers fixed the problem and I could save the game again and the running-in-place workers were gone.
 

Attachments

  • 2019-11-19_20-26-21.save
    502,5 KB · Views: 2
  • output_log.7z
    4,4 KB · Views: 2
Last edited:
Status
Not open for further replies.