The New Method / Substep / Concept Idea Thread

[brododragon]

Reminds me of another post where someone thought they never got parity with their solving order for 3BLD.
If you can't figure out if it will be a skip or not intuitively, then please do some more testing before posting.

I'll try to do more testing, it was 12:00.

 

[zimlit]

Steps:
1. 2x2x3 + eo
2. right cross edge and back right f2l pair
3. Remaining edges
4. last 5 corners

 

[RedstoneTim]

Steps:
1. 2x2x3 + eo
2. right cross edge and back right f2l pair
3. Remaining edges
$. last 6 corners

This seems good for a 2 look LSLL approach. However there's an issue with alg count (for comparison, L5CO which only solves five corners is already 614 algorithms).
Also as I've said on the Discussion page of the wiki article, the name ZZ-EF is already taken so this should be renamed and possibly just be listed as a variant in the ZZ wiki article.

 

[ProStar]

Steps:
1. 2x2x3 + eo
2. right cross edge and back right f2l pair
3. Remaining edges
$. last 6 corners

What type of EO? Petrus style?

 

[zimlit]

This seems good for a 2 look LSLL approach. However there's an issue with alg count (for comparison, L5CO which only solves five corners is already 614 algorithms).
Also as I've said on the Discussion page of the wiki article, the name ZZ-EF is already taken so this should be renamed and possibly just be listed as a variant in the ZZ wiki article.

the alg count should be the same as L5CO since I accidentally wrote the wrong thing it just needs to preserve edges. as for the name that is true all though I'm not sure to call it. also it only has those 614 algs since everything else is intuitive and you could reduce the alg count by using heise techniques to solve two more corners leaving you with a heise finish.

 

[zimlit]

What type of EO? Petrus style?

I would assume that it is petrus style but I've never completely understood the difference

 

[fortissim2]

Steps:
1. 2x2x3 + eo
2. right cross edge and back right f2l pair
3. Remaining edges
$. last 6 corners

Isn't it just 5 corners?

 

[Parity Nightmare]

Seems like an interesting method!

 

[dodecicosidodecahedron]

The idea is to orient the corners and turn them right with only 2 algorithms. That works everytime nomatter how the LL look like after F2L.
You apply a trigger algorithm right after F2L and you either have an X or no correct color on the edges. That means you only have 3 OLL pattern left if X and slightly more 12 OLL if no color.

Isn't this basically just CLP + ELL?

 

[zimlit]

Isn't it just 5 corners?

Yes

 

[mukerflap]

Welp, there goes 1lll for Petrus-W. I guess CLP->L5EP is your best bet still

Petrus W is now officially unusable

 

[RedstoneTim]

the alg count should be the same as L5CO since I accidentally wrote the wrong thing it just needs to preserve edges. as for the name that is true all though I'm not sure to call it. also it only has those 614 algs since everything else is intuitive and you could reduce the alg count by using heise techniques to solve two more corners leaving you with a heise finish.

If we just concentrate on the 2LLSLL after F2L-1 + EO (since the steps before are just Petrus), this would have to be more efficient than already existing approaches to LSLL in two looks (like ZZ-a and ZZ-Zipper) to be viable. (Maybe someone here can calculate the average movecount?).
Also to reduce algorithms, conjugated COLL (the idea is taken from 42) might be possible (although you have to consider that reducing alg count also means raising movecount).

 

[Deleted member 51471]

Petrus W is now officially unusable

WV HKPLL is usable

 

[zimlit]

If we just concentrate on the 2LLSLL after F2L-1 + EO (since the steps before are just Petrus), this would have to be more efficient than already existing approaches to LSLL in two looks (like ZZ-a and ZZ-Zipper) to be viable. (Maybe someone here can calculate the average movecount?).
Also to reduce algorithms, conjugated COLL (the idea is taken from 42) might be possible (although you have to consider that reducing alg count also means raising movecount).

conjugated coll seams like an interesting Idea it also probably would not take to many moves

 

[Skewbed]

If we just concentrate on the 2LLSLL after F2L-1 + EO (since the steps before are just Petrus), this would have to be more efficient than already existing approaches to LSLL in two looks (like ZZ-a and ZZ-Zipper) to be viable. (Maybe someone here can calculate the average movecount?).
Also to reduce algorithms, conjugated COLL (the idea is taken from 42) might be possible (although you have to consider that reducing alg count also means raising movecount).

Conjugated COLL should work. Then, you would just have L5EP. Although this would probably be better with ZZ than Petrus.

1. EOCross (probably better than EOLine)
2. Left pairs/block
3. BR slot
4. Conjugated COLL (42 algs)
5. L5EP (16 algs, 12 without EPLLs)

Seems pretty good, especially for it's alg count.

 

[Cubingcubecuber]

Conjugated COLL should work. Then, you would just have L5EP. Although this would probably be better with ZZ than Petrus.

1. EOCross (probably better than EOLine)
2. Left pairs/block
3. BR slot
4. Conjugated COLL (42 algs)
5. L5EP (16 algs, 12 without EPLLs)

Seems pretty good, especially for it's alg count.

When is the DFR corner solved?

 

[Skewbed]

When is the DFR corner solved?

During conjugated COLL.

 

[Cubingcubecuber]

During conjugated COLL.

What’s that? Is it like COLL but as a conjugate, so x, COLL, x’

 

[carcass]

COLL, but only to avoid diagonal plls, so it would be fewer algs and not as bad for the sune and antisune cases

 

[RedstoneTim]

Conjugated COLL should work. Then, you would just have L5EP. Although this would probably be better with ZZ than Petrus.

1. EOCross (probably better than EOLine)
2. Left pairs/block
3. BR slot
4. Conjugated COLL (42 algs)
5. L5EP (16 algs, 12 without EPLLs)

Seems pretty good, especially for it's alg count.

This is the basic idea of ZZ-Zipper. Conjugated COLL should probably be added as an alternative to L5CO though.

conjugated coll seams like an interesting Idea it also probably would not take to many moves

After some thought, I've noticed that this won't work. COLL doesn't preserve edge permutation, so L4C would have to be used. The disadvantages are that L4C is 84 algs, recognition will be a lot harder and that it's also considered one of the worst ZBLL subsets. So this seems to be a pretty bad approach.

Edit: For everyone wondering how Conjugated COLL works, I've made a wiki article for it.