View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0000403 | AI War 1 / Classic | Bug - Other | Oct 11, 2010 12:05 am | Oct 19, 2010 7:21 pm | |
| Reporter | Fleet | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.706 | ||||
| Summary | 0000403: Game is still running fast | ||||
| Description | Kknowledge and game clock are still ticking fast as of 3.706. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | |||||
|
|
3.706 or 3.707? |
|
|
This would have been 3.707, sorry about that. Clock time actually seems accurate in my solo game, but it was most certainly still ticking fast in the one where Tss was hosting, and I think I checked the =/- speed modifier. |
|
|
Hmm, I'm playing multiplayer right now and am not seeing it... |
|
|
Ah well, thanks for taking a look at it. I'll post if I see it again. |
|
|
I guess I can confirm this in 3.707. Running AI War in a window with the system clock up right beside it, I get 63 seconds pass on the AI war clock for 60 passing on the windows system clock. This is on High Performance. On Extremely Low performance I see 73 seconds in AI war pass for 60 seconds system time. On Insane Performance I see 60 (maybe 60.5?) seconds AI war time pass for 60 seconds system time. These are all solo games. I restarted AI war between each test and generated a new game with the different performance settings, I did not adjust the game in progress through the stats screen. |
|
|
I got the extra 3 seconds too! The original ticking i reported was faster than this, and I almost decided not to report the solo increase of 63 game seconds to 60 wall clock seconds, but I'm glad you see the same speedup. |
|
|
Okay, thanks guys -- that's a lot easier to deal with. |
|
|
Are you guys still seeing this in 3.712? And if you will, please check out the new game time percentage timer in the Stats window. It shows what percentage of realtime your game is running at. Generally +- 10% is normal, so the 63 seconds for 60 seconds does not concern me. However, if you're seeing wildly higher number (more than 66 seconds for a minute), that is concerning). |
|
|
Pretty sure this is resolved, marking as such. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Oct 11, 2010 12:05 am | Fleet | New Issue | |
| Oct 11, 2010 12:29 am | Chris_McElligottPark | Note Added: 0000605 | |
| Oct 11, 2010 12:33 am | Fleet | Note Added: 0000608 | |
| Oct 11, 2010 12:34 am | Chris_McElligottPark | Note Added: 0000610 | |
| Oct 11, 2010 12:34 am | Fleet | Note Edited: 0000608 | |
| Oct 11, 2010 12:35 am | Fleet | Note Added: 0000611 | |
| Oct 11, 2010 12:45 am | Dazio | Note Added: 0000620 | |
| Oct 11, 2010 12:45 am | Dazio | Note Edited: 0000620 | |
| Oct 11, 2010 12:49 am | Fleet | Note Added: 0000622 | |
| Oct 11, 2010 12:50 am | Chris_McElligottPark | Note Added: 0000623 | |
| Oct 11, 2010 12:50 am | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Oct 11, 2010 12:50 am | Chris_McElligottPark | Status | new => confirmed |
| Oct 14, 2010 12:23 am | Chris_McElligottPark | Note Added: 0000801 | |
| Oct 14, 2010 12:23 am | Chris_McElligottPark | Status | confirmed => feedback |
| Oct 19, 2010 7:21 pm | Chris_McElligottPark | Note Added: 0001373 | |
| Oct 19, 2010 7:21 pm | Chris_McElligottPark | Status | feedback => resolved |
| Oct 19, 2010 7:21 pm | Chris_McElligottPark | Resolution | open => fixed |
