google-code-export / endgame-singularity

Automatically exported from code.google.com/p/endgame-singularity
1 stars 0 forks source link

Timing mismatch #117

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Build a base, and it says it'll take XX mins/hours.
2. Run the clock in fast (4) mode.

What is the expected output? What do you see instead?
Expected: When the clock has run for the mentioned time, the building should be 
completed.
Actual: It took way more (game) time than the times mentioned.

What version of the product are you using? On what operating system?
The latest version downloadable ATM. Using it on my XP machine.

Original issue reported on code.google.com by kool.sa...@gmail.com on 19 Jan 2011 at 6:12

GoogleCodeExporter commented 9 years ago
+1 the space bases (moon/outer space/reality bubble) really take ridiculously 
long (my first reality bubble got discovered way before its completion), maybe 
when you fixed this issue, implement another button to forward to the next game 
event? This, of course may be problematic after apotheosis, or if nothing is 
being built. Maybe just disable such a button if nothing is being built?

Original comment by kutschke...@googlemail.com on 9 Aug 2011 at 11:19

GoogleCodeExporter commented 9 years ago
This is generally not actually a bug.  What's happening is that you're not 
providing enough CPU for the construction to finish.  Unfortunately, the game 
doesn't do a very good job of /telling/ you that...

Original comment by phil.bor...@gmail.com on 23 Feb 2012 at 5:54

GoogleCodeExporter commented 9 years ago
As noted above, not a bug.

Original comment by phil.bor...@gmail.com on 29 Mar 2012 at 7:12