I've been screwing around, avioding BLD for a long time now.... I need 3OP + M2 guide

try (M2 E2) (RUR'U')|(E2 M2) (URU'R')
i dont have a cube to hand, but im pretty sure thats a 5-cycle...
ill edit it in a minute if its not.
another cool 'g-perm' with edges and corners is
(r2) (RUR'U')|(r2) (URU'R').
 
well, im saying, yes, you can maybe just find a random 5-cycle like that. but I don't think someone can find good 5-cycles for a chosen 5-pieces on the spot. Someone, please prove me wrong, and show me how.
 
Even I don't have a cube at hand and I too am sure that its a 5 cycle. It gives me an idea of how one may do a 5 cycle. My understanding of it now goes this way.

3-cycle - 2 swaps with a cubie common
5-cycle - 2 three cycles with a cubie common
 
my understanding of very easily creating cycles is...
3 edge cycles - one inner slice + RUR'U' (and its inverse, obviously)
5 edge cycles - 2 inner slice turns + sexy trigger and inverse
edge and corner 3 cycles - wide turn/equivalent + sexy trigger and inverse.
these require no understanding, and are good for practising actually solving commutators.
 
I've been playing wiht 3OP recently and I have a question.

1. Do you solve 3 pieces at a time?
2. I'm learning it because I plan to go freestyle corners, what else will I need to know?
3. What's a good memo method for freestyle corners?
4. How fast can M2 edges with freestyle corners get?
 
I've been playing wiht 3OP recently and I have a question.

1. Do you solve 3 pieces at a time?
2. I'm learning it because I plan to go freestyle corners, what else will I need to know?
3. What's a good memo method for freestyle corners?
4. How fast can M2 edges with freestyle corners get?

1. 2 at a time
2. Commutators
3. Images
4. You can get the WR with it.
 
I've been playing wiht 3OP recently and I have a question.

1. Do you solve 3 pieces at a time?
2. I'm learning it because I plan to go freestyle corners, what else will I need to know?
3. What's a good memo method for freestyle corners?
4. How fast can M2 edges with freestyle corners get?

well ville, the WR holder, memos freestyle corners by numbers/visual. He remembers wher the pieces have to b permuted with the numbers, then remembers the orientation/way the stickers are facing with visual. Mcwizzle uses M2 and sometimes freestyle and he can get 1:2x.xx, but i agree with tim, i think you could get the WR with that method.
 
I've been playing wiht 3OP recently and I have a question.

1. Do you solve 3 pieces at a time?
2. I'm learning it because I plan to go freestyle corners, what else will I need to know?
3. What's a good memo method for freestyle corners?
4. How fast can M2 edges with freestyle corners get?

well ville, the WR holder, memos freestyle corners by numbers/visual. He remembers wher the pieces have to b permuted with the numbers, then remembers the orientation/way the stickers are facing with visual. Mcwizzle uses M2 and sometimes freestyle and he can get 1:2x.xx, but i agree with tim, i think you could get the WR with that method.

Not really but I'm trying to learn it =]
 
well ville, the WR holder, memos freestyle corners by numbers/visual. He remembers wher the pieces have to b permuted with the numbers, then remembers the orientation/way the stickers are facing with visual.
Pretty much, I would just like to point out that I remember the 2 things at the same time. I sort of "feel" the right sticker when memorising. I'm not completely sure how I use this memo method. It has something to do with having stickers in UD, FB and RL group. So say I have UFL->BUR->LBD it would be 136 for the order and the stickers go something like "correct", FB, RL. It's weird.

Mcwizzle uses M2 and sometimes freestyle and he can get 1:2x.xx, but i agree with tim, i think you could get the WR with that method.
Not for long. :) (I hope)
 
OK, I've come to a conclusion with my method which I shall use!!!

Execution:

Corners = 3OP/freestyle
Edges = M2 for all excluding the M slice for the M slice I will use classic Pochmann to avoid bad orientation

Memo:

corners = (uncertain) visual orientation + numbered Permutation
Edges = (95% sure) Person+Action
 
How do you use Classic Pochmann for the M slice? The buffers are different...

Unless you mean first rotate the cube so that DF is in UR, do the set up moves, do a T perm, undo setup moves, undo cube rotation, but that seems ridiculously slow to me.

I think it would be way faster to just preorient the M slice and then learn the simple algs (U2 M' U2 M', M2, M U2 M U2) to shoot to the oriented M slice locations. That's what I'm doing right now because it's still way faster than Classic Pochmann edges.
 
Last edited:
Edges = M2 for all excluding the M slice for the M slice I will use classic Pochmann to avoid bad orientation

How do you use Classic Pochmann for the M slice? The buffers are different...

Unless you mean first rotate the cube so that DF is in UR, do the set up moves, do a T perm, undo setup moves, undo cube rotation, but that seems ridiculously slow to me.

I think it would be way faster to just preorient the M slice and then learn the simple algs (U2 M' U2 M', M2, M U2 M U2) to shoot to the oriented M slice locations. That's what I'm doing right now because it's still way faster than CP edges.

Uh what? Most of that post didn't make sense :/

I was responding to the part of his post quoted above.

Maybe he's not using Classic Pochmann the way I'm used to and using that method it's efficient, but if that's true, I'd like him to elaborate on that as I'd be interested in the method.

The rest of the post I was basically explaining how I assumed one would use Classic Pochmann during the middle of an M2 solve using cube rotations to make up for the change in buffer. Of course, that would mess up some other stuff which you'd have to fix, making things even worse.

Then I proposed a method I use which simplifies shooting to places on the M slice by preorienting. It's slow, but I think it's faster than Classic Pochmann.
 
Last edited:
Ah okay, I understand a little more now.

But, I think you mean 3OP? CP means corner permutation..

No, I was using it as short for "Classic Pochmann" because I was being lazy and I hoped that the context would make sense despite the overloaded abbreviation.

I'll fix the OP.
 
Back
Top