![]() This begged the question if Winmine really did use the system clock as a reference. However, when he compared the system clock to a stopwatch there was no difference. Joe Nuss (USA) also checked and found the clock showed 58 after 60, 97 after 100 and 223 after 230 real seconds. He warned, "If the speed of the counter depends on PC configuration than all records are not made under the same circumstances". Georgi then let a minesweeper game run on his computer for 500 real seconds and found the game clock reached only 480. 190 seconds instead of 201 means the game is about 5% slower than the clock. I've ran the game for 5 minutes and the difference, if any, was less than half a second. otherwise my times may be invalid." This was a surprise, and Marc replied, "There is no discernible difference between my game and my clock. I think we shall all have to hope that whatever timing mechanism is used, it is consistently slow across computers. So I don't think that it is just the video. There was also about a 10-second lag over 3 mintues when I checked it against the system clock. After 190 seconds were showing on the timer my watch said it was about 201. The following day, David Barry (Australia) noted, "I just checked the timer (in the actual game) against my stopwatch. If there's a discrepancy between the actual time passed and the time displayed by the timer in a recorded movie, it's because the movie doesn't play at the same speed at which it was recorded." It runs perfectly synchronous with the system timer. However, when Matt watched an 82 second Camtasia video he found it took 85 seconds! Marc Schouten (Netherlands) wrote "there's nothing wrong with the timer in Minesweeper. Matt McGinley (USA) replied this was unlikely because the Timer Jump bug suggested minesweeper used the system clock. He found that "when watching some downloaded videos that the time counter of Minesweeper does not count seconds" and that on his computer "the counter approximately shows 96 for the real 100 seconds". Timer Lag was discovered again by Georgi Kermekchiev (Bulgaria), who posted about it in the Guestbook on. Gregory Lewis (USA), the admin for the club, replied he once had the same problem and it was caused by a low CMOS battery. On he said a slow clock had helped him set new minesweeper records, before he realised the mistake. ![]() The first known person to discover Timer Lag was user "Swannaplay" in the Minesweeper Yahoo! Club. This is a bug of all Windows Minesweeper versions before the release of Windows Vista. Timer Lag is when the minesweeper clock counts slower than real time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |