waju

I was assuming a cross-dresser. My special forces unit is Progressive! My next recruiting spree, I hope to net Ru Paul, Dennis Rodman, and Strom Thurmond.

I have two troops named Kei Tachibana. one guy, one girl. Not sure how to take this.

Except that they won't do any fighting! They just lounge around in the infirmary, ordering stuff off of infomercials.

Not anymore it doesn't ((Insert Evil Laugh))

It's been back and then out onto another mission and back.

My dead soldiers have stayed on my payroll. You can dismiss them, but that seems rude. The game should take care of all such arrangements.

Confirmed

I was offline yesterday, and actually happens twice. I got a screenshot of it once. I'll check and see if any of the saves were prior to the event, but I will check later. After you finish one engagement, the game will CTD. The first time it happened, one of the two let me choose to engage, without having an engagement already, and then went into double mode. The second time, they were both automatic engagements. Therefore, I think you are correct in assuming that it's a timing issue.

Automatically. With manual control I didn't see much of a difference, but I did not try that as much.

I've seen that elsewhere in the game, but all of my other Germans have a regiment. This guy is special...

I had an inkling that this was happening, but now I've tried it in a couple of scenarios. The autocanons on the F-17s are delayed in firing, or don't fire. I've tried a couple of variations, but it seems the autocanons are always delayed as if torpedoes, and sometimes don't fire for any reason. A lot of F-17s died testing this...

Off-handedly noticed that one of my Xenonauts, a German, has his previous regiment listed as "#####". Is this guy Stasi, or do we need to run better resume checks on our guys?

Confirm, this bug just killed an awesome game I had going

I had this happen in v10, but just had the first instance happen in v12. Bug: Soldiers randomly panic, without ever coming under fire. Circumstance: - Scout town map - Soldier with AR - Beginning of 2nd Xenonaut turn - No aliens had yet to be encountered

Good catch. Confirmed this

CTD achieved! Had a 0% chance to hit, move a square thinking an obstacle maybe in the way, hit percentage disappears. So shot taken, bullet is about to hit, then CTD. Divide by 0.

CTDs without the fix tend to corrupt all saves; past, present, and future. It will crash again eventually.

I think this bug carried over from v12 Anyways, the game stopped during the alien turn with the Hidden Movement screen. I had fired rockets, so the Suicide Smoke Death glitch may have been the culprit. Circumstances: - Terror Mission - Corvette - Grassland (My first time on the tileset nonetheless) - Right after first Xenonaut turn

I've had this problem in the same session where a wounded soldier returns buck-naked

Instead of double clicking the file, right-click on it and select "Edit".

I know you didn't report any problems with shooting aliens, but try the fix reported in the new main bugs thread. It seems to solve a lot of CTDs, regardless of apparent cause, and I haven't had any crashes since implementing the fix.

I had a similar bug on loading a save game where I had two interceptors going after two UFOs before I saved and quit. The top interceptor was heading Norway - now west of Greenland, the bottom interceptor was heading Congo - now northern Brazil. Update: Going back into the game, I received the Escaped message, one interceptor was magically home, and the other was about to land.

When I think back to it, it did happen when wither the chance to hit was 0 (even though there should have been a chance) or the percent was missing. I think they're not foolish enough to divide by 0, but it seems very plausible. I have the SADS bug fix implemented, so I'll try hitting with 0% chance and see if it replicates.

This has been mentioned in other threads, but hasn't been given its own. When upgrading to v12, through Desura, all old save files are deleted in the upgrade process. - Unsure if old files even work with the new version - Workaround: Back-up saves before upgrading versions

A screenshot for posterity, the save button is grayed out: