Nir1213
Member
maybe because the site is simple, and CStimer is a bit complex, but Cstimer is pretty cool once you get to know the basics.Why don't you use CStimer?
maybe because the site is simple, and CStimer is a bit complex, but Cstimer is pretty cool once you get to know the basics.Why don't you use CStimer?
timer.cubing.net has a nice aesthetic and you can sync solves, which is the main downfall of cs timerWhy don't you use CStimer?
Oh, I have seen some of your PB scrambles, one had a one move xcross with free pair. I think you need to switch for me to take your results seriously.Been practising a lot and I get lucky sometimes. could be something to do with the fact that timer.cubing.net scrambles tend to give free pairs
It is a cubing timer site. How different can they really be?Oh, I have seen some of your PB scrambles, one had a one move xcross with free pair. I think you need to switch for me to take your results seriously.
I think the difference between random state and whatever the one you use has is pretty big. qqtimer.net has a pretty simple interface and reasonable scrambles.It is a cubing timer site. How different can they really be?
After much peer pressure I have switched back to cstimerI think the difference between random state and whatever the one you use has is pretty big. qqtimer.net has a pretty simple interface and reasonable scrambles.
lol I agree, I avg around 19 after 130 solvesI'm practising cstimer virtual cube. It's weirdly fun, like 4x4 OH
lol I agree, I avg around 19 after 130 solves
You already did, on the discord (I'm Luminescence2081/J8Cubes)Best of luck! I’d be happy to help if needed.
@Lucas Garron Have you heard about the timer.cubing.net scrambles being easier than others from anyone/where else?
timer.cubing.net is actually every careful to produce the best possible random-state scrambles where other timers (e.g. qqtimer, csTimer) currently do not. In fact, you might notice that the only currently supported events are ones where proper random-state scrambles are possible.
OK cool, thanks! Maybe the browser's built in thing needs updatingI should probably clarify: timer.cubing.net, qqTimer, and csTimer use the same code for 3x3x3, which I adapted from Chen Shuang's Java code several years back. (Code for other puzzles is similarly shared.)
The only significant difference is that timer.cubing.net is using the browser's built-in high quality random number generation (crypto.getRandomValues() instead of Math.random()).
OK cool, thanks! Maybe the browser's built in thing needs updating
That's true. I just seemed to be getting a ton of free pairs and xcrosses etcHmm, the browser API is almost certainly not an issue. Browsers know they need to be super careful with it, and it would be a very serious bug if the data was distinguishable from true randomness.
And if there was an issue, it's also unlikely that the issue would result in noticeably easier scrambles (for the same reason that qqTimer and csTimer are fine in practice).
I took a quick look at some basic scramble distributions (piece orientations, piece permutations), and they looked pretty normal. But I take scrambles very seriously, so I'll try to take a closer look.
Here's a JSON file of 100,000 scrambles if anyone else would like to run randomness tests on it: