Kouki

Thanks for the report! As fusion-waffle kindy stated, whenever a game crashes it generates a bug report .zip file in My Documents/My Games/Xenonauts-2/BugReports/. Simply drag and drop it when making a reply.

Thanks for the report! You might need to manually delete the entire game, I'll outline the steps below. - Locate install directory of the game (On Steam, right click the game -> Properties -> Installed Files -> Browse...) - Once the install directory is located, uninstall the game in Steam. - Once game is uninstalled, delete the xenonauts 2 folder - Go to Documents/My Games - Delete the Xenonauts 2 folder - Once everything above is deleted, reinstall Xenonauts 2

Thanks for the report! Can you send us a bug report when this happens again? Pressing F11 will prompt the game to generate a bug report, which should give us some idea as to what's going on.

Thanks for the report! Your comment describing the bug happening after loading the save has allowed us to reproduce a case for the unpathable pegasus walls. It looks like the walls become pathable when you load an existing gc save. We'll look into it and figure out what's going on, thanks again!

Thanks, we'll keep on the lookout as to what's causing this to happen.

Thanks for taking the time to post a bug report! We're aware of this issue and this will be fixed in milestone 7!

Thanks, we'll look into this.

Hello there, thanks for the bug report! Just to make sure, was the ground combat mission here newly generated in 6.30.1? We made a few changes on the pegasus a few patches back to fix a bug that will cause an issue if you loaded a save from an older version of the game.

Thanks for the bug report! The first issue (smoke grenade thrown not generating smoke) is an issue that we've also encountered on testing last week, we're working towards figuring out what's causing said bug. For the other bug (smoke not propagating to lower levels when thrown on higher elevation), I'll have to double check with the team as I'm not sure whether this is intended behaviour or not.

Thanks, will bring this up with the rest of the team.

Thanks for the report! Can you send us a save of your campaign so we can give it a look? The ideal save is one prior to the laser battery upgrade completing but any save will help. You can also press F11 to generate a bug report file, then upload said bug report file here.

Thanks for the report! I will double check this with the rest of the team as I'm not sure whether this is a bug or an intended interaction.

Thanks for taking the time to post a bug report! Did the game generate a bug report .zip file when it crashes? It usually automatically makes one and this is usually located in Documents/Xenonauts 2/BugReports (same directory you got the output.log file) If there's no bug report file, can you try loading the save again and see if it crashes? If it does, can you relaunch the game and see if it prompts you to create a bug report file? If there's no such prompt, can you press F11 so the game can manually compile a crash report for us to look into? Thanks!

Yeah, that is my suspicion as well, thanks for the input!

I made a reply on the Discord thread (I presume you're azab0128?), I'll be pasting it here as well. Thanks for taking the time to post a bug report! By a hard crash do you mean that your PC crashes or is it just the game? If it's the former, then we'll need more information, I'll list down a bunch of stuff below that would help us figure out what is going on. Have you also changed any hardware recently? If so, please let us know as well. Error Codes - If this was a BSOD, then it should display a stop code. If you can send us the stop code then it'll help a lot in identifying what caused the crash. Memory dumps - Press Windows key, in the search bar type '%systemroot%', this will open your Windows folder. Check if the folder 'Minidump' has anything in it or if there are any .dmp files generated. Event Viewer Logs - Press Windows key, in the search bar type 'event viewer' and open it. Once it's open click Create Custom View on the right hand side of the window. On the Logged option, select the option that covers the timeframe when your system last crashed. On Event level, select 'Critical'. And on the Event Logs drop down, click on Windows Logs. Press OK then it should generate a custom view that lists down the critical errors that happened within the timeframe you selected. Next, click 'Save All events in Custom View As' and which will prompt to save the logs in .evtx format. Send us this log as well so we can give it a look. Hardware information (dxdiag) - Press Windows key and type 'dxdiag' in the search bar, once it opens click Save All Information... on the lower right side of the window, then send us the file generated. Hardware info pt.2 (msinfo32) - Press Windows key and type 'msinfo32' in the search bar, open the result named System Information. Once it opens, click File and then Save. Then send us the .nfo file which will contain information about your hardware.

Thanks, we'll look into this

Thanks for the bug report! We'll look into this and try to figure out what's going on, though by any chance do you have an end of turn save too? (An F11 .zip file would help a lot too). The start of turn save after a bug happens doesn't really provide us with the repro case as the bug has already happened and there is no logging. If possible can you press F11 when bugs like these happen the next time? Thanks again!

Thanks, we'll look into it!

Hello, sorry for the very late reply but it looks like you posted a Xenonauts 2 bug report in the X1 forum. There were a bunch of loading errors that was fixed in the patches leading up to 6.29, which is currently the public release build, are you still experiencing crashes when loading into missions?

Thanks, we'll get it fixed

Thanks, we'll get these fixed!

Thanks, looks like the wrong type of wall was used here, we'll get this fixed!

Can you send us a save from your campaign so we can give it a try? Thanks!

Can you send us a save from your campaign so we can give it a look? Thanks!

Nice catch, we'll look into it!