Planetary Invasion killing my game

I apologize if this has already been reported. I've searched the forum and attempted to find if this has already been posted on here.

When I attempt to invade a planet, the game brings up the invasion screen with the forces on either side. Then the screen goes black and the only thing I can see is a small area around my cursor. When I move the cursor, the window of what I can see comes along with it. If I find and click the button on the invasion screen, it seems to process normally, but once the battle is over the screen goes black and nothing happens.

The game never really crashes though. I eventually have to window out and kill it with the task manager.

This problem happens ONLY at the planet invasion screen. (weird side note; I had 2 of my planets invaded without this occuring. It's only when I invade an AI planet and am going to win).

System Specs:
Windows XP
Intel 2.53ghz
Radeon 9800 Pro
1 gig RAM

Downloaded the most current version of the ATI drivers a few days ago (Feb 17th 2006 version).
6,996 views 9 replies
Reply #1 Top
I have a similar experience playing the game on my laptop. I was 3/4 of the way through a game where I was winning, then for some reason trying to invade a planet resulted in a CTD.
I sent an email to stardock with the exception log file and started a new game.

Similar situation, towards the endgame now and am trying to mop up some minor races and the bug has resurfaced.
Its strange as I've invaded people earlier in the game with no problems, and other civs can invade me with no issues.

Bit frustrating that it only manifests itself during the later stages of a game.
Does it happen on your PC from the very start?
Reply #2 Top
Yeah I am winning a game but I CTD whenever I invade now...
Reply #3 Top
I'm having the same problem. I'm getting ready to invade one of my larger enemies, so I've built up quite a fleet of combat transports and big custom attack ships. Every time I direct my combat transports to invade a planet, I CTD. I don't even get to the attack screen.

Windows XP
NVidia Geforce 6800 GT
AMD Athlon 3200+
2GB RAM
Reply #4 Top
OK so a few people seem to get this crashing issue. In order to help determine what is causing the problem, I suggest that you install the stardock smart exception utility and email the exception log to the support team at stardock when the invasion crash occurs.

I guess the more information they have, the easier it will be to pinpoint the cause.

Luckily I'd saved the game just before my invasion so I just reloaded it, attempted the invasion, crashed, then sent that exception log to support.

Other than that, I don't know what to suggest. The fact that it only occurs late game (for me..) makes me think that it could be to do with a certain tech being researched, or a super project that affects invasion bonuses being constructed e.g. Tir Quan training or No Mercy Invasion Centre.

But I'm really clutching at straws here, it could be anything in a piece of software this complex. Stardock will no doubt be much more able to find the cause. I will post here if I get a message from tech support
Reply #5 Top
Jimmy, you're a genius! I had *just* completed No Mercy Invastion Centre before I started trying to invade. Since I couldn't cancel the superproject, I tried destroying the colony it was built on, and Voila, invasion works again!
Reply #6 Top
Ah.. my game is also crashing when invading a planet.. and I had just buildt the No Mercy Invasion centre too..
Reply #7 Top
I think that we've fixed this one for the next update.
Reply #8 Top
Good to hear its fixed in the next update. Don't know if I can contain my invasion desires until the next patch though..

For now I will sell off the offending colony to my drengin allies. Nice to have pinpointed the problem so quickly anyway.
Reply #9 Top
Got a reply from tech support saying to try updating my graphics card drivers and see if the problem persists. I updated my laptop ATI drivers about 3 weeks ago I believe so thought I had the newest version. Maybe I don't..

Got to go to work now unfortunately, but will try looking for updated drivers when I get back.

Anyone else had this problem, only to find updating their drivers solved it?