Blindsolving Discussion and Help

[DYGH.Tjen]

He is using Buffer = A, and it goes to I. Maybe you just scrambled wrong.



Memo is correct.

Correct, but way to many moves.
Use this comm: [l, F r' F'] (Executed as x [l, U r' U'] x')
or this: y' [l u l', U] y

There is the mistake. The comm is for UC, not for UD. Use something like that: U [D r2 D', l2] U'

Correct, but do a cube rotation like this: U y' x [r U2 r', d2] x' y U'

Correct but slow. Much better: L' [u, r' U2 r] L

Correct.

Correct.

Corrcet, but much nicer with a rotation: x' [r' U2 r, u2] x

Correct, better: R' [d', r U2 r'] R

Correct.

Here is your incorrect solution: http://tinyurl.com/algrF-d2r-UrFr
Here is the corrected version with some of my comms: http://tinyurl.com/alglFr-F-UDr2D

Thank you very much Jakob!

Also, Sorry that question was irrelevant, what I should've of asked is: Can you please label the buffers you're using for each cycle?
I first assumed it was A, but that doesn't go to I.

Is that your mistake?

Thanks Zane for trying! @Jakob yeah I know my comms are wayyyyyy not-optimal. How do you look for 'good' comms everytime you solve? Or are you already used to the comm from doing it too often? =D

EDIT: Oh we're all online atm.

EDIT2: Jakob is off.

EDIT3: Jakob is on, Zane's off.

 

[Jakube]

EDIT2: Jakob is off.

And back online.

I already used to most of the comms. I can do them fast without barly thinking. For other cases I have a certain "plan" how to do them.
If the two targets are both on F, R, B, L-face, I normally do a Setupmove (F, R, B, L) and then do something like that: [r U2 r', d2]. I always look for a good setup move. There are most of the time two possibilities how to do the setup. Sometimes I also use a 9-mover, because its just faster than do Rotation 8-mover Rotation. F.I. GS optimal would be: [f U' f', d], much faster is: d [r U2 r', d] d'
If there is one target on the U-face or on the D-Face I also know some tricks, how to handle them fast.

It´s just practice, every solve you do you will discover nicer and faster comms.

 

[Michael1026]

Are there any tuts on old pochman for 2x2's? Because 2x2's aren't necessarily the same as 3x3's.

 

[aronpm]

You can solve a 2x2 blindfolded exactly the same as 3x3 blindfolded, ignoring edges.

 

[Carson]

I use M2 + Old Pochman for corners, solving corners first. If I have parity and an edge to flip, should I wait until after executing the parity algs to perform the edge flipper?

 

[Cubenovice]

Are there any tuts on old pochman for 2x2's? Because 2x2's aren't necessarily the same as 3x3's.

As Aronpm mentioned: 2x2x2 is identical to solving the corners of a 3x3x3

My preferered Old Pochmann tutotial: Joel van Noort's

 

[DYGH.Tjen]

I use M2 + Old Pochman for corners, solving corners first. If I have parity and an edge to flip, should I wait until after executing the parity algs to perform the edge flipper?

