Well, instead of all posting crash reports in the main topic, I thought it might be better to make a new one, where we can all share our evidence, so as to make it easier if ever someone wants to look at it.
The BASIC, MINIMUM
requirement for a report is a save, with a description of what to do to get a crash. Ideally something as simple as "press end turn, shooting happens then the game crashes". Try to make a save as close to the crash as possible (ie just before pressing end turn) so that testers don't have much to do.
Extra info that is useful:
1 - Screenshot of the offending unit
2 - Info about the offending unit and how to circumvent the bug.
To get the extra info, it is sometimes useful to activate debug mode. You do that by going in your config folder (check here
for where that could be on your computer), open the file called options.cfg
, find the place where it says debug: false
and replace it by debug: true
. Then, in the game, before pressing the end turn button, press control-d, to activate the debug mode. This will allow you to see the whole map and watch as the enemy takes their turn.
Find which unit is active just before the game crashes and take a screenshot. Note the position of the offending unit, and then you can use that to find it in your save. For example, if the unit was shown as being at location (35,42,1) when you clicked on it (as shown in my screenshot below), you can then search your save for "- 35
" and should soon find a place that looks like:
which should refer to an enemy unit (something like STR_SPARTAN_RIFLEMAN
) Then note the id
of that unit (typically something like 1000012), as it will allow to see all its items by searching for owner: 1000012
. You can remove these items from the save, and see if the crash still happens.
Below is my first report:
1 - Save at deployment. Game will crash after Spartan Rifleman at 35/42/1 opens the door to the civilian.
2 - Screenshot of offending rifleman
3 - Removing equipment from the save did not help. Probably terrain issue?