This is the F2L subset which flips and permutes edges on the E layer of a 3x3

JoshFarrell

Member
Joined
Mar 8, 2015
Messages
20
This is the JF2L subset which is obviously an F2L subset, it is split into two sections EF2L and SF2L. EF2L flips, switches and cycles edges around the E layer of the cube (F2L edges that aren't in correct position and or flipped correctly). SF2L is a subset that moves F2L pairs in the first two layers in to their correct position.

Welcome to my subset, hope you enjoy,
https://docs.google.com/spreadsheets/d/1hW4m0JmHSPKEOlBFbB2tnQN3xoWR_Y5hXgXwfS1EOiE/edit?usp=sharing

Would love some feedback! :P
 
Last edited:
So would you use this at the end of f2l to fix any edges that might have already been inserted, but with the wrong orientation/location? Or is your idea to insert all the edge pairs as simply as possible, not caring about edge orientation/location so that you could save on moves, and then just fix them at the end of f2l?

-Doug
 
So would you use this at the end of f2l to fix any edges that might have already been inserted, but with the wrong orientation/location? Or is your idea to insert all the edge pairs as simply as possible, not caring about edge orientation/location so that you could save on moves, and then just fix them at the end of f2l?

-Doug

Well the initial idea I had was to fix edges that had already been inserted and therefore it is not complete due to the rarity of some cases but now you say that I may complete it and add every case :cool:
 
I've heard of the last step of corners first method which is the same thing except it preserves LL. if yours doesn't, then its new.
 
Interesting, but what's the purpose of this?

also,
The orientaion of an E layer edge piece is determined by whether you can turn the E layer to match the piece to its coresponding F2L pair corner.
isn't a great definition imo. It would be better to define oriented as solvable with <R, U, L, D, F2, B2>, which is what most people use.
 
Great idea. Bad algs.
Happens too frequently to interesting ideas.

What programs are you using? You should work on improving the algs.
Also, there seems to some mistakes for some cases. I think fixing them should be your priority.

Good job. I hope to see this in a more polished form in the near future.
 
Quite surprised by this - a lot of the algs are good and the spreadsheet is nicely formatted too. Recognition might be a bit of a pain, but it seems like it's probably worth the effort. Maybe a bit more advice from F2L specialists and this could work.

CW switch ' z' D' M U' R2 U M' U' R2 (U D) z - rotation sucks, but it preserves your LL completely which you can begin to recognize on the L face as you execute the alg.

Case number 3 - U2 move at the start is unnecessary, unless you want to do some edge control.
 
Last edited:
Yh I know I tried to keep the algs 2/3 gen but when it came to moving 3 pieces into different places its hard not to use bad algs

Great idea. Bad algs.
Happens too frequently to interesting ideas.

What programs are you using? You should work on improving the algs.
Also, there seems to some mistakes for some cases. I think fixing them should be your priority.

Good job. I hope to see this in a more polished form in the near future.

Thank you, currently using cube explorer, and that is defiantly my priority, if you have the time I would love to know which ones need fixing.
 
Last edited by a moderator:
No, as in excluding the B face.

Oh for some of them yes, for each case I excluded certain sides to try get the best algorithms but with some, excluding the B face would mean random L and R moves one ofter each other which aren't the easiest to finger trick, so I tried to find the best algorithms which in turn would be the fastest.
 
Oh for some of them yes, for each case I excluded certain sides to try get the best algorithms but with some, excluding the B face would mean random L and R moves one ofter each other which aren't the easiest to finger trick, so I tried to find the best algorithms which in turn would be the fastest.

You could try including slice moves?

Case 3 becomes y F' M' U' R' U M U' R U F
 
Last edited:
You could try including slice moves?

Case 3 becomes y F' M' U' R' U M U' R U F

Yh thanks. Thats also one job I am planning on doing, (alternate algorithms, such as ones including M moves and so on), do you think it would be worth making algorithms that do not affect the last layer (for blindsolving)?
 
Not for blindsolving, but it will help lookahead for normal 3x3x3

So what do you think the next step for this substep is? After I have improved upon it and added multiple algorithms what do you think I should do, try get it out there more?
 
So what do you think the next step for this substep is? After I have improved upon it and added multiple algorithms what do you think I should do, try get it out there more?

If it's good enough, people will notice it. Perhaps move onto generating stuff for incorrectly slotted pairs like F' U R' U2 R U' F, I don't know, I don't practice 3x3x3.
 
Back
Top