rowehessler
Veteran
- Joined
- Nov 25, 2007
- Messages
- 877
the third most choice is 6+....highly doubt that
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.
mines usually 8 seconds, and i turn under 7 tps...
Don't you count rotations as a move though? I don't think most people do.I think you're underestimating yourself haha. I reach mid 7 pretty frequently, and I have no doubt you beat that often.
Don't you count rotations as a move though? I don't think most people do.
Even without ETM I still end up in the low to mid 7 range cuz I don't rotate much. It's pretty bad.
Oh... I've always thought ETM didn't include rotations :fp Do you have any reconstructions of your solves? Do you know what your average movecount for F2L is? I guess you know 2lLL, so if your movecount is so high it's probably because of something in F2L.Even without ETM I still end up in the low to mid 7 range cuz I don't rotate much. It's pretty bad.
You can ask Chris Olson if you don't believe me. I wouldn't be surprised if my average movecount is above 70.i highly doubt that, your move count would probably have to be in the 70s; its probably in the 60s.
Nope, ETM counts rotations. It also counts things like not double flicking U2s, because honestly that IS two turns. Counting it as one is stupid. I have a couple sub 10 averages uploaded that I might reconstruct today.. Depends on my level of laziness. But then again because they're sub 10, they may have been more efficient ones. Idk. I'll go reconstruct one and post them here.Oh... I've always thought ETM didn't include rotations :fp Do you have any reconstructions of your solves? Do you know what your average movecount for F2L is? I guess you know 2lLL, so if your movecount is so high it's probably because of something in F2L.
Yeah, I just checked on the wiki... imo there should be a metric like ETM but that doesn't count rotations. Because that's what I always useNope, ETM counts rotations. It also counts things like not double flicking U2s, because honestly that IS two turns. Counting it as one is stupid. I have a couple sub 10 averages uploaded that I might reconstruct today.. Depends on my level of laziness. But then again because they're sub 10, they may have been more efficient ones. Idk. I'll go reconstruct one and post them here.
Yeah, I just checked on the wiki... imo there should be a metric like ETM but that doesn't count rotations. Because that's what I always use
I didn't mean you had to reconstruct all your solves! I just wanted to see if there were any you'd already reconstructed so I could try to find any inefficient parts. Btw, how do you slow down the video to reconstruct? I don't know how to...
That's cool...2. youtubeslow.com lets you go to ¼ speed, which is usually good.
F2 L U B2 D2 L' D R2 F' R' D2 L2 D2 R' U2 D2 L' U2 B2
y // inspection
U L U L y' U' R' y' U' R' F R // Xcross
U' L' U U L U' L' U L // 2nd pair doubleflick U2
U' R U' R' U2 R U' R' // 3rd pair D2 L U2 L' D2
y' U U y' U2 y' R' U' R U' U' R' U R // 4th pair wtf even is that
R2 D R' U2 R D' R' U2 R' // OLL 2-gen! The COLL cases are easy to learn for this case; three of them are variants of this, one is R' or F, Y perm, R or F' and one is front sune-back sune. This is that last one. I just do F sexy F' then ELL for the other...
U U' f R f' R2 u' R U' R' U R' u R2 // PLL 2-sided PLL recog could help eliminate unnecessary AUFs
That's cool...
I've just seen you've done one reconstruction already.
I could probably find a better X-cross for the first (or second) solve, but I'm tired atm. There were two very inefficient F2L cases I found, one in each solve; as I said if you don't like what I've suggested the wiki contains several algs for each case.L2 F D2 B' U2 B D2 F D2 F2 D' B' F' R' D' U' F D2 B' D2
z2 // inspection
L' U' D' R' F U' U' y U' L' U L U y2 L F' L' // Xcross I'd do it as cross preserving pair, U' R' F D U L' D' L' y' R' U R. Remember D moves can be useful when making crosses.
U' y' R' U' R // 2nd pair That's such an inefficient way to insert that pair
L' U U L U' L' U L // 3rd pair U2 is better than U U
R U' R' U y' R' U2 R U' U' R' U R // 4th pair Learn a better way to solve this pair e.g. R2' U2' F R2 F' U2' R' U R' or U2 r R U R' U' r' U2 R U R U' R2' (the U2 orientes the LL edge). Alternatively, try to avoid this case by removing the pair from the slot as you set up another F2L case, before the three move insertion. If there are cases you have trouble with, look at the wiki for an alg that you like (for example I didn't like case 31, so I found R U' l U' R' U l', which I really liked when executed as l F' R U' R' U l'. It went from being one of my slowest cases to my fastest except for the three movers.
U' r' U' R U' R' U2 r // OLL
U L' U' L F L' U' L U L F' L2 U L U2 // PLLU2 B2 F2 U' F2 U' B2 U2 L2 D' L2 R F U2 R' B U L' D L' R'
x2 // inspection
R D F R U' B2 // cross
U' U' U' y L' U L // 1st pair Practise cross to F2L transition by doing blind cross etc. You don't want to have to do three U moves and then a rotation straight after the cross.
R U' R' U' y R' U R // 2nd pair
U' L' U L U' U' y L U L' // 3rd pair
L' U L U' L' U U L U' U' L' U L // 4th pair U L' U L U' L' U' L
U' l' U' l L' U' L U l' U l // OLL
U U' R' U L' U2 R U' R' U2 R L U // PLL Again, practise 2-sided PLL recog, especially for easy cases such as this.
I could probably find a better X-cross for the first (or second) solve, but I'm tired atm. There were two very inefficient F2L cases I found, one in each solve; as I said if you don't like what I've suggested the wiki contains several algs for each case.
Yeah, I used to be like that. I didn't learn F2L from a tutorial (which was a stupid thing to do, it took forever...), so although most (90%) of my cases were what most people use anyway, there were some ones that were awful (R U2 R' U2 R U R'; L' U' L U2 y' R U' R'; R U R' U2 R U2 R' d R' U' R and probably a few more). If you're inefficient with intuitive F2L, learn some algs and it should help with efficiency/speed.Thank you! The sad thing is that this is more efficient than normal![]()