#### Animaginarytale

##### Member

- Joined
- Jun 4, 2019

- Messages
- 11

I stumbled across an old thread talking about U2, an improvement to R2, which you all know is generally regarded as bad. The idea is similar, but you setup to UFR and use U2 to swap with UBL buffer instead.

The problems with the older thread:

Parity sucked

Special cases sucked

So I have decided to use speed optimal comms instead and a simple parity method to use in conjunction with M2.

METHOD:

The method is very simple, setup to UFR (without disturbing anything else on U), do U2, undo setup. However, for special cases (everything on U) there are algs, and if they come second in a letter pair you must shoot to the opposite target.

So:

UBR - UFL

RBU - LUF

BRU - FUL

The more optimised algs are (from Jack Cai’s Comm list):

UBR: Aa Perm U2

RBU: R D R2 D2 R U2 R’ D2 R U2 R D’ R’ U2

BRU: R’ D’ U2 R’ D R U2 R’ D’ R D R U2

UFL: U2 Ab Perm

LUF: F U2 R’ D’ R U2 R’ D R F’ U2

FUL: Lw’ U2 R’ D2 R U2 R’ D2 R’ Lw U2

FRU: R' D' R D R' D' R U2 R' D R D' R' D R

RUF: R' D R D' R' D R U2 R' D' R D R' D' R

PARITY:

1) CEEC order

If you find parity during corner memo, during M2 do parity to swap UL and UB. Then do U2 as per normal and do parity alg:

U2 (FRU’R’U’RUR’F’RUR’U’R’FRF’) or U2 (Y perm)

2)ECCE order

Do corners as per normal, do U2 before edges, then do edges as normal/use UL UB swap. If you use basic M2, do the parity at the end. To fix parity, do FRU’R’U’RUR’F’RUR’U’R’FRF or basically a Y perm to end.

Advantages of this method:

Simple and similar to M2

Faster than OP and has potential to sub 50 (with M2)

Disadvantages:

Slow(er?)

Takes some time to get used to (like M2)

What do you think of this method? Like potential, limits and improvements? Just tell me below! Any feedback is welcome.

Edit:

This is the original thread: https://www.speedsolving.com/threads/u2-method-for-corners-and-edges.39840/

This is the thread I found: https://www.speedsolving.com/threads/new-3bld-corners-method-u2.47632/

The problems with the older thread:

Parity sucked

Special cases sucked

So I have decided to use speed optimal comms instead and a simple parity method to use in conjunction with M2.

METHOD:

The method is very simple, setup to UFR (without disturbing anything else on U), do U2, undo setup. However, for special cases (everything on U) there are algs, and if they come second in a letter pair you must shoot to the opposite target.

So:

UBR - UFL

RBU - LUF

BRU - FUL

The more optimised algs are (from Jack Cai’s Comm list):

UBR: Aa Perm U2

RBU: R D R2 D2 R U2 R’ D2 R U2 R D’ R’ U2

BRU: R’ D’ U2 R’ D R U2 R’ D’ R D R U2

UFL: U2 Ab Perm

LUF: F U2 R’ D’ R U2 R’ D R F’ U2

FUL: Lw’ U2 R’ D2 R U2 R’ D2 R’ Lw U2

FRU: R' D' R D R' D' R U2 R' D R D' R' D R

RUF: R' D R D' R' D R U2 R' D' R D R' D' R

PARITY:

1) CEEC order

If you find parity during corner memo, during M2 do parity to swap UL and UB. Then do U2 as per normal and do parity alg:

U2 (FRU’R’U’RUR’F’RUR’U’R’FRF’) or U2 (Y perm)

2)ECCE order

Do corners as per normal, do U2 before edges, then do edges as normal/use UL UB swap. If you use basic M2, do the parity at the end. To fix parity, do FRU’R’U’RUR’F’RUR’U’R’FRF or basically a Y perm to end.

Advantages of this method:

Simple and similar to M2

Faster than OP and has potential to sub 50 (with M2)

Disadvantages:

Slow(er?)

Takes some time to get used to (like M2)

What do you think of this method? Like potential, limits and improvements? Just tell me below! Any feedback is welcome.

Edit:

This is the original thread: https://www.speedsolving.com/threads/u2-method-for-corners-and-edges.39840/

This is the thread I found: https://www.speedsolving.com/threads/new-3bld-corners-method-u2.47632/

Last edited: Aug 20, 2019