Can't settle new colonies

I realize this is Beta but this bug is really not nice! Whenever my colony ships reaches a planet it brings up the colony name and I leave it like it is and press enter. Then the game crashes and a message comes up about microsoft error reporting and asks me if I want to report this error becuase the galciv2.exe has been terminated. Has anyone else had this problem? I would think that the stuff in the beta would at least work enough to show the basics of the game. And colonizing is needed in the game! It's possible it could be my computer. I'm running it on a notebook computer. But my specs should allow it to run.

3 Ghz intel p4
1 gig ram
128mb GeForce FX video card
WinXP Service pack 2.
Well I downloaded the latest graphic drivers for my custom built HP notebook from the HP website. That's what nvidia said to do, and if I colonize a planet on the first turn the game doesn't crash. If I colonize it after the first turn the game crashes with that stupid error reporting message. I realy don't want to buy a new desktop computer to play this game because the drivers for the notebook graphics suck. Will someone please help the idiot. (That's me.) Thanks.
6,128 views 6 replies
Reply #1 Top
There have been a lot of colonization crashes reported on the Beta 1 level, some related to drivers, some related to GC2 code. The GC2 code fixes have been promised in Beta 2.

The crashes also seem to be related to the method of sending colony ships to colonize a planet. I have found that I can avoid the current set of colonization crashes related to GC2 code by sending colony ships to a tile next to a planet (on autopilot), then moving the ship onto the planet with the number pad keys.
Reply #2 Top
A few minutes ago I was trying to mess around and see if I could keep it from crashing. My survey ship reached an anomaly the same turn my colony ship reached a planet. The colony name window came up first and I clicked on ok lhen it went to the found anomaly window and after I clicked to close that window it did not crash. I'm not sure what that proves though?
Reply #3 Top

It may have been unrelated.  But I'm fairly certain that you shouldn't have problems colonizing when the second beta comes out.

Reply #4 Top
Glad to hear it, thanks.
It is very frustrating reading what others are doing.

Not sure if I will be able to download the next build. It may be too big for my dial up connection.
Reply #5 Top
It may be too big for my dial up connection.


Are you in a location like mine? My DSL connection is cheaper now than my old dial up was. 'Course, I had two phone lines to support the dial-up without interfering with other phone calls, but it still comes out cheaper now than one line and a dial-up ISP.
Reply #6 Top

Well, Stardock Central supports resume downloading so you could start it at night before you go to bed and even if something goes wrong, you'll be able to pick up later on.