masterofthebass
Premium Member
two words:
****ing nuts...
****ing nuts...
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
the WR is 0.83 by Patrick Jamson http://www.worldcubeassociation.org...gionId=&years=&show=100+Persons&single=Single
Source: http://www.worldcubeassociation.org/regulations/For Magic (and similar puzzles) the puzzle must be flat on the surface. The maximum elevation of the bottom side of the puzzle at the end of a solve is two tiles higher than flat.
What new rules are you talking about? Could you tell us where you heard this?
Also, could you stop typing "..." so much? It just makes your posts harder to read.
What new rules are you talking about? Could you tell us where you heard this?
Also, could you stop typing "..." so much? It just makes your posts harder to read.
sorry for the periods. it is a habit of mine.
yes, new rules says TWO TILES higher than flat. and by a calculation with the surface and angle, it is close to 25 degree. or use other magic that folded once so it stack two tiles then measure it.
people here are very strict. they question a little about something on anything. and they knows it. so they apply some strict.
if my PERIODS are being questioned??? what more if it is a WR solve.
it is just my two cents.
peace. hehehhehehe...![]()
I do agree, but magic is one the few events where it is obvious to see a DNF or +2 pretty much every time. I guess if the competitor doesn't care, it doesn't matter how long the judge takes to look at each solve. But I do agree with Stefan, that was some overkill.I actually think that was the best judging of an magic event i have ever seen. Sure it could be excessive, but when someone is getting times where it is close to WR territory, i think it needs to be done right. The last thing we want is for there to be questions around a WR's legitimacy.
Exactly. I went through and looked at it frame by frame, and it looks like he drops it out of the air, which is nice so we know he wasn't solving when he stopped the timer. He had the puzzle solved and his hands within an inch of the time at around 0.68 for each solve (which I'm guessing is common for most fast magic solvers).For me, though, the biggest concern with magic is whether the person is stopping the timer separately from touching the puzzle.
I didn't calculate but I'd say it's about 10 degrees. Though I'd never state that as the rule (like you did) cause rephrasing just introduces error (like you did, significantly).yes, new rules says TWO TILES higher than flat. and by a calculation with the surface and angle, it is close to 25 degree.
There is. And not just at the end. Check the frames at the start of the solve, you should see the same delay there.Perhaps there is a delay in the display time
I do agree, but magic is one the few events where it is obvious to see a DNF or +2 pretty much every time. I guess if the competitor doesn't care, it doesn't matter how long the judge takes to look at each solve. But I do agree with Stefan, that was some overkill.I actually think that was the best judging of an magic event i have ever seen. Sure it could be excessive, but when someone is getting times where it is close to WR territory, i think it needs to be done right. The last thing we want is for there to be questions around a WR's legitimacy.
Exactly. I went through and looked at it frame by frame, and it looks like he drops it out of the air, which is nice so we know he wasn't solving when he stopped the timer. He had the puzzle solved and his hands within an inch of the time at around 0.68 for each solve (which I'm guessing is common for most fast magic solvers).For me, though, the biggest concern with magic is whether the person is stopping the timer separately from touching the puzzle.
Here is one frame at 0.68 seconds with the puzzle solved and his hands very close to on the timer:
![]()
One frame later at 0.81:
![]()
And then 4 frames after that at 0.90 and his hands are well off the timer (after stopping it):
![]()
Amazingly quick, and kind of interesting that it took that long for the timer to stop with his hands so close to the timer. Perhaps there is a delay in the display time from when the timer is actually stopped.