Status
Not open for further replies.
why do you use the r perm for parity, why not say a j perm, or y perm, or what ever?

Talking of Old Pochmann? Well, if you have an uneven number of edges to shoot, then the 2 corners in the T perm are swapped. So, if you do a R perm, it swaps those 2 corners and 2 edges that you would swap in the Y perm when shooting corners.
 
What is the best/easiest way to learn COLL?

I don't have a problem with the recognition method or learning the algs, but how do you match them up to start?
I guess what I'm trying to say is, when starting COLL, how did you get practice recognizing and relating the cases?
 
I ordered from SpeedCubeShop and got a Track and Confirm code. I used it and it told me it was in Bakersfield California. That was a week ago and the track and confirm still tells me it is in Bakersfield. Whats the deal?
 
Maybe I'm stoopid, but I kind of need this illustrated for me.

When using 3OP+M2 and you have corner permutation parity, what do you do to fix this? I'm trying to figure out how to do this without stuffing up the edges. E.g. I memo edges. All good. Then I memo corners, and find out I have parity. If I executed corners and then did a 2/2 swap, wouldn't the edges that I just memoed be wrong?

My brain hurts.

If your corner buffer is ULB, then perform an R perm once you've solved corners to swap UL and UB, as well as UBR and URF. Then solve edges normally. Once edges are solved, do U' F2 U M2 U' F2 U, followed by that same R perm again.

(This is assuming that for your last corner you simply use a PLL to swap your buffer with the unsolved corner, also swapping UL and UB in the process.)

If you solve edges first, all you have to do is U' F2 U M2 U' F2 U in between edges and corners.

Hope this helped.

Urdoinitrong (No offense)

That's Old Pochmann parity, which I have no problem with. In old pochmann, there is a fixed corner buffer and the edge buffer is where you said it is. (usually)

With 3OP and M2, the edge buffer is kinda the whole M slice, except it isn't really a buffer, so whatever. The corners don't even HAVE a buffer fyi, they're solved with 3 cycles. (And 2 corner swaps such as E-Perm.) But I now realise all I have to do is swap the two corners that are a 2 Cycle, and the UB/DF edges, wherever they may be.

Ya so thanks for helping me think, anyway.
 
My avg is around 22, should i learn MGLS and how should i start with it. Thanks a lot :D
If you know full OLL and PLL there's no reason to learn more algorithms at your speed.

So I say this- if you want to learn MGLS, learn MGLS. There are a lot of options for LL, that's just one of them.
 
I just know about 10 OLLs, so i think i 'll go for it :D But MGLS is totally different and don't use any OLLs, so how can i start with it ?
 
I am currently using 2-look OLL.
How much sense would it make to learn VHF2L instead of 1-look OLL?

I like the idea behind VHF2L but wonder why you would use it if you know 1-look OLL?
 
Well, personally, I use 1-look OLL, but I see absolutely no reason not to use VHF2L instead. There seem to be fewer algs and recognition doesn't look like it would be too much of a problem. Why not?

Unless someone can provide a good reason not to use VHF2L, I say go for it. =)

The reason a 1-look OLL user might learn some of these cases could be to force the OLL into a case they favor, or (in very rare cases) if the user is learning ZBLL. However, I think that you are correct. In general, a 1-look OLL user has no need for VHF2L.
 
I just know about 10 OLLs, so i think i 'll go for it :D But MGLS is totally different and don't use any OLLs, so how can i start with it ?
Learn all of the ELS. Then solve the F2L case you get using <R,U>. That'll preserve edge orientation.
 
Status
Not open for further replies.
Back
Top