Cyrus C.
Veteran
Are there any drawbacks to building the 2x2x2 & 2x2x3 at the same time, like in this scramble: L R2 F' U' R2 B' R2 B2 R' U' F2 R2 U' F2 U2 R' F' L2 U F L2 R D B2 R?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
1. Build an intuitive 2X2X2 block in as few moves as possible.
2. Expand to a 2x2x3 block intuitively.
3. Correct bad edge pairs by placing them in a specific slot and performing F' U' F
4. Complete the first two layers with only 2gen algs to preserve last layer edges.
5. Get the corners in place but not necessarily oriented with a single algorithm.
6. Use Sune as many times as needed to orient the last layer with the corners now in place.
7. Use a single algorithm as many times as needed to permute the last layer edges.
Are there more advanced or more efficent steps I could be using?
Should I look for the 2x2x2 & 2x2x3 in inspection?
Couple questions.
Do most Petrus users use 6-gen for their 2x2x2 & 2x2x3?
What method do you use for 4x4x4?
If you switched from Fridrich, do you think Petrus is better or worse for one-hand?
You should consider that OLL/PLL might actually be faster than COLL/EPLL for petrus.
You should consider that OLL/PLL might actually be faster than COLL/EPLL for petrus.
Or even better, OLL (+CP recognition)/ PLL (with CP predicted)![]()
You should consider that OLL/PLL might actually be faster than COLL/EPLL for petrus.
Or even better, OLL (+CP recognition)/ PLL (with CP predicted)![]()
Does this really help? I can't really imagine being much faster recognizing a PLL when I know that it's, say, a diagonal corner swap.
Psst. I and Im (EJF2L) are the longest (move-count) cases on average.EJF2L is nice also.