Toaster

I just ran into this as well, definitly tied to an alien base being present, it only ever starts happening shortly before a base is discovered.

Saves should be in your documents folder, in a folder called "Xenonauts"

I've gotten this too. If I load a game with a terror site available, then I send a chinook, and when it arrives at the site nothing happens and the mission doesn't initiate.

I've noticed the crash only happens with firearms. If I use an explosive weapon(rockets, grenades) that have a 0% chance to hit, or a missing % chance, then everything still works fine.

I thought this was fixed for this build but once again I get this notice at the end of the month, even though, after receiving the new funding money, I should have more than enough to pay everything. I can only assume it's still deducting your bills before adding the new funding money.

Don't think this has been posted yet, haven't seen it anyways. Had a crashed scout UFO, a Caesan is inside the room where the power core is, 2-3 squares away from the door, I have a soldier sitting on the square just beside the door, on the outside. The door is closed. On the AI's turn, the Caesan shoots 2 shots *through* the closed door and kills my soldier.

I'm getting this too. I implemented the fix mentioned here: http://www.goldhawkinteractive.com/forums/showthread.php/2238-V12-Error-in-weapons_gc.xml-file Then started a brand new game. On my first ground mission, on the first turn an AI friendly soldier fires on an alien out of my site site but doesn't hit it. On the second turn nobody fires. On the third turn the alien comes into view. My % chance of hitting is listed as 0% for both sniper rifle and m16. I take the shot anyways with the sniper, he hits but doesn't kill, alien is surpressed(with the surpressed symbol over his head, and he crouches). I take a second shot with the m16, it hits and game CTDs.

After transfering any soldiers or vehicles from one base to another, every save made after that point is corrupted and causes a CTD on load. I'm not *positive* it's the transfer that caused it, but it's the only significant event I can think of that occured between the working saves and the corrupt ones.