• Welcome to SpeedSolving.com — the world’s largest puzzle community!

    You’re currently browsing as a guest, which means you have limited access to discussions, resources, member profiles, and community features.

    Join 50,000+ cubers and puzzle enthusiasts from around the world to ask questions, share solves, improve faster, and be part of the community.

    Registration is free, fast, and easy — create your account today.

    Already a member? Log in here to hide this message and start participating.

Random Cubing Discussion

YzWq2.jpg


Hackmat :3

Kir that is the greatest thing ever. I thought about doing something to my timer along these lines but wasnt sure how to go about doing it and never bothered to look it up.
 
There was a Megaminx solve I did a while back. I swear I started the timer like normal, and then proceeded with the solve. It felt slow and sloppy, and yet when I stopped the timer, it said 57.xx. I knew it wasn't fast during the solve, but it was sub-1 according to the timer. So I thought that the timer lagged and didn't count the solve as a PB. Does qqtimer have problems like these or does felt-slow-but was-actually-not solves a lot more common? whauk had a sub-10 solve recently but he claimed that it felt super slow.

I had a 16.xx one time and it felt like a 25.xx on qqtimer.
 
I've been trying to do some walkthrough solves, and it looks like a lot of cases are missing? Or maybe I just don't know how to interpret them. Like, in CO, there are no cases where the edge is in the U layer.

Or just redifine Step1: Build a layer(D) and ensure at least one F2L edge already is somewhere in the E-layer, I think this cuts down the CO cases by 50%, and if there are multiple edges you may even choose the best.
 
Back
Top