[Milestone (Prototype) v2.06 - Geoscape] CTD after accessing squad screen via 'Armory' or 'Launch Combat Team'.

[CompoTheSmoggie]

Description: CTD after clicking on 'Armory' Tab or 'Launch Combat Team' to Crash Site-1 (Scout).

What Happened: After downing the UFO, I tried to send Skyhawk-1 to the UFO crash site. The game temporarily freezes and then crashes to the desktop. On reloading the Day 36: After Interception (Auto) and trying to access the 'Armory' tab, it also freezes and crashes to the desktop as well.

Mods: WeMod 'Xenonauts 2 - 01/08/2023 (Build 2) used previously for 'Infinitive Money' cheat, hence 'Funds Available $826,542,300'.

Any Remedial Action: Clean install performed (manual deletion of files in 'My Documents/My Games/Xenonauts-2' as well as 'C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2') but issue is repeated with backup saves on a clean install. I have tried to 'Collect Bounty (+100,000) and access the 'Armory' tab, again freeze and crash.

Additional Info: Couldn't find an 'output.log' in the 'Logs' folder, only a 'resolve_layers.log' so I've attached that. In the saves folder I had a 'steam_autocloud.vdf' file so I don't know if that's any use in fault diagnosis. I've also included the 6 json files from out of my 'Settings' folder in the 'My Documents/My Games/Xenonauts-2' folder.

auto_strategy_after_intercept-20.json resolve_layers.log steam_autocloud.vdf audio.json display.json general.json input.json mods.json profile.json

Edited October 6, 2023 by CompoTheSmoggie
Added that version is 'Prototype'.

[Kouki]

Thanks for reporting the bug! Is this a new campaign after the 2.06 patch or one carried over from an earlier version? There was a bug from 2.04~05 that caused CTD on clicking armory that should have been fixed on 2.06, however if you're using a save file carried over from a campaign in an earlier prototype version (like 2.05 or earlier), that might still cause crashes when entering armory.

[CompoTheSmoggie]

@Kouki

Thanks for coming back to me with a reply so promptly.

It's a new campaign on milestone 2.06. I usually delete and wipe missions that have ran on a previous version and restart on a new version.

I run the cheats, rather unashamedly, to progress the game faster and hence to get any bugs that are going to appear, early in the game.

There's nothing worse than getting to say, completing all the research at day 170 and then the game CTD's.

Best regards,

Compo

(Xenonauts-2 Username = Mykolas Kumpaitis)

[SoftwareSimian]

I just ran into that. Around day 180, trying to deploy to Terror Site. However my current campaign was started in v2.04 I believe so I'm probably subject that that already-fixed bug. But just in case, I'm attaching the logfile and a savefile from a couple days earlier, just in case it's useful.

user_day_177_manual_save-109.json output.log

[Kouki]

11 hours ago, CompoTheSmoggie said:

@Kouki

Thanks for coming back to me with a reply so promptly.

It's a new campaign on milestone 2.06. I usually delete and wipe missions that have ran on a previous version and restart on a new version.

I run the cheats, rather unashamedly, to progress the game faster and hence to get any bugs that are going to appear, early in the game.

There's nothing worse than getting to say, completing all the research at day 170 and then the game CTD's.

Best regards,

Compo

(Xenonauts-2 Username = Mykolas Kumpaitis)

I see, that's interesting. We'll have to check into this because if this is indeed a new campaign, then that means a bug that should've patched out on 2.04 is back.

 

6 hours ago, SoftwareSimian said:

I just ran into that. Around day 180, trying to deploy to Terror Site. However my current campaign was started in v2.04 I believe so I'm probably subject that that already-fixed bug. But just in case, I'm attaching the logfile and a savefile from a couple days earlier, just in case it's useful.

user_day_177_manual_save-109.json 741.56 kB · 0 downloads output.log 2.95 MB · 0 downloads

Most likely related bugs I'm afraid, the CTD on OP's post is caused by a nullref on skylance torpedo, while yours was caused by another nullref on alenium torpedo. We'll take a look into this and get it patched out, thanks for reporting the bug!