Not all of them are (I was referring to the EO case, not that specific LSE case), and also I don't use misoriented centres.

yeah, let me see what the average actually is without misorientated centers or any tricks, my math is probably wrong:

(eo skip): 1 case that takes 0 moves
(6 flip): 1 case that takes 11 moves
(2 flip): 12 cases that take 7 moves, 3 cases that take 8 moves
(4 fliip): 2 cases that take 3 moves, 6 cases that take 4 moves, 2 cases that take 7 moves, 1 case that takes 8 moves, 4 cases that take 5 moves

average = (0+11+84+24+6+24+14+8+20)/32 = 5.97 moves
 
Just a thorght, has anyone ever gone F2B, Cls, CP+EO, lse? It could be cool. Don't know if there's and alg set yet tho.

Some cases just aren't worth the recognition and then CP recognition because they aren't faster than CMLL algs even if they are 2 Gen (I did force a CMLL skip one time with that method though lel)
 
yeah, let me see what the average actually is without misorientated centers or any tricks, my math is probably wrong:

(eo skip): 1 case that takes 0 moves
(6 flip): 1 case that takes 11 moves
(2 flip): 12 cases that take 7 moves, 3 cases that take 8 moves
(4 fliip): 2 cases that take 3 moves, 6 cases that take 4 moves, 2 cases that take 7 moves, 1 case that takes 8 moves, 4 cases that take 5 moves

average = (0+11+84+24+6+24+14+8+20)/32 = 5.97 moves
Interesting, that's lower than I expected. I'm starting to think my LSE is inefficient now...
 
So, I said I was done with Roux, but I never really knew how to practice. I would just solve with it, and do slow solves. I never really improved. Never thought about BLD solving the FB or anything like that. So, that being said, how did you guys practice your F2B because my splits are around 12- 8- 5-7 (seconds) Move-count is about 20-23-14-20
 
Sure. Now, these weren't speedsolves, but solves where I went slow, so I could count the moves, so they are fairly lower than normal, but...
Scramble:U' F2 U' L2 B2 U' F2 D' F2 D U' R' U' B U2 F2 U' B2 F' U F

FB: y' U L' U M' L U2 F' R' U' R2 U B2

SB: r' U' M' R2 U2 r' U' R U M' U'M U2 r U R'

CMLL:U L'U' L U' L' U2 L

EO:U2 M U2 M' U M

LR: M U2 M U2 M2 U'

M-Slice: U' M E2 M' E2
 
I was about to ask if anyone uses CP EO, because I do! If you want algs that's just OLLCP-A, you dont need more!
 
So, I said I was done with Roux, but I never really knew how to practice. I would just solve with it, and do slow solves. I never really improved. Never thought about BLD solving the FB or anything like that. So, that being said, how did you guys practice your F2B because my splits are around 12- 8- 5-7 (seconds) Move-count is about 20-23-14-20

work on your first block, decrease the movecount to be less than 12 on average and around 6 seconds. believe it or not, if you can do one first block, the average movecount for it is 7 moves.
 
Sure. Now, these weren't speedsolves, but solves where I went slow, so I could count the moves, so they are fairly lower than normal, but...
Scramble:U' F2 U' L2 B2 U' F2 D' F2 D U' R' U' B U2 F2 U' B2 F' U F

FB: y' U L' U M' L U2 F' R' U' R2 U B2

SB: r' U' M' R2 U2 r' U' R U M' U'M U2 r U R'

CMLL:U L'U' L U' L' U2 L

EO:U2 M U2 M' U M

LR: M U2 M U2 M2 U'

M-Slice: U' M E2 M' E2

FB: F' sets up the first pair r' F' inserts it B' M B' inserts the last pair.
 
I was only going to say stuff about FB but then forgot, sorry :p
Sure. Now, these weren't speedsolves, but solves where I went slow, so I could count the moves, so they are fairly lower than normal, but...
Scramble:U' F2 U' L2 B2 U' F2 D' F2 D U' R' U' B U2 F2 U' B2 F' U F

FB: y' U L' U M' L U2 F' R' U' R2 U B2
y' U L' U M' L U2 F' could be solved like this:
F' // setup pair
r' F' // insert pair
or maybe like this:
U R' U2 // pair corner+edge
F2 // insert pair

R' U' R2 U B2 is good for that pair. It's not a great case.

