Kouki

This should be fixed as of 7.27.7, which is currently in the experimental branch of the game. Thanks again for taking the time to post the bug report!

We've released 7.27.7, which should include fixes for the loading screen tip!

Yeah, looks like the randomization is not working properly for the tips. The tips displayed will vary from user to user, but it will always display the same sequence of tips. In my case it was the teleporter tip. We'll look into it and get it fixed

Hello there, sorry to hear that this bug ended up taking and wasting so much of your time, but the detailed bug report is very much appreciated. I thought I've fixed all of these bugs, I looked into this and it looks like a spawn point was placed barely on the edge of the ufo hull, which made it barely clip into it, this caused the servitor to get stuck inside the ufo. This has been fixed and will be deployed in a future patch.

Hello there, thanks for taking the time to post a bug report! Can you send us your save so we can take a look? If you press F11 the game should compile a bug report, we can then check the saves or logs to see what exactly happened.

Thanks for taking the time to post a bug report! I'll do a bunch of tests on my end but if you can provide a save then we'd appreciate that too. When you think it's happening on a mission, press F11 and let the game compile a bug report. Once the bug report .zip is made, can you please send that to us so we can take a look? Thanks again

Thanks for the bug report! We'll have to investigate what went wrong here. One thing I want to point out though is it looks like you have one save file that got corrupted. If you delete said save, it will help prevent crashes in the future from happening. I'll bring this up with the rest of the team as well as it looks like the corruption was recent (8/3)

Hello there, thanks for the report! 1. We'll need a bug report for this one, this gets reported every few months or so but we haven't found a way to reproduce this on our end so figuring out what's causing the bug is a bit hard. Ideally, a way to reproduce the bug with the save is the best as we'll be able to figure things out right away, if you have a save like this then that'd help us tremendously, if not that's totally okay as this one is a rather niche bug and requires specific steps to reproduce sadly. 2. I'll need a save for this as well, it's possible that the roofs for the building where you threw on top of it were bugged and need fixing (HP too high, or wrong roof type painted, etc). Do note demo charges do more damage to structures than grenades so demo charges will destroy more floor tiles than standard grenades. If on both cases the same grenades were used, this is hinting strongly towards a genuine bug that we'll need to check as it can either be a roof issue or a grenade issue.

Yeah, those issues come from the same issue as well, so the fix should sort those out as well : Glad to know you're enjoying the game! This version should be relatively stable so there shouldn't be too many bugs to worry about

Yeah, it would most likely affect cover. We've made a fix for it but it probably won't get deployed to the live build of the game for awhile as the fixes will break a lot of saves.

Thanks for the bug report! Can you try switching to experimental and then try to load in the ground combat mission (load from the geoscape before combat autosave)

Thanks for taking the time to post a bug report, the f11 saves allows us to repro the bug. We'll look into it and get it fixed

It looks like there's a corrupted save in your save folder. Deleting it should solve the issue. In Main Menu, click "Save Folder" once that opens, open the folder named "saves" and then delete this save "user__300_manual_save_created_2026-07-01-07h41-293".

Thanks for the report! Looks like the doors are bugged here and while visually it's opened inwards, the gamelogic is showing as it opening outwards instead. The 4 AP cost difference is the cost for opening/closing the door. We'll get this fixed

Thanks for the report, something probably broke it when we fixed a different issue, we'll look into it

Thanks for taking the time to reply! No problem, let us know if it happens again so we can look into it!

Thanks for the report! We'll look into it after the weekend (once the rest of the team is back)

Hello there, sorry for the late reply and thanks for taking the time to post a report! I downloaded the save and it looks like this might be the wrong one? The save is from a soldier rescue mission in the early game and there are only cleaner soldiers as your enemies. If you can send us the correct save, we'll give it a look. Thanks again!

Hello there, was the armour equipped on an unassigned soldier? Loadouts on unassigned soldiers do not take away equipment from your base stores. It's meant to represent what they will be using once they're moved to an active dropship. As such, unequipping stuff from unassigned soldiers will not add back to your equipment pool, as they were not taking any in the first place. If the armour disappears from a soldier assigned on a dropship, then this might be a bug. Can you send us a save we can look into? Ideally one where we can attempt to reproduce the bug, thanks!

Hello there, I've forwarded this to our programmers so they should be replying sometime soon. The post is more likely to get tripped up by the automated spam detection if there are links in it as there are tons of bots that post spam in the forum every week. Iirc there's currently no way to flag a person as a non bot (my post replies get flagged as well every now and then).

I'll double check but iirc this is a known issue that is fixed in our dev build. This will come out in the future as part of a larger patch

Thanks for the report! There is a known issue with AC autoresolve which we discovered and made a fix for. This should come out in 7.25.1, which should come out in experimental fairly soon.

Thanks, we'll get this fixed!

Thanks for taking the time to post a bug report! This is a known issue with the specific wall material on AMD cards, we're working on fixing it but it will take some time

Sorry for the very late reply, but we've looked into this issue and it should get fixed in a future patch.