DrKorbin
Member
Ah thanks, I get it now (I forgot T-perm can do the trick)
So that means you leave BUl and FDR to the end (all the other targets are done), then you apply those algs above, right? :confused:
Yep.
Ah thanks, I get it now (I forgot T-perm can do the trick)
So that means you leave BUl and FDR to the end (all the other targets are done), then you apply those algs above, right? :confused:
When I have one solved layer (including slice layers), I take my hand off it, and just remember that all four edges on that layer have been memorised. It lets me put my fingers on more pieces, and lets me see the cube better.I'm really good at corners and use old pochmann. Get a corner sucess everytime. But edges (use m2) I have problems with, as it is hard for me to track which pieces are solved and which unsolved. The putting fingers on it method doesn't really work for me since there are more edges than fingers. Any suggestions?
I'm really good at corners and use old pochmann. Get a corner sucess everytime. But edges (use m2) I have problems with, as it is hard for me to track which pieces are solved and which unsolved. The putting fingers on it method doesn't really work for me since there are more edges than fingers. Any suggestions?
When I have one solved layer (including slice layers), I take my hand off it, and just remember that all four edges on that layer have been memorised. It lets me put my fingers on more pieces, and lets me see the cube better.
Anyway, you have 11 pieces to solve and 10 fingers, so when you get to the last one you don't need a finger on it
You can easily check if you have memoed a correct number of edge targets:
For 3x3 edges you should have 11 targets if you don't have any cycle breaks or flipped/solved pieces.
Cycle break always adds 1 target and obviously flipped/solved piece reduces one target
So take the scramble
F R2 B' R2 U2 B' U2 B' U2 F D2 R' D' F R B' L' D' R2 B2 R2
and scramble in your own solving orientation.
Now start to memo edges:
DL LU FU FR UR
after 5 targets you hit your buffer piece so thats cycle break. Lets break to UB location and continue
so UB RD BL UB
now we have another cycle break. Lets break to DB location and continue
DB RB DB end of cycle.
now we have memoed 12 targets and we had 2 cycle breaks so we should have 11+2(cycle breaks)=13 targets.
This means that we have one edge that must be either solved or flipped in its correct location. And by looking at the cube we see that this edge is FL edge
Now we have correct amount of targets because 11+2(cycle breaks)-1(flipped edge)=12
Is there a timer that records memo and execution time?
qqtimer has a "bld mode" which lets you split after finishing memo.
Hi,
I currently use letterpairs for memo, M2 edges and TuRBo Corners.
While I am really fine with memo and edges, I am sick of using TuRBo because it's the reason for approximately 95% of my DNFs.
Besides it feels slow to track the orientation of the pieces when doing the individual setup moves and undoing them correctly. I average around 0:45 for just corner execution (around 3:00-3:15 for a complete solve).
There are not many cubers who use TuRBo for corners, so I couldn't find many experiences concerning this. But this problem doesn't seem to be uncommon.
So what should I do?
Switch to Old Pochmann? This would be some kind of step backwards, but would probably make things a lot easier.
Or any other idea how to simplify or improve this?
Thanks.
to be absolutely true. Old Pochmann is by far more braindead, yet strikes a perfect balance between "algorithms" you need to learn (every single corner target with its necessary setup eventually becomes an algorithm embedded into your muscle memory) and the times you can achieve.it feels slow to track the orientation of the pieces when doing the individual setup moves and undoing them correctly.
I average around 40 seconds for corners-only memo and execution, and I've set my current official PB of 1:47.02 using M2/OP.I average around 0:45 for just corner execution (around 3:00-3:15 for a complete solve).
So after all it really comes down to practice (surprise, eh?) but OP can easily be as effective as TuRBo, whereas it is more easy to track setups, etc.
Hi Laura!
I suggest to switch to commutators or a slight modification of it. Jan made up a system which uses just one corner (I think it was DFR) and all its commutators, so 54 cases. You can easily set up each corner to to DFR/RDF/FRD with one move, do one commutator and undo the setup. As commutators are intuitive it shouldn't be that hard to come up with all the cases and imo there are no really hard ones for that corner
The TuRBo ones are useful (U perms, R U R' U' M' U R U' r'+mirrors+inverses; M' U M U2 M' U M+mirror). COLL isn't useful as it affects edge permutation. Other than those ELLs and PLL, I don't think there are many other useful alg sets to learn. Someone please correct me if I'm wrong (I'm not that good at BLD, and other people probably know more than me), but I think that's right.Can someone tell me what algorithm sets are most common in BLD? I'd like to learn the things that overlap a lot with other methods, to maximize the usefulness of my algs. I know PLLs are used some. Learning those regardless. Are COLL or ELL used much? I know 3 cycles are used, and they're a subset of ELL. Is learning full ELL useful for BLD?
The TuRBo ones are useful (U perms, R U R' U' M' U R U' r'+mirrors+inverses; M' U M U2 M' U M+mirror). COLL isn't useful as it affects edge permutation. Other than those ELLs and PLL, I don't think there are many other useful alg sets to learn. Someone please correct me if I'm wrong (I'm not that good at BLD, and other people probably know more than me), but I think that's right.