Patch 5.2 spending bug?

from GalCiv3 Forums

Hey, just downloaded the new patch, startet a new game as Terrans and somehow my spending doesn't work anymore.

No matter where I put my sliders the corresponding numbers stay the same? only happens in the overall govern window.

I don't remember this happening before.

Happening to anyone else?

 

EDIT: Now works, but only after hitting the reset button in the govern window. very very strange.

4,771 views 3 replies
Reply #1 from GalCiv3 Forums Top

That is indeed very strange Nagini6. I'm glad to hear you were able to quickly resolve it though.

If you run into that issue again, or any other issues with Patch 2, please see the article below for some general troubleshooting tips and instructions on placing a ticket, if the recommendations do not help:

https://esupport.stardock.com/index.php?/default_import/Knowledgebase/Article/View/496/161/general-galactic-civilizations-iii-troubleshooting

Thanks!

 

Reply #2 from GalCiv3 Forums Top

I havent been able to repro this. Is anyone else seeing it?

ObjectDock - Access shortcuts and frequently used applications from an animated dock.
Reply #3 from GalCiv3 Forums Top

Derek,

i have not seen i recently, but (if my memory serves me well) i have seen it at least twice in previous beta(s). (From memory:) it happened for me when my treasury was exactly zero. I could move the production wheel slider, but this had no influence on changing the actual production/research/wealth values. I can't remember if the wheel itself was dimmed or not.

My conclusion then was that the update of the actual values was inhibited by the condition (treasury <= 0) while the disabling of the production wheel (user) interface was inhibited by the condition (treasure < 0), making the function of the production wheel (at treasury == 0) null and void. Because in the turn thereafter i would regain functional control if the treasure became positive or the production wheel would go to its locked state (at 100% wealth) if the treasure became negative.

I had actually forgotten that i ran into this until i read this post. It is also quite possible that the observed behaviour by me and the problem as posted here are completely different, but i thought to mention it anyway in case this would help you guys out.