random anomalies .. not so much

from GalCiv3 Forums

i built my own map with the map editor i placed a few anomalies but left the rest to be placed randomly (i believe there is a checkbox for allow random anomalies)

the problem is that the anomalies aren't random... i get the same "random" anomalies in the same spot every time i start a new game.

i think the seed must be generated when i started building the map and is now locked in can we have a way to randomize the "random" seed?

 

 

8,001 views 5 replies
Reply #1 from GalCiv3 Forums Top

Thanks for report.  We'll look into it.

 

Reply #2 from GalCiv3 Forums Top

Did you try to exit the game before starting a new game?

I believe there was an report earlier that starting a new game without exiting GC3 (from the game go to the main menu and start a new game using "quick start") would yield the same map (I guess use the same seed). I do not know if this has been fixed.

Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from GalCiv3 Forums Top

Quoting pshaw, reply 1

Thanks for report.  We'll look into it.

 
End of pshaw's quote

We'll have a fix for this in 1.81

Reply #4 from GalCiv3 Forums Top

Quoting pshaw, reply 3

Did you try to exit the game before starting a new game?
End of pshaw's quote

yes ive started multiple new games sometimes over the course of weeks and every time the same "random" anamolies were in the same place

Quoting pshaw, reply 3

We'll have a fix for this in 1.81
End of pshaw's quote

sweet thanx i havent had a chance to play recently but now i want to again 

Reply #5 from GalCiv3 Forums Top

Quoting androshalforc, reply 4


Quoting pshaw,
reply 3

Did you try to exit the game before starting a new game?



yes ive started multiple new games sometimes over the course of weeks and every time the same "random" anamolies were in the same place


Quoting pshaw,
reply 3

We'll have a fix for this in 1.81



sweet thanx i havent had a chance to play recently but now i want to again 

End of androshalforc's quote

We released the patch that includes this fix yesterday.