Blindsolving Discussion and Help

[sa11297]

I really don't recommend doing M2 with the M slice flipped when you have parity. I strongly urge you to do what Julian said:

1. Solve the corners, except for the last target.
2. Solve the edges.
3. U' F2 U M2 U' F2 U
4. Solve the last corner target.

can you explain why you dont think that having the m slice swapped is a good idea? the ONLY thing it does is make it so that odd numbered swaps are the opposite algorithm instead of even, right? please correct me if I am wrong

EDIT: i kind of got ninja'd so nvm. My new question is: Is there a good way to check for parity at the beginning?

 

[JasonK]

Is there a good way to check for parity at the beginning?

Just count the number of corner targets, if it's odd you have parity.

1. Solve the corners, except for the last target.
2. Solve the edges.
3. U' F2 U M2 U' F2 U
4. Solve the last corner target.

Wow, I hadn't thought of that before, I may steal it.

 

[Julian]

I really don't recommend doing M2 with the M slice flipped when you have parity. I strongly urge you to do what Julian said:

1. Solve the corners, except for the last target.
2. Solve the edges.
3. U' F2 U M2 U' F2 U
4. Solve the last corner target.

Hey Rob, I use auditory memo for corners. If I were to do this, what's a good way to remember that last corner target all the way through?

 

[lucarubik]

parity edge and corner I memo them visually, as pasive pieces

 

[sa11297]

thank you guys for answering my questions quickly and completely. Just so you know my current situation, I am using pochmann edges and corners as seen on badmephisto's video (and an R perm for parity). I use tapping only for memo and memo edges then corners. I take around four to five minutes for the whole solve, and my best is 3:41.

I am transitioning to M2+pochmann (obviously) and I will probably change my edge memo to lettering using speffz. I will solve like this:
1. Solve the corners, except for the last target.
2. Solve the edges.
3. U' F2 U M2 U' F2 U
4. Solve the last corner target.

and eventually learn TuRBo and maybe even BH.

any tips on anything? like on how I should do memo if you think that my way is bad? also I am thinking on fixing edge orientation at the end if the m slice has incorrectly oriented edges or if there is a correctly permuted but incorrectly oriented edge outside the m slice to begin with.

 

[riffz]

Hey Rob, I use auditory memo for corners. If I were to do this, what's a good way to remember that last corner target all the way through?

What lucarubik said. Just memorize the parity piece visually. You could also add the single letter to your memo so you're at least reminded of the last corner when you finish executing them.

 

[Julian]

Okay, thanks Rob and Lucas. I'll start trying this

 

[lucarubik]

cool to find someone who call me by my name, not luca and stuff

 

[Julian]

cool to find someone who call me by my name, not luca and stuff

Haha, cool

So I was using this (last corner target after edges), but came across a problem. Twisted corners. If there are any, should I do them after edges as well? And how should I memo them? Right now I memo them with a weird combination of auditory and visual.

 

[lucarubik]

visual is right, and yes you should do them after edges as well, maybe you can try to solve edges first, or change the way you solve the parity so you can solve the last corner before the edges, you could solve the last corner with OP, then do M2 L U' L' U M2 U' L U L' M2- first edge (as I used to)

 

[Julian]

visual is right, and yes you should do them after edges as well, maybe you can try to solve edges first, or change the way you solve the parity so you can solve the last corner before the edges, you could solve the last corner with OP, then do M2 L U' L' U M2 U' L U L' M2- first edge (as I used to)

But doesn't that leave the M-slice off? i don't want that.

Ok, I'll try solving last corner + twisted corners after edges now in parity solves.

 

[lucarubik]

why dont you want that?
if you want to be free to use comms you are, its like doing DB- UB- UL and then DB- UB- first memoed

 

[thackernerd]

I'm trying to memorize old Pochmann and I've almost got it but how are supposed to know if and edge is flipped correctly or not?

 

[Cube Equation]

Where can I learn M2/R2 effectively? The Youtube videos I've seen are a bit fast-paced and Stefan Pochmann's website does not give sufficient details (in my opinion, though I do understand the basics of the method).

 

[Cubenovice]

I'm trying to memorize old Pochmann and I've almost got it but how are supposed to know if and edge is flipped correctly or not?

“There are no flipped edges” in Old Pochmann.
You have to think in “stickers” instead of edges: You shoot the “sticker” that is in your buffer position to its correct location – (repeat until edges are solved)

“There may be some flipped edges” on your cube though…
But these are the edges that are flipped in place and you should have no problem in identifying those.

 

[porkynator]

Just a quick question: is it worth using more than 1 buffer (when a buffer gets solved, changing it)? Why?

 

[RyanReese09]

No. What if that buffer gets solved while still using the first buffer? Too much thinking.

 

[Mike Hughey]

Another perspective:

Yes. Especially with centers on big cubes. Buffers routinely get solved when solving centers on big cubes, with an average that seems to be around 2 solved per attempt per type of center piece. So by switching buffers, I average about one fewer commutator per solve, per type of center piece.

It doesn't seem like too much thinking to me, but I admit I haven't tried the alternative; I've always done it this way.

 

[Henrik]

I know (or am pretty sure) that Ville uses floating buffers. (going clockwise on the U layer starting at UF?)

And as far as I know LarsN has been experimenting with floating buffers as well on the big cubes.

But I like brain-dead buffers

 

[Mike Hughey]

Chris Hardwick uses floating buffers on wings, but not centers. I use floating buffers on centers, but not wings.