• Welcome to the Speedsolving.com, home of the web's largest puzzle community!
    You are currently viewing our forum as a guest which gives you limited access to join discussions and access our other features.

    Registration is fast, simple and absolutely free so please, join our community of 40,000+ people from around the world today!

    If you are already a member, simply login to hide this message and begin participating in the community!

Update on the Rubik's Cube Timer Site!

Seems you're motivated to work a lot on this timer, which is cool to see! Since you're looking for feedback, I thought I'd offer a few suggestions to make sure the timer is fair and reliable:
  • Scrambles: you should not be using random-move scrambles. They produce measurably biased results, and I would never use or recommend any timer that does this. (In the case of YoTimer, it also seems to be capable of generating impossible scrambles on Square-1.) Since you're already using `cubing.js`, you might find it easy to use it for scrambles as well:
  • Your code is using `Date.now()` to get timestamps, which means the time can jump around when the computer clock corrects itself. This can and has caused inaccurate timing results for timers like this. Fortunately, you can fix this by swapping out all those calls for `performance.now()`.
 
Seems you're motivated to work a lot on this timer, which is cool to see! Since you're looking for feedback, I thought I'd offer a few suggestions to make sure the timer is fair and reliable:
  • Scrambles: you should not be using random-move scrambles. They produce measurably biased results, and I would never use or recommend any timer that does this. (In the case of YoTimer, it also seems to be capable of generating impossible scrambles on Square-1.) Since you're already using `cubing.js`, you might find it easy to use it for scrambles as well:
  • Your code is using `Date.now()` to get timestamps, which means the time can jump around when the computer clock corrects itself. This can and has caused inaccurate timing results for timers like this. Fortunately, you can fix this by swapping out all those calls for `performance.now()`.
Wow. Are you a developer of twizzle? I didn't know you were here. Thanks a lot for the feedback .I'm still in the learning phase. I'll watch the videos on your Youtube channel. I'd like you to review the updated version again in the future.
 
It would be nice if you added a feature where you hold to start, but either tapping or holding the space bar stops because currently, the timer keeps going until you release again. Another good feature would be an option to view times in minutes, not just seconds.
There are already two different settings: hold space and press space. I don't understand what you mean exactly?
 
There are already two different settings: hold space and press space. I don't understand what you mean exactly?
When hold space is enabled, to stop the timer you must press and then release the spacebar to stop the timer, unlike on a stackmat, where you just have to touch it again. I would like it if you could have it more like a stackmat, where you hold to start, but the timer stops once you touch the space bar again, not when you push then release again.
 
When hold space is enabled, to stop the timer you must press and then release the spacebar to stop the timer, unlike on a stackmat, where you just have to touch it again. I would like it if you could have it more like a stackmat, where you hold to start, but the timer stops once you touch the space bar again, not when you push then release again.
Now I get what you mean. I'll fix that. Thanks for feedback.
 
Last Updates: Thanks to @Lucas Garron . We now get the scramble algorithms directly from cubing.js. So now we have the correct scramble algorithms. And I also fixed some bugs about starting and stopping the timer. I hope you like it.
 
I found a bug where your PB that is marked does not change when you delete that time so if you accidentally start and stop quickly your marked PB is wrong forever.
When you click on info it says there is no data but I think it still says it in the pb section. Thank you for your feedback. I will fix it as soon as possible.
 
I found a bug where your PB that is marked does not change when you delete that time so if you accidentally start and stop quickly your marked PB is wrong forever.
Problem solved :) The problem will not occur again after resetting the times or switching to a new season.
 
New Update: When you click on the time, you can add a + penalty to that time, mark it as DNF, write a comment about that time, retry the scramble algorithm of that time and copy it with its details. If you encounter an error while using it, I would be glad if you could give me feedback.

Ekran görüntüsü 2024-12-05 181355.png
 
Back
Top