Edmund
Veteran
I'm pretty sure he uses the WTF method.
Michael Gottlieb computer 6x6x6 WR: 1:38.34
- Thread starter Robert-Y
- Start date
So it seems that hi-games timer is incorrect when computer run slowly. That doesn't have sense at all. I remember that time ago, when I used a slower computer, when the cube turned slow the timer was running correctly. I see it a bit strange. But still you are really really fast 
Robert-Y
Legend
I'm really confused about the problem, the replay looks real to me, it looks like it was just a fast solve...
@qqwref: Are you really sure you're not capable of doing 1:3x.yz?
@qqwref: Are you really sure you're not capable of doing 1:3x.yz?
mazei
Veteran
Well so far 2 people have timed the replay and said its 1:3x.yz.
Robert-Y
Legend
I timed it myself and got 1:38.xy
qqwref
Legend
- Joined
- Dec 18, 2007
- Messages
- 7,834
- Location
- a <script> tag near you
- WCA ID
- 2006GOTT01
- YouTube
- Visit Channel
Yeah, I'm pretty sure. I had 1:57 before and that's really hard for me. As I said, the 1:38 replay times at like 2:05 on my stopwatch, and it took about that long on the solve itself too.
esquimalt1
Regular
whatever stopwatch you're using is running fast then michael. I timed it on my stopwatch and got 1:38.30. everything was perfect the whole time.
masterofthebass
Premium Member
YOU GUYS CAN'T COMPREHEND THAT COMPUTERS ARE DIFFERENT.
The java on qq's computer alone, is running slow, therefore creating a time that is faster than he actually did it in. It is also the reason when he plays back the replay on HIS computer, it plays back slower. For anyone else, it will be 'normal' speed, which is not the actual speed he did it at.
The java on qq's computer alone, is running slow, therefore creating a time that is faster than he actually did it in. It is also the reason when he plays back the replay on HIS computer, it plays back slower. For anyone else, it will be 'normal' speed, which is not the actual speed he did it at.
Edmund
Veteran
Wow, I'm slow. Thanks for clearing that up.
Robert-Y
Legend
Yeah thanks for that Dan, I am also slow.
I think that people that doesn't program will hardly understand... I think (although it is totally different) that this example may help to understand:
Imagine that you will do a video solving the cube. You record at 20 fps and get a 12 seconds time. Now you play the video at that speed and the solve is 12 seconds. But if you play it at 30 fps (a normal speed for videos), people will see you solving it in 8 seconds (a lot faster).
Well, Michael "recorded" his solve at a "slower" than normal speed (and even the clock ran slower) because perhaps of the computer running slowly, but when you see the replay at a "normal" speed it seems that the time was lower.
However, the strange point is that clock goes at real speed when I play, even if the game run slow, and not only in this game (and even in programs I do)... that's why I want to play games that has cronometers/countdowns on fast computers. I also remember that one day I got a lot of freeze in a solve, but the clock ran correctly anyway.
Imagine that you will do a video solving the cube. You record at 20 fps and get a 12 seconds time. Now you play the video at that speed and the solve is 12 seconds. But if you play it at 30 fps (a normal speed for videos), people will see you solving it in 8 seconds (a lot faster).
Well, Michael "recorded" his solve at a "slower" than normal speed (and even the clock ran slower) because perhaps of the computer running slowly, but when you see the replay at a "normal" speed it seems that the time was lower.
However, the strange point is that clock goes at real speed when I play, even if the game run slow, and not only in this game (and even in programs I do)... that's why I want to play games that has cronometers/countdowns on fast computers. I also remember that one day I got a lot of freeze in a solve, but the clock ran correctly anyway.