SB: r' U' M' R2 U2 r' U' R U M' U'M U2 r U R'
r' U' M' R2 U2 r' U' R can be done like this:
r' U' M' F R2 F'
or r' U' M' F R F' R

U M' U'M U2 r U R'
I would finish with r' instead of R to keep the centres oriented, but it doesn't really matter, since you can fix it during CMLL too.

EO:U2 M U2 M' U M
You could've solved UL and UR at the same time as EO here! If you track where they go, you can do U2 M U2 M' U' M', which coincidentally skips EP too.

LR: M U2 M U2 M2 U'
You could solve this ULUR case with M' U2 M'.


Most of them are small things that won't make much difference for now (like LSE tricks), but your first square was a bit inefficient. Try to look for moves that aren't doing anything - for example, if you insert a pair with L' U L, the last L move isn't solving any new pieces, so you could just do r' F instead.
 
Do you guys have any tips for improving look ahead? A good 4-5 seconds of my solve time is taken up by looking for pieces, and when I see everything and I don't take that time, I normally get a sub 20 (I average about 24).
 
Do you guys have any tips for improving look ahead? A good 4-5 seconds of my solve time is taken up by looking for pieces, and when I see everything and I don't take that time, I normally get a sub 20 (I average about 24).
Slow turning is good, start at like 3 tps with no pauses and slowly increase.
 
Do you guys have any tips for improving look ahead? A good 4-5 seconds of my solve time is taken up by looking for pieces, and when I see everything and I don't take that time, I normally get a sub 20 (I average about 24).
so to lookahead, you gotta use prediction, which is like if you instantly knew how to solve second block square, you could also look at where the last corner-edge pieces are and by using your knowledge of the moves needed to complete the square, you predict what corner-edge pair case you will have once the square is done. using that method you could basically one look second block. but, i dont know anyone with a recognition game so strong. so what you would do is look for the corner edge pieces while slowly executing your square solution and then as soon as you see them you can predict and speed up until your second block is pretty much done. you should always slow down toward the end of each step / alg execution because it will give some time to look ahead the next one, and to adjust to the new state of the cube so youre not rushed for recognition and liable to make an error in that panicked state.

you also would do piece tracking at times in the solve because you will rarely see all the needed pieces at once, and you wont always be able to predict a really long way in the future. like when youre solving the first block you can one look it in inspection + predict the placement of a second block edge, then use your first block execution time to look for the other pieces needed to complete the square. once youve located the needed pieces and youve tracked them to a point where you can predict their placement after first block, then you can proceed with the second block completion as i described before. (idk why i explained it in this order, but whatever)

here is another great tactic (which i often forgo during second block in favour of cube tilting because im noobular), using the information available to you so that you can deduce the location of another piece. so say that you have a 4flip and the ULUR colour is red-orange/white; you see that one of the flipped pieces in U is red/white, and that the other is green/white. while finishing your cmll alg, you slowed down and were able to see both colours on an unflipped edge in U. that edge was white/blue. you see the U/D colour of the other unflipped edge and it is yellow, so it doesnt matter that you cant see the other colour because it could not possibly be the orange/white ulur piece. so at this point you know 100% that the orange/white ulur piece must be at DF or DB. you look to DF and see the the flipped edge there is yellow. since the orange/white piece does not have yellow on it, and since you are only able to see 3/4 white pieces, you deduce that the other ulur piece is in DB without having to tilt the cube. now you can orient edges while influencing ulur positioning, or simply predict the moves needed to solve them once you orient edges. some real sherlock holmes type stuff.

yayyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy~


Slow turning is good, start at like 3 tps with no pauses and slowly increase.


owao. thats not even that slow. a 24 second roux solver would have like 2.25 tps. calculated by guessing he uses 54 moves to solve. i have no what i should actually expect from someone his speed, but my speedsolves are 50stm so i just bumped that up a bit.
 
Last edited:
owao. thats not even that slow. a 24 second roux solver would have like 2.25 tps. calculated by guessing he uses 54 moves to solve. i have no what i should actually expect from someone his speed, but my speedsolves are 50stm so i just bumped that up a bit.
Yes, I have a sub-20 Ao5 with 2.67 average TPS. 3 TPS is definitely too fast for starting slow turning. 1.5-2 TPS at first would be better imo.
 
Last edited:
Back
Top