Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also, when saving in campaign missions you can use one of the other save slots.
The main difference is that for the corrupted saves, I previously removed some units from the repository, and these units are still ingame. Moreover, I've removed some unused parts of removed units that are still in game too.
Here is the step I think will reproduce the problem:
- create a new game, with a factory (inside a campaign for me)
- create a new unit
- clone a structural part
- modify it (I'm not sure it is mandatory, but it will ensure the original part cannot be used inplace)
- create a unit around this modified part (I tried with wheels, a computer and a battery around a bended stuff, but here again I think the only modified part can constitute the unit to trigger the bug)
- build it with the factory
- save
- enters the repository
- remove the previously created unit
- remove the previously created part
- restart the game (mandatory ?)
- reload the save : it should crash before displaying the continue button
In case of, I've a backup the directory before and after the operation.
A patch will be issued very soon that will resolve this problem. In the meantime, until the patch is available, please avoid removing unused modules while on a mission.
Thanks for the report!