The Orcuber's Hunt For The Best 3x3 Method

[0rcoraCuber21]

I have a method idea. I’ll name it HF-O “Hexagonal Francisco (Orcuber variant)”

1. Build a 223 block
2. Solve PAE (pair and edge). PAE is solving the FR pair and the DB edge at the same time. (algorithmic)
3. Rotate so the 223 block is at the back, then for the rest of the first 2 layers and orient the edges at the same time (HFOLS, algorithmic, ~305 algs)
4. ZBLL (algorithmic, ~493 algs)

The PAE is the last pieces of the 2x2x3 block right or am I misunderstanding this.

 

[Martyt7777]

The PAE is the last pieces of the 2x2x3 block right or am I misunderstanding this.

I mean like this

Step 1 is 2x2x3 block

Step 2 is PAE

 

[0rcoraCuber21]

I mean like this

Step 1 is 2x2x3 blockView attachment 48178
Step 2 is PAE

View attachment 48179

Yeah okay what about the DB edge isn't it solved in a 2x2x3 block held on the left.

 

[Martyt7777]

Yeah okay what about the DB edge isn't it solved in a 2x2x3 block held on the left.

Mb I meant the BR edge

 

[CrossPetrus]

I’m genning the eopair algs and I’m getting 896 cases right now. Manageable, but a lot, especially if I make step 3 algorithmic.

 

[CrossPetrus]

Here are the eopair algs. There are 896 cases and the algs average 7.59 stm.

https://docs.google.com/spreadsheets/d/1BVRZaAykXFQ4UKC8O7uks14n_LOoSsR5/edit?usp=drivesdk&ouid=100242630063312859715&rtpof=true&sd=true

 

[Caleb Valenzuela]

but id think that zbls+zbll is worse than wv+pll

I turned into a skull emoji after reading that

I have a method idea. I’ll name it HF-O “Hexagonal Francisco (Orcuber variant)”

1. Build a 223 block
2. Solve PAE (pair and edge). PAE is solving the FR pair and the BR edge at the same time. (algorithmic)
3. Rotate so the 223 block is at the back, then for the rest of the first 2 layers and orient the edges at the same time (HFOLS, algorithmic, ~305 algs)
4. ZBLL (algorithmic, ~493 algs)

or should we say… Orcsagonal Francisco

no offense though but it kinda just seems like a worse version of APB

 

[Sub20Soon]

I mean like this

Step 1 is 2x2x3 blockView attachment 48178
Step 2 is PAE

View attachment 48179

But the 2x2x3 block is built intutively right ? This means lookahead would be much harder since edges pieces could be in the cross piece slot.

 

[Caleb Valenzuela]

But the 2x2x3 block is built intutively right ? This means lookahead would be much harder since edges pieces could be in the cross piece slot.

i’m assuming 223 will be built like in APB (on the left), since there is a rotation after 223 and FR pair and BR edge, so you could build the 2x2x3 block like: 1x2x3 -> DFDB

 

[Sub20Soon]

i’m assuming 223 will be built like in APB (on the left), since there is a rotation after 223 and FR pair and BR edge, so you could build the 2x2x3 block like: 1x2x3 -> DFDB

Holy i need to watch a vudeo about APB and petrus and other more undergroud methods.

 

[Caleb Valenzuela]

Holy i need to watch a vudeo about APB and petrus and other more undergroud methods.

fun fact
APB is pretty much an optimized version of petrus

 

[Sub20Soon]

fun fact
APB is pretty much an optimized version of petrus

So we are optimizing an optimized method

 

[Caleb Valenzuela]

So we are optimizing an optimized method

kinda
but i don’t think it’s at it’s fullest potential
petrus is like the grandfather
APB is like the father
whatever optimizations comes after are the children
this might be my goofiest analogy yet

 

[Michael Wimberly]

I have a method idea. I’ll name it HF-O “Hexagonal Francisco (Orcuber variant)”

1. Build a 223 block
2. Solve PAE (pair and edge). PAE is solving the FR pair and the BR edge at the same time. (algorithmic)
3. Rotate so the 223 block is at the back, then for the rest of the first 2 layers and orient the edges at the same time (HFOLS, algorithmic, ~305 algs)
4. ZBLL (algorithmic, ~493 algs)

I am NAHT learning 800 algs bruv

 

[Caleb Valenzuela]

I was thinking of something:
step 1: solve 223 on the left
step 2: do a y move then solve the FL pair
step 3: solve FR pair + EO (ZBLS type)
step 4: solve ZBLL + DF edge

or something like:
step 1: solve 1x2x3 on the left
step 2: solve a 1x2x2 at BR
step 3: FR pair + EO
step 4: ZBLL + DFDB edges (probably a HUGE alg set)

but i don’t think both will work because
version 1:
cons:
requires a rotation
ZBLL+DF edge will probably add a couple hundred more algs (if i had to guess maybe the tally will be around 700 algs?
version 2:
cons:
FR pair + EO probably won’t be ergonomic considering you have DFDB unsolved. Also it will probably take a lot of algs
ZBLL + DFDB will probably result in a couple thousand algs combining that with non-matching edges and corners in the top layer for horrendous recog

TDLR: the two methods i just made are bad so learn from this guys

 

[Caleb Valenzuela]

I am NAHT learning 800 algs bruv

I mean since ZB is pretty much the most optimal method right now, the method we have to make will probably require more or less 800 algs. Even the full version of APB has around 700 algs, which is a lot (BUT most of them are easy to memorize and are quite intuitive)

 

[Martyt7777]

guys hear me out for like the 7th time

What if we find a way to solve the cube into like this position (223 block with BR 2x2 block in this position), and then finish the 1st 2 layers while solving EO at the same time, ending the cube with ZBLL? We could get extremely easy cases like U/U'/U2/∅ R', but could also make certain cases slightly harder compared to ZBLS

 

[acrystal]

I have a method idea. I’ll name it HF-O “Hexagonal Francisco (Orcuber variant)”

1. Build a 223 block
2. Solve PAE (pair and edge). PAE is solving the FR pair and the BR edge at the same time. (algorithmic)
3. Rotate so the 223 block is at the back, then for the rest of the first 2 layers and orient the edges at the same time (HFOLS, algorithmic, ~305 algs)
4. ZBLL (algorithmic, ~493 algs)

CrossPetrus said that the 2nd step would take 5951 algs, which is why i used EO+SBT

 

[CrossPetrus]

CrossPetrus said that the 2nd step would take 5951 algs, which is why i used EO+SBT

That’s if you allow the pair pieces to be anywhere. If you pair them up and then insert them, then it’s 896 algs, and I already posted the algs. I think that’s the best way to go, and then I think we should just blockbuild the front and do zbll. Yes, it would take 1,389 algs, but it be better than having wv and pll, and should be a pretty efficient method.

 

[acrystal]

Here are the eopair algs. There are 896 cases and the algs average 7.59 stm.

https://docs.google.com/spreadsheets/d/1BVRZaAykXFQ4UKC8O7uks14n_LOoSsR5/edit?usp=drivesdk&ouid=100242630063312859715&rtpof=true&sd=true

oh thx for the algs, but can you explain what the algs are for btw can can you explain why 896?