1 |
So basically the problem here is that if you sit with a watch and check the real time it takes to build an object, you get a small difference compared to the expected (based on tooltips) time.
|
1 |
So basically the problem here is that if you sit with a watch and check the real time it takes to build an object, you get a small difference compared to the expected (based on tooltips) time.
|
2 |
\n
|
2 |
\n
|
3 |
I dont see anything there that can be fixed without breaking too many other things. The choice is to either have ugly real-time numbers, or to have ugly numbers in the code.
|
3 |
I dont see anything there that can be fixed without breaking too many other things. The choice is to either have ugly real-time numbers, or to have ugly numbers in the code.
|
4 |
\n
|
4 |
\n
|
5 |
It might be a good idea to fix the ETA widget so that it displays the adjusted real time, but i highly doubt it would matter - in a real game the ETA timer is always very unstable and the small error created by this engine problem is absolutely irrelevant.
|
5 |
It might be a good idea to fix the ETA widget so that it displays the adjusted real time, but i highly doubt it would matter - in a real game the ETA timer is always very unstable and the small error created by this engine problem is absolutely irrelevant.
|
|
|
6 |
I bet if someone ninja-changed it to work that way, no one would even notice it for years, possibly ever.
|