Kouki

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!

As fusion waffle has kindly pointed out above, there's currently a bug in the game wherein losing (due to panic reaching 100 in 2+ regions) will immediately bring you back to the main menu instead of showing the game over screen first. We've released a 6.30 update recently which solves this issue, can you try updating to the latest version? Thanks!

Thanks for the report! Not sure if this is necessarily a bug but I'll bring this up with the rest of the team.

Thanks, we'll get it fixed!

Thanks for taking the time to post the timestamps for the video. It looks like the pop-up dialogue being out of order happens because the uoo bombardment panic happens prior to the bombardment pop-up, as such the 100 panic pop-up is triggered after the damage, before the actual bombardment pop-up happens. We're reversing that order (bombardment pop-up before region panic is applied) so that this doesn't happen again. As for the other bug you've mentioned, will bring this up with the rest of the team so that it gets fixed, thanks again!

Thanks for the response! We've included a fix for this on the recently released 6.30, let us know if you experience any other bugs!

Thanks for the response!

Thanks for the bug report! We'll look into this, although do you have a save by any chance?

Can you send us the .zip file so we can take a look at what's going on? Simply drag and drop said zip file when making a reply and it should get attached automatically, thanks!

The game's logs and the screenshot from the F11 bug report will help us a lot in this case, as it'd narrow down the scenarios that cause said bug. I did some testing on my end and found that the grenade throw is more likely to hit the ceiling in the base defense maps if the throw target is quite far away, although I'm not sure if this covers all cases of grenade throws hitting ceilings.

Hey there, thanks for taking the time to post these bug reports! The detailed breakdown is very much appreciated. We'll look into this mind control issue and figure out what's going on. Though we would very much appreciate if you can press F11 whenever you spot a bug. This will generate a .zip file with the logs and potentially useful saves that will save us a ton of time in figuring out what's going wrong. Thanks!

Thanks for the very detailed report! Yeah, it looks like having your soldier crouched affects the move attack preview's accuracy calculation, we'll get it fixed.

Thanks for the report! We'll get it fixed