Existing custom race not appearing with Beta 2A

First time I tried a game under beta2A, my custom race had been a selected opponent in an earlier game, and I deselected them when starting my first game under 2A. Now, starting my second game under 2A, even though the .customrace file for them still exists, they are not displaying as a selectable race. Do I need to recreate them for the new beta build? An unselected custom race that previously existed was displaying properly.
3,759 views 3 replies
Reply #1 Top
I've personally made it a general rule to delete my custom race file and other bits when updating to a newer beta build. Just to stay on the safe side of things.
Reply #2 Top
Yeah, probably should have done that. I always delete my old saved games. What I didn't understand is why a custom race not used as an opponent displays, but one that was previously an opponent and then deselected disappeared for the next game, even though the file is still there. I tried sending both files to the recycle bin and then restoring them, but it didn't change how the game currently sees them.
Reply #3 Top
Find your prefs.ini file from c:/program files/stardock/totalgaming/galciv2/darkavatar
Rename if to prefs_old.ini.
Then run the game.

This will reset your settings and may eliminate whatever is preventing your custom race from showing up.

If your custom race does show up, please email your prefs_old.ini file to [email protected] so we can look into why your race didn't show up.  Please provide a link back to this forum thread in your email message.

After emailing us, or if that does not fix the problem, you may delete the prefs_old.ini file.

Novaburst does have a good point.  It's generally a good idea to delete your old custom race and saved game files when updating to a new version.  Old data that may have been changed in the new version may get saved into those files, so problems that were fixed in the update may persist.

Thanks.