Kouki

Thanks, we'll look into it

Just to clarify, do you mean that if the bullet it fires goes outside firing cones like this? In this case, this is not necessarily a bug but this happens because the weapon always fires towards the center of the UFO, even if the UFO is only at the edges of the firing cone.

Thanks for taking the time to post a bug report. Do you still have a save when this happened? If so, can you please send it to us so we can take a look?

Thanks for the report! yeah, this is a known issue with the stalker armor, it will be fixed in an upcoming patch

Thanks for taking the time to post a bug report! As fusion-waffle has kindly stated, we need more information as to how these happens. An F11 bug report .zip will help, but we'll also need to know how the soldier moved when the bug happened as that will allow us to reproduce the bug.

Thanks for taking the time to post a bug report. Did the game prompt to create a bug report when you relaunched the game after a crash? If so, can you please send us said bug report so we can look at the logs? We'll need to check what errors are happening to figure out what is causing the crash

Thanks, we'll look into it!

In that case can you check whether your saves are still in Onedrive? We've migrated the save location for Windows 11 saves to <username>\AppData\LocalLow\Goldhawk Interactive\Xenonauts 2\Saves, so if you copy over your saves to the new location, it should work.

Hello, we've looked a bit into your saves and it looks like it was corrupted? If you still have it, can you send us this specific save as it was not included in the compiled bug report. It's auto_strategy_after_combat_166.json and the full directory is on C:/Users/Void Smasher/Documents/My Games/Xenonauts 2/Saves/nakazator/auto/auto_strategy_after_combat-166.json

Thanks for the report, we'll look into it!

Are both PCs using Windows 11, or is one on Windows 10?

Thanks for taking the time to post a bug report! As fusion-waffle has stated, this is intended so that you can start building other base facilities while the generator is under construction. If that was not the case, then you'd have to wait for the generator to finish construction before adding buildings, which can significantly affect your campaign, in a bad way.

Thanks, will have to check with Chris just in case this was a deliberate change,

Looks like you have a mod installed that is causing the crash. Can you remove all of your mods first and see if it can relaunch successfully?

Thanks for the bug report. We'll look into it

Hello there, sorry for the late response. Does the game still generate a free MARS unit when a mission pops up? If that is the case, can you send us a save file before the bug happens (i.e. before the mission pops up on Geoscape)?

There are the supporter effects for the ones in the screenshot. The second and last images are both Security supporters so I've only attached three. Infiltrators as a whole incur +0.5 doomsday increase and +0.5 Elimination OP cost per day

It looks like the floor where the round wreckage is sitting atop of got destroyed as you can jump down from that tile. Although it's strange that there are no frills and that the wreckage did not fall off. We'll look into it and figure out what's going on

Yeah, noticed this as well. Was planning to add destruction effects but haven't had the time yet as of recent. Thanks as always for the reports!

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

Oh hmm, something must've broken quite recently. We'll get it fixed asap

Thanks for the bug report! We're aware of this bug and will get it fixed in a future patch

Thanks, we'll look into it

Can you send us your log files so we can check what errors are causing the game to crash? You can usually find this in Documents\My Games\Xenonauts 2\Logs, under a .log file named "output". If you can attach said file when you make a reply, we can check so that's causing the bug. I'd suggest doing a clean install as outlined by fusion-waffle too, especially if you've owned the game at any point in time prior to the 1.0 release.

Thanks for the report! We're aware of this issue and this will be fixed in a future patch!