That can't be right. If I do the alg twice I end up with 4 unsolved centers.

What one do you 4blder use?

it IS right and it switches centers indeed
that is what the r2 at the start is for (in case of parity it solves centers)

Are you performing it on a solved cube?
then you are r2 and 4 centers off...
Just keep repeating it :)
 
That can't be right. If I do the alg twice I end up with 4 unsolved centers.

What one do you 4blder use?

I suppose you solve edges using simple r2 method. If you have done an odd number of "shootings" then you have centers on r-layer swapped (right slice if r2 away from solved, except UBr and DFr edges are on their places). First you do r2, and your centers are back, but UBr and DFr are swapped now. Then you do D' L' F ( l' U2 l' U2 F2 l' F2 r U2 r' U2 l2) F' L D, swapping them, and the entire cube is solved now.

Did you try to do a sighted solve?
 
I suppose you solve edges using simple r2 method. If you have done an odd number of "shootings" then you have centers on r-layer swapped (right slice if r2 away from solved, except UBr and DFr edges are on their places). First you do r2, and your centers are back, but UBr and DFr are swapped now. Then you do D' L' F ( l' U2 l' U2 F2 l' F2 r U2 r' U2 l2) F' L D, swapping them, and the entire cube is solved now.

Did you try to do a sighted solve?

Do a sighted solve. It works.
 
Did you try to do a sighted solve?

Well I haven't done any full attempts yet but I will do some sighted ones. I want to do 3-cycles but I also want to understand r2.

Also I have another question, my centers memo is around 2:30 and my corners memo is 30-45 but my edges memo is around 10:00, my question is how can I improve my edge memo time?

For 3x3 my edge memo is around 30-45.
 
Also I have another question, my centers memo is around 2:30 and my corners memo is 30-45 but my edges memo is around 10:00, my question is how can I improve my edge memo time?

Why is your memo so slow? Do you determine where which piece goes slowly, or do you recall your lettering system slowly, or do you memorize 12 words slowly, or do you review your memo often? Find the answer and train that part.
 
Can someone with 20ish execution (Porky) post their corners/edges splits for execution. I'm at about 12-15 for corners and 15-18 for edges, and I want to know what to work towards.
 
Hey guys, i have a question,

I'm thinking about this:

I made up one name for each of the 18 cases for TuRBo (corners). Case number 18 for example is a fish. So i'm thinking about writing down that for lets say 20 cases its the case "fish" and so on. I have a list on my computer for every corner case, so i can practise my image system. Now i could just add the case, next to the image. So i could practise the image + the case.
I wouldnt have to write down the setups, because they are easy, i would just take the shortest setups and thats it.

eg.

pieces-------image-------case

DRB-FUL------box-----(9-)marathon

I think its a bit like BH because i read something about names for the cases, so you dont have to memorize all the algorithms.
Is it a good idea to do it like that or is it better to learn BH then? Because it would be hard to switch afterwards.
I wouldnt like to switch, just because it might me 1 move less for every case in BH. I have 1.9 setup moves in average in TuRBo. I just want to make sure, that i wont do any mistake, BEFORE writing down/learning all this..

Greetings, Dennis
 
Hey guys, i have a question,

I'm thinking about this:

I made up one name for each of the 18 cases for TuRBo (corners). Case number 18 for example is a fish. So i'm thinking about writing down that for lets say 20 cases its the case "fish" and so on. I have a list on my computer for every corner case, so i can practise my image system. Now i could just add the case, next to the image. So i could practise the image + the case.
I wouldnt have to write down the setups, because they are easy, i would just take the shortest setups and thats it.

eg.

pieces-------image-------case

DRB-FUL------box-----(9-)marathon

I think its a bit like BH because i read something about names for the cases, so you dont have to memorize all the algorithms.
Is it a good idea to do it like that or is it better to learn BH then? Because it would be hard to switch afterwards.
I wouldnt like to switch, just because it might me 1 move less for every case in BH. I have 1.9 setup moves in average in TuRBo. I just want to make sure, that i wont do any mistake, BEFORE writing down/learning all this..

Greetings, Dennis

To me this sounds like just as much work as learning BH. Have you attempted to learn commutators yet?

Also, I think when you said names for all the cases, you were referring to how some people have an image for every letter pair, and every letter pair refers to a BH cycle.
 
To me this sounds like just as much work as learning BH. Have you attempted to learn commutators yet?

It would be one day of work. Its not a lot. Learning BH would take more than one day i guess. AND i already know the 18 algorithms for TuRBo, so i wouldnt have to do this anymore.
I watched some videos about commutators here in the forum and i didnt really get into it. I guess i would understand it, if i would meet someone at a competition who would just show me some cases in front of me.

Also, I think when you said names for all the cases, you were referring to how some people have an image for every letter pair, and every letter pair refers to a BH cycle.

I have one image for every pair of corners and and one image for every pair of edges. I know them perfectly.
440 images for the edges and 378 images for the corners. So dont get me wrong. I wouldnt have to learn these.
I would just add the case-name next to all the images that i already know. And the case would belong to an algorithm that i already know. Its just learning the case name/image thing. You know?

Btw: I need 12.1 (or LESS) total moves in average to solve 2 corners with TuRBo. So its not that much more than BH i guess?
But i dont USE TuRBo yet. Thats why i want to know all this, BEFORE switching totally..

Greetings, Dennis
 
Last edited:
Sounds like you're most of the way there anyway, but a lot of people don't need an intermediate step. It will pay off though since unlike most people Once you're using BH you'll have a way other than OP to solve tough cycles.
 
So you think i should just go for it?
BH for corners takes about 10 moves in average to solve 2 corners i think, right?
And i would need about 12 moves. So i would need about 7 moves more in average
and i dont know, if i should learn BH because of these 7 moves in one solve..

Dennis
 
Speaking of BH Corners:

UBL -> LFU -> UFR

Any ideas on how to handle this case with an explanation of how it works?

Not optimal and there's probably a better way, but I'd do [F: [U2, R' D' R]]

F sets it up to an 8-mover, U2 interchange, R' D' R insertion.
 
Last edited:
Another interesting but definitely non-optimal solution to ULB > LUF > URF is [F, L' U2 L U2 L]

I would do F [U2, R' D' R] F' though.

EDIT: Or you can do x' U2 [R2, U' L2 U] U2 = x' U2 R2 U' L2 U R2 U' L2 U', which is optimal HTM.
EDIT2: DrKorbin already posted that.
 
Last edited:
So you think i should just go for it?
BH for corners takes about 10 moves in average to solve 2 corners i think, right?
And i would need about 12 moves. So i would need about 7 moves more in average
and i dont know, if i should learn BH because of these 7 moves in one solve..

Dennis
TuRbo is a convenient trick to use with BH. Please try to learn comms. When I started turbo, I was still getting used to a memo system that didn't use numbers. You are way past that. I never knew OP, so Turbo was my fallback on BH comms I didn't understand. If you want to make a list case by case, try to think of it more like getting stuff in the TuRBo frame. Actually, I could make that for you, but think about trying comms because that is the best way to optimize your corners.
 
Back
Top