If you use M2/OP and solve corners first, all you have to do is solve corners, do an R-perm (R U' R' U' R U R D R' U' R D' R' U2 R' U'), solve edges, then do another R-perm and U' F2 U M2' U' F2 U.
So basically what the R-perm does is switches UB and UL edges, while simultaneously switching UFR and UBR corners. If you have parity and solve corners first, the Y-perms will make the UB and UL edges swapped, as you did an ODD number of Y-perms. If you do 2 it's fine, but if you think about it, if you do 1, 3, 5 etc, the UB and UL edges will be swapped. To fix this, do an R-perm directly after solving corners. This will then restore the edges, but switch the UFR and UBR corners. Leave it that way.
So, you have solved your edges. Since you have parity (an odd number of edge targets), you will be an M2 off. So what you have now is an M2 off and the 2 corners you switched earlier. Do the fix U' F2 U M2' U' F2 U, this basically restores the M slice and switches UB and UL edges. Then do an R-perm to restore everything.

Hope that helped

 

[MeshuggahX]

I use M2 + Old Pochman for corners, solving corners first. If I have parity and an edge to flip, should I wait until after executing the parity algs to perform the edge flipper?

I flip the incorrect edges last, after my parity alg.

 

[Carson]

If you use M2/OP and solve corners first, all you have to do is solve corners, do an R-perm (R U' R' U' R U R D R' U' R D' R' U2 R' U'), solve edges, then do another R-perm and U' F2 U M2' U' F2 U.
So basically what the R-perm does is switches UB and UL edges, while simultaneously switching UFR and UBR corners. If you have parity and solve corners first, the Y-perms will make the UB and UL edges swapped, as you did an ODD number of Y-perms. If you do 2 it's fine, but if you think about it, if you do 1, 3, 5 etc, the UB and UL edges will be swapped. To fix this, do an R-perm directly after solving corners. This will then restore the edges, but switch the UFR and UBR corners. Leave it that way.
So, you have solved your edges. Since you have parity (an odd number of edge targets), you will be an M2 off. So what you have now is an M2 off and the 2 corners you switched earlier. Do the fix U' F2 U M2' U' F2 U, this basically restores the M slice and switches UB and UL edges. Then do an R-perm to restore everything.

Hope that helped

I got this part, thanks though. I was asking what MeshuggahX answered below. My approach is a little different than yours I think. For parity, I do a J perm after corners and M' U2 M' U2 followed by a Y rotation and a T perm after edges.

I flip the incorrect edges last, after my parity alg.

This is what I was asking, thank you!

 

[MrMoney]

Hi all,

I seem to have forgotten the r2-parityalg . r U2 r2 U2 r U2 r U2 r2 l U2 ri U2 r U2 li U2 .... it goes along this line. What am I doing wrong? the centers turn up wrong.

 

[Jakube]

@MrMoney: Do you mean this one?

Parity fix: If you have an odd number of edges memorized, you have parity, this is the case where the DFr and UBr edges are
solved, and the rest of the r slice is an r2 away from solving. The algorithm to solve this parity is:
r2 D' L' F l' U2 l' U2 F2 l' F2 r U2 r' U2 l2 F' L D.

 

[MrMoney]

Hi JAkube, that "effect" but not that algorithm! I find that algorithm not particulary good... r U2 algorithm is needed

 

[MaeLSTRoM]

Here's a better alg for that.
first, do a r2 so the centres are solved.
then:
[F2:rU2r'U2r'U2lU2r'U2rU2F2r2F2l']

 

[tim]

Hi all,

I seem to have forgotten the r2-parityalg . r U2 r2 U2 r U2 r U2 r2 l U2 ri U2 r U2 li U2 .... it goes along this line. What am I doing wrong? the centers turn up wrong.

http://www.garron.us/archive/data/r2_parity.txt you're welcome.

 

[MrMoney]

Thank you tim!!! r' U2 r2 U2 r U2 r U2 r2 l U2 r' U2 r U2 l' U2 was the algorithm I was seeking. First move is ri instead of r!

 

[Jakube]

Nice alg, maybe I´ll switch.
I´ around 1 second faster than with my normal way.

 

[aaronb]

Is the Multi Blind WR decided by points (Number of solved cubes - number of unsolved cubes), or by how many they have solved, then if that is tied it goes to points?

 

[MaeLSTRoM]

Is the Multi Blind WR decided by points (Number of solved cubes - number of unsolved cubes), or by how many they have solved, then if that is tied it goes to points?

Points, then time.

 

[Cubenovice]

This 4bld centers discussion has inspired me:

my first (sighted) attempt at figuring out comms for centers:
Uw R' U' Fw D2 Uw Fw Uw2 F' Uw2 R2 F' U2 L' B2 Fw' Uw' U2 Fw' L Uw L' D2 F2 L' Rw2 R' U F2 U2 F R Uw L' R B' D' U' L2 R2

I solve with Yellow top, green front I placed Speffs letters after // for your reference


x' y2 // orientation to solve some stuff
F u r U r' u' r U' r' F' // MI
f u' r U r' u r U' r' f' // UJ
U2 b l U2 l' d l U2 l' d' b' U2 // SX (this is the crazy one, moving my buffer piece out of the way, do people actually do this???)
f' U2 f d f' U2 f d' // PL (P is where I typically store buffers for a new cycle, even though it was not the next R face piece in typical memo order)
L2 f U' f' d2 f U f' d2 L2 // EO
D' r f U2 f' u f U2 f' u' r' D // FW
r U2 r' d r U2 r' d' // KG
f' U2 f d2 f' U2 f d2 // PH (new cycle)
r' U r d' r' U' r d // TH (close the loop)

alg garron


Some questions:
do you do stuff like a set up move that actually moves the buffer?
what is your typical storage location in case the whole U face (buffer face) is solved?
- "next piece" on a specific face or "last piece" on a specific face (I hiope you get what I mean...)

 

[amostay2004]

Thank you tim!!! r' U2 r2 U2 r U2 r U2 r2 l U2 r' U2 r U2 l' U2 was the algorithm I was seeking. First move is ri instead of r!

It's r if you don't do the r2 first, ie cancelling with the r' in the alg