• 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.
Status
Not open for further replies.
I just finished learning COLL and I will spend around a week getting good at the algs/recognition, but which algorithm set should I learn next? (I am getting CN now, but on white/yellow I average around 11.7 globally) And I if I learn WV I can only use COLL when I do some kind of VHLS, right?

Assuming you use CFOP, learn some of the easier WV cases but not all of them. COLL isn't as good as OCLL/OLL->PLL for TH in many cases anyway
 
I just finished learning COLL and I will spend around a week getting good at the algs/recognition, but which algorithm set should I learn next? (I am getting CN now, but on white/yellow I average around 11.7 globally) And I if I learn WV I can only use COLL when I do some kind of VHLS, right?
I don't think you would always need COLL and force it. It's more of if you get all the edges oriented already, better to do OLL and PLL than VHLS - COLL - EPLL, plus all of VHLS is a bad thing to learn.
 
Assuming you use CFOP, learn some of the easier WV cases but not all of them. COLL isn't as good as OCLL/OLL->PLL for TH in many cases anyway
Yes, I don‘t use COLL for the sune/anti-sune cases, for example.

I don't think you would always need COLL and force it. It's more of if you get all the edges oriented already, better to do OLL and PLL than VHLS - COLL - EPLL, plus all of VHLS is a bad thing to learn.
I was just wondering, if WV would help, even though I know COLL...anyway, thanks for the reply!
 
I was just wondering, if WV would help, even though I know COLL...anyway, thanks for the reply!

Learn the easy cases if you want, the algset is really small and half of it is R U' R' into an OLL with some cancellations. But keep in mind that WV and COLL are not that compatible, and don't try to pair the last pair and always use WV, just use it to force OLL skip when the case is right in front of you.
 
My ao100 is 55.25 on 3x3. Is this considered sub50?
As per xyzzy, no, a 55.25 average of 100 is not under 50 seconds.

However, if you meant you, the answer is still probably no.

Often when people do long averages, like ao1k or ao10k, the time lags significantly behind the cuber. But for averages like an ao100, those are still short enough to be lucky and they aren't super indicative of what your speed is.
 
Is there an alg set where you orient the corners of both layers while preserving EO and/or the E layer?
The closest thing I know is TOLS, which solves the orientation of the DFR corner while orienting the top layer, but that also includes edges not oriented cases.
Does anyone know of a way to generate orientation algorithms that don't care about permutation? Cube explorer and Alg explorer solve permutation and orientation, but often these algs are not optimal.
 
Does anyone know of a way to generate orientation algorithms that don't care about permutation? Cube explorer and Alg explorer solve permutation and orientation, but often these algs are not optimal.

In kubesolver it's quite straightforward to generate algorithms for solving and/or orienting edges and/or corners.
 
Are there any sizeable benefits to learning some F2L algorithm cases after using intuitive for 2 years? The concept of algorithmic F2L confused me at first but I would like to know if there are any algorithms I should learn for certain cases that are "Bad"? (My F2L split is around 4-5.5 not including cross)
 
Well, I'm working on a belt method, and after you solve the E layer and EO, you do CO. And it doesn't really matter where on the cube the oriented corners end up, since the next step is to solve the D layer.
Every new cuber thinks of a belt method thinking they have an original idea. The reason no one uses it is because it's bad. Please don't waste your time developing it.
 
Well, I'm working on a belt method, and after you solve the E layer and EO, you do CO. And it doesn't really matter where on the cube the oriented corners end up, since the next step is to solve the D layer.
A belt method would probably have bad recog and movecount. With some optimizations, it could possibly be a decent method, like SSC, but generally, a belt method is not worth your time.

Edit: ninja'd
 
I noticed that Kirjava's OLLCP hax page on the wiki is down. I was thinking of learning it, so does anyone have a copy of table of all his cases?
 
Status
Not open for further replies.
Back
Top