kinch2002
Premium Member
My order is
Memo:
+ centres
x centres
wings
middle edges
corners
Execute:
corners
+ centres
x centres
wings
edge parity
middle edges
corner parity
So I basically execute in the same order as I memo apart from corners. I find I don't have much problem recalling any particular set any more than the others, because they're all being memoed for the same amount of time. I've been thinking about switching some stuff to be backwards so that it will be fairly short term - possibly making middle edge execution straight after corners, but I think I'd then get problems with non-centre-safe algs (for m-slice pieces). As it is, I'm happy enough.
I have a bigcubebld-related question too...I use r2 for wings, and do the really slow way of doing the l-slice wings (moving to UBl using l-slice, then flipping the edge using B' U R' B U', r2, flip edge back, then undo first move). I hate doing this because I can't even turn the algs fast and I'm sure they're extremely inefficient. Is there any way of doing these pieces (presumably paired with the next/previous piece) without using on-the-fly comms?
Memo:
+ centres
x centres
wings
middle edges
corners
Execute:
corners
+ centres
x centres
wings
edge parity
middle edges
corner parity
So I basically execute in the same order as I memo apart from corners. I find I don't have much problem recalling any particular set any more than the others, because they're all being memoed for the same amount of time. I've been thinking about switching some stuff to be backwards so that it will be fairly short term - possibly making middle edge execution straight after corners, but I think I'd then get problems with non-centre-safe algs (for m-slice pieces). As it is, I'm happy enough.
I have a bigcubebld-related question too...I use r2 for wings, and do the really slow way of doing the l-slice wings (moving to UBl using l-slice, then flipping the edge using B' U R' B U', r2, flip edge back, then undo first move). I hate doing this because I can't even turn the algs fast and I'm sure they're extremely inefficient. Is there any way of doing these pieces (presumably paired with the next/previous piece) without using on-the-fly comms?
