Crash With Too Many Races

GalCiv3 is advertised as handling 100 Races.  It does, but it will not handle 101.  It crashes instantly when the total races reaches 101.  Everyone needs to understand that 100 races means you and 99 opponents.  When the number of opponents reaches 100, the total races reaches 101, and the game crashes.

I found this in version 1.02 when I was thinking that 100 meant 100 opponents.  I had manually added opponents to get to 99 then added one more.  The game instantly crashed.

It is easier in 1.03 with the Add Random Opponents "slider" at the bottom of the available opponents list.  Since this "slider", like other "sliders" in GC3, can be easily and quickly adjusted with the mouse wheel, it is possible to quickly increase the number of random opponents until 100 is reached.  When this happens, the game instantly crashes.

If some opponents are manually added, the game will crash when the number of random opponents is increased to bring the total opponents to 100.

Even worse, if the mouse wheel is moved in the other direction, the number will quickly decrease to 0, then go past 0 to some value.  It briefly shows 99 before the game crashes.

If clicking on the arrows is used instead of the mouse wheel to change the numbers, the same thing happens.

3,059 views 5 replies
Reply #1 Top

Hmm and I thought the top number should be 128 races. You should file a ticket over this. I think you're the first one who bothered to make so many races to create 100 opponents :) My congratulations!

Reply #2 Top

Quoting Bloodlust1983, reply 1

Hmm and I thought the top number should be 128 races. You should file a ticket over this. I think you're the first one who bothered to make so many races to create 100 opponents :) My congratulations!
End of Bloodlust1983's quote

My long standing suspicion had been that the 128 number includes minors.  Haven't bothered to find out yet as I still have a 70+ faction game to finish off. :)

Reply #3 Top

I don't want to take credit for creating so many races.  I only made 4 of the 166 I have available.  These races include:

    8 that came with the game
    4 that I made as factions
    7 that are from mods that I found in various posts in the forums and then downloaded.
147 that are faction files that I found in various posts in the forums and then downloaded.

So, I am a prolific downloader of the work of others rather than a prolific maker of races.

Also, I do have a ticket in on this.

Reply #4 Top

Old-Spider,

Is it possible that the 101st race is defective and causing the crash?  have you tried with a different 101st race?  (aka the core from the faction contest caused my game to crash if used I had to copy and modify it to get it to work.)

Reply #5 Top

Quoting Seilore, reply 4

Old-Spider,

Is it possible that the 101st race is defective and causing the crash?  have you tried with a different 101st race?  (aka the core from the faction contest caused my game to crash if used I had to copy and modify it to get it to work.)
End of Seilore's quote

My first thought is "no" since it occurs while adding only random races.  There is no way of knowing which races are being added at that time.  It may be that none is added until the map generation starts and an existing race is picked to fill the random slot.  If this is the case, then it crashes because of the number of opponents rather than the actual race that is the 100th opponent.

To be sure, I started a new game with today's update and added 95 opponents from the various races I have downloaded.  I then added races that come with the game one at a time.  When I added the Thalans as the 100th opponent, the game crashed.  It seems to based on the number of races rather than the particular race that is the 100th opponent.