Some example solves with a strange ZZ/roux hybrid

[CubeRoots]

first things first, I am not an advocate for this method, nor do I claim it is good or I 'invented' it - so feel free to rip it apart. all I say is it's pretty interesting, especially for the ZZ/Roux user. Also, there are probably lots of improvements to be made, I am not a great blockbuilder and i have only been practicing this method for a couple of hours. And roux for a day or so.

It goes like this:

EO (read: EO, NOT EOLine)
Build two 2*2*3 blocks on the left and right layers (same as roux), except: only use a subset of the moves <R,U,L,D,M2,r2,l2> +?<E2,S2,u2,d2>?, this preserves EO.
COLL
LSE (however, if you have followed the method correctly you should not need to orient)

solve 1

Scramble: L' R U' F U' L2 R' D' R' D L R D' R' F2 D' B2 R2 U2 D' R2 D' L F R'

Solution:
L D' R D F' // EO (5,5)
U M2 R U' L U L2 U' R' U' // Block 1 (10,15)
M' l' R' U R2 U R' U2 R U' R' U R U' R' // Block 2 (15,30)
R' U2 R' D' R U2 R' D R2 // COLL (9,39)
M U2 M U M2 U' //Permute UL/UR (6,45)
M U2 M' // finish (3,48)

Solve 2

Scramble: F' R' B' D2 U B' R2 D' F' L' B2 R2 U' F' D L2 R F' D R2 L2 F' L2 U D

Solution:
D' F' L D' R2 F' // EO (6,6)
R U' R' U R U2 R' U' D' M2 U' R' U L2 U2 L R' U R U M' l' U L // blocks (24,30)
U l' U2 R' D2 R U2 R' D2 R2 //COLL (10,40)
U2 M U2 M U' M2 U' // Permute UL/UR (7,47)
M2 U2 M2 U2 // finish (4,51)

Solve 3

Scramble: R2 U' B2 F L' B2 D2 B L' D2 L' R U' B' D U R' U' F' U' R2 B L2 F2 B'

Solution:
F D2 R U B // EO (5,5)
U' R' U R' L' U L U' L U2 R U' L' // Block 1 (13,18)
R' U r2 L' U R U' L U M2 U2 M' r U' R' // Block 2 (15,33)
U' l' U2 R' D2 R U2 R' D2 R2 // COLL (10,43)
U M2 U M2 U //(5,48)
M E2 M' E2 // lol finish (4,52)

You may notice, there are a tonne of cancellations in there i cba with sorting out. some of the blockbuilding is grim too.

What do you think of the solves/method?

 

[Kirjava]

I am not an advocate for this method, nor do I claim it is good or I 'invented' it - so feel free to rip it apart

:tu

me and rob explored various versions of this system a few years ago. concluded that you're performing a harder system to achieve a worse movecount.

we couldn't make it work, maybe you can though.

 

[CubeRoots]

we couldn't make it work, maybe you can though.

I really want it to :'(

oh and by the way, how does the roux user perform M? M' is great but M is a nightmare for me

 

[Kirjava]

Depends what alg it appears in. There are many ways.

I've taken to using my left ring finger to push from D to B recently though.

Like in here;

 

[A Leman]

I feel that by preserving eo in a Roux solve you loss moves on your blocks and your Coll Just to force an eo skip, but in a normal Roux solve the eo and UR/UL pairing normally happen at the same time. I don't feel like it is worth it since planing the EO burns inspection time and preserving it increases movecount.

 

[Athefre]

Rarely is EO a good step. Instead of direct solving it partially solves the edges. It works well in OLL because corners are involved too. It works well in LSE because it happens that it is easy to manipulate the LR edges.

 

[5BLD]

EO beforehand is never good in Roux. It simply adds moves. Sure COLL is nice but may as well do EO influence in SB to COLL or even DFDB orient during SB then OLLCP.

Also! Misoriented edges in step 4a are sometimes better than skips!

 

[Kirjava]

Also! Misoriented edges in step 4a are sometimes better than skips!

Yah, its like how some parity cases are better than non parity.