Kouki

Yeah it's currently a known issue that we'll address eventually, atm we're focused on pushing out milestone 2 so unfortunately it may take a while! Thanks for reporting the bug.

Oh that is indeed a mistake, thanks for reporting it!

Thanks for reporting this bug, we've made a fix for this and it should be out on next patch!

Yeah it's a known issue for the Pegasus because it doesn't load in properly into the Geoscape, we're working on it, thanks for reporting the bug!

Používám chatGPT k překladu do češtiny, takže se omlouvám, pokud bude těžké to pochopit. Můžete mi poskytnout soubor se uloženými daty, abych se na něj mohl podívat? Pokud ano, postupujte podle návodu na odkazu níže a přiložte soubor k odpovědi. Můžete vložit webový odkaz, který jsem poskytl níže, do Google Překladače a jednoduše ho přeložit do češtiny. Stačí, když odkaz na web vložíte jako na obrázku, který jste připojil k této zprávě. Děkuji! To raffik: Thanks for translating for us!

Yeah, it's part of an experimentation we forgot to remove before publishing the prototype build, we'll get it patched out, thanks for reporting it!

Yeah it's what happens when the ladder is not destroyed even though the container is, thanks for reporting the bug though! It's a known issue and we're working on it.

Thanks for telling us about the bug, though as softwaresimian said, a save file would be very helpful to allow us to understand the situation that leads to the bug. Please refer to this post to know where to access your save and upload it here so we can take a look into it.

Thanks for the report, that's currently indeed one of the new issues introduced by the recent changes in the armor system for 2.02. We're currently working on a fix for it!

Hello there, thanks for the bug report. It's currently a known issue that tooltips block information for the modules in armory. Though I believe we're reverting to the previous module system after feedback from the playtesters. Thanks for the report though!

Hello Kent, thanks for telling us what happened. It would help us a lot if you can provide the save file for the campaign where this happened. This will allow us to directly investigate the cause for the error. It also provides the information we need when reproducing the bug (what version of the game you're running, what kind of error it is, etc.) To provide the relevant save file for us. You can do the following steps: 1. Load the campaign wherein you encountered the error 2. Save the campaign and name it in a way that makes it easy for you to remember. 3. Look for the save, your save files are located in one of the save folders in Documents/My Games/Xenonauts 2/Saves 4. Make a reply on this thread 5. Drag and drop the save file you've named(which comes in a .json format) to the post you're making, the file should attach on its own. Like so 6. Submit reply (I've attached some images, to make it easier to understand I hope it helps)

Thanks a lot for providing the save! Yeah it's probably related to the fix with the infinite sell bug fix released on 2.02, thanks again!

Thanks for reporting the bug, can you upload the save? It'll save me time if I can check the bug right away! Thanks!

Thanks for the report. Can you attach the save file so I can take a look at it, it'd also be helpful to know what version of the game you're playing on (though I can check that when I get your save file)

Thanks for the report. For the first bug, that's a known issue that happens when a teleporter is damaged by a demo charge and other explosives. We're working on that atm. For the second bug, is it a small ufo? It's possible that you might've gotten the observer UFO, which has an upper level. If not then can you upload the save here? For the warden armour, by adding it multiple times, do you mean in dropship or in garrison(unassigned)? The way the item system works, items are only counted as used if it is equipped in the dropship, if you equip garrisoned troops, it won't count because they item is only considered being used when in the dropship screen. If that's not the case, attaching the save will help a lot!

Thanks for attaching the save! We'll take a look into it at and see what's wrong. Thanks!

Thanks for telling us about the bug you've encountered! Can you try updating to the 2.02 prototype? We already had a fix for this specific bug for 1.7 but accidentally wasn't able to include it in milestone 2 prototype, I've tried reproducing this bug last Friday and it should be fixed now tho! Do tell me if it isn't just in case, thanks!

Thanks for the report! We've got several reports regarding that issue and a fix is being worked on right now and should be included in the next patch.

You've probably already seen it but replying just in case! The 2.02 prototype patch should fix the CTD error. It's been released yesterday by Chris. Hope it helps!

Great, thanks for attaching the save. Unfortunately I can't replicate the crash on my end, though I did get some errors. We'll take a look into it and get it fixed. Btw in case you might want it, I've attached a manual save after accepting the victory screen below (which seems to be when the CTD happens for some people), I can't guarantee anything but maybe it might allow you to continue playing on your campaign? Hope it helps. EDIT: The save will most likely cause a crash on your next ground combat mission. Though there's already a fix for this error that should be included in the next patch. user_day_24_raffik-2.json

Hello Raffik, thanks for reporting the bug. Can you upload the save file and logs (if there are any). We've been getting a bunch of CTD bug reports on the 2.0 prototype build and it'd help us a lot if you can provide the save.

Woops, my bad. Asked chris to make sure and yep you're right. This is indeed normal behaviour and not a bug.

Thanks for the report, took a look into it and it seems like the recent patch has caused this. We'll get it fixed asap.

That's weird. Tested your save and seems to be the same for me as well. Interestingly the cover works depending on how far you are shooting from. I'll talk about this with the programmers and see if we can fix it for the next patch. Thanks for the report

Thanks for reporting the bug. That's interesting, I was able to reproduce it on my end as well. We'll get it fixed asap (depending on whether there are more urgent bugs to be squashed first!)