Divineskulls
Veteran
Improving slowly but surely. I have a sub-15 Ao100, but I suck at getting good averages on film. Oh well. Tips would be very much appreciated. :3
Last edited by a moderator:
[Unofficial] 15.09 3x3 Average of 5- Nick Rech
- Thread starter Divineskulls
- Start date
Improving slowly but surely. I have a sub-15 Ao100, but I suck at getting good averages on film. Oh well. Tips would be very much appreciated. :3
cyoubx
Veteran
You turn really fast o.O
Nice solves, but you seem to do a lot of extraneous U/U's.
Nice solves, but you seem to do a lot of extraneous U/U's.
Divineskulls
Veteran
Lol, thank you, I suppose! xD I do need to work a bit on lookahead at this speed.
And yeah, I think that goes along with the lookahead, not being able to see the next pair fast enough.
cyoubx
Veteran
Yeah, you could achieve the same times with something like 4tps
I'm not great at lookahead either, though.
Try this:
Do solves where you have your eyes closed during the cross, then open them and look for the first pair. Close your eyes and solve the pair, open and look for the second, etc., then do your LL normally. See if your times are much slower. If you're looking ahead while turning at all, they should be slower because you have your eyes closed. If your times are about the same, then that means you're barely looking ahead at all.
Being good at looking ahead and being good and finding the next pair are separate things. Being really good at looking ahead means you are starting to look for the next pair the moment you start solving the current one. Being really good at finding the next pair means as soon as you start looking, you see it.
So, two scenarios:
1. Really good look ahead, terrible at finding the pair. This can result in huge pauses between pairs, even with really good look ahead. The "looking ahead" happens as soon as the current pair solve is started, but it takes longer to find the next pair than it takes to solve the current one due to poor ability to find the next pair.
2. Really good pair finding, terrible look ahead. This can actually result much shorter pauses, because even though the look ahead only starts when the current pair is complete, the next pair is found immediately.
I think scenario two is the one that most people naturally end up with. This is because no ones starts CFOP with knowledge of every F2L case, and therefore needs to watch and think about it as they're doing them. Then, they look for the next pair. So, not only does the habit of focusing on your current pair become very strong, but they're only practicing pair finding when the cube isn't turning. I say habit because even once a person is able to not have to focus on the current pair, they will still tend to.
My tip now would be that, since you are clearly at a point where your hands just know how to solve each case, do a lot of solves with this process:
1. Inspect cross, look for a corner edge pair to follow.
2. Start solve and track the pair trying to focus on them as much as possible, and on your cross solve as little as possible.
3. As soon as your cross is done and you see where the corner and edge ended up, take note of the color of the pair (the two side colors) and where it's slot is.
4. Close your eyes and "feel" the muscle memory, which you clearly have with that TPS (but go slower!).
5. Open your eyes and, as soon as you do, start doing what you "felt" in your head, while focusing 100% on looking for another corner and edge pair.
6+. Repeat the process for each pair, including the fourth while looking ahead to the OLL as it forms. Do the same for OLL -> PLL if you can do two sided PLL recognition.
The idea behind the process is that you are forcing yourself look ahead while the cube is turning, so you gain practice in finding the pair while it's turning, but you also get yourself into the good habit of "feeling" the next muscle memory instead of focusing on it.
I was talking in a tone of fact, but it's all just my opinion and experience of course. Let us know how it works out if you decide to try it.
Do solves where you have your eyes closed during the cross, then open them and look for the first pair. Close your eyes and solve the pair, open and look for the second, etc., then do your LL normally. See if your times are much slower. If you're looking ahead while turning at all, they should be slower because you have your eyes closed. If your times are about the same, then that means you're barely looking ahead at all.
Being good at looking ahead and being good and finding the next pair are separate things. Being really good at looking ahead means you are starting to look for the next pair the moment you start solving the current one. Being really good at finding the next pair means as soon as you start looking, you see it.
So, two scenarios:
1. Really good look ahead, terrible at finding the pair. This can result in huge pauses between pairs, even with really good look ahead. The "looking ahead" happens as soon as the current pair solve is started, but it takes longer to find the next pair than it takes to solve the current one due to poor ability to find the next pair.
2. Really good pair finding, terrible look ahead. This can actually result much shorter pauses, because even though the look ahead only starts when the current pair is complete, the next pair is found immediately.
I think scenario two is the one that most people naturally end up with. This is because no ones starts CFOP with knowledge of every F2L case, and therefore needs to watch and think about it as they're doing them. Then, they look for the next pair. So, not only does the habit of focusing on your current pair become very strong, but they're only practicing pair finding when the cube isn't turning. I say habit because even once a person is able to not have to focus on the current pair, they will still tend to.
My tip now would be that, since you are clearly at a point where your hands just know how to solve each case, do a lot of solves with this process:
1. Inspect cross, look for a corner edge pair to follow.
2. Start solve and track the pair trying to focus on them as much as possible, and on your cross solve as little as possible.
3. As soon as your cross is done and you see where the corner and edge ended up, take note of the color of the pair (the two side colors) and where it's slot is.
4. Close your eyes and "feel" the muscle memory, which you clearly have with that TPS (but go slower!).
5. Open your eyes and, as soon as you do, start doing what you "felt" in your head, while focusing 100% on looking for another corner and edge pair.
6+. Repeat the process for each pair, including the fourth while looking ahead to the OLL as it forms. Do the same for OLL -> PLL if you can do two sided PLL recognition.
The idea behind the process is that you are forcing yourself look ahead while the cube is turning, so you gain practice in finding the pair while it's turning, but you also get yourself into the good habit of "feeling" the next muscle memory instead of focusing on it.
I was talking in a tone of fact, but it's all just my opinion and experience of course. Let us know how it works out if you decide to try it.
Divineskulls
Veteran
Awesome, thank you for taking so much time on your post, I really appreciate it! I will definitely work on your process, it seems like it will help my lookahead AND pair finding a lot! 
Brest
Moderator
[youtubehd]aIZ7yhi6NhE[/youtubehd]
D2 R2 B2 L2 R' B F U' F2 U R' F2 R' U2 R D' B' R
y' // inspection
r' U' R F' U x' R2 L2' // cross
y2' R U' R' U y' U R' U' R R' R U' R' U R // 1st pair
y2' U' R U2' R' U2 R U' R' // 2nd pair
y U U2' (R U R' U')2 d' L' U L // 3rd pair
U3' x R' U U' R R' U R U' x' R U' R' // 4th pair
U' r U R' U R U' r' r U' r' // OLL
U U' (y x) R' U R' D2 R U' R' D2 R2 // PLL
View at alg.garron.us
y' // inspection
r' U' R F' U x' R2 L2' // cross
y2' R U' R' U y' U R' U' R R' R U' R' U R // 1st pair
y2' U' R U2' R' U2 R U' R' // 2nd pair
y U U2' (R U R' U')2 d' L' U L // 3rd pair
U3' x R' U U' R R' U R U' x' R U' R' // 4th pair
U' r U R' U R U' r' r U' r' // OLL
U U' (y x) R' U R' D2 R U' R' D2 R2 // PLL
View at alg.garron.us
Code:
[B]Step Time STM stps ETM etps[/B]
[COLOR="red"]Total 15.44 76 4.92 94 6.09 [/COLOR]
Cross+1 4.64 20 4.31 25 5.39
F2L 10.90 54 4.95 69 6.33
LL 4.54 22 4.85 25 5.51
[B][SIZE="4"]%[/SIZE]
Step Time STM ETM[/B]
Cross+1/F2L 43% 37% 36%
F2L/Total 71% 71% 73%D' F2 L2 B' D' U2 F2 U L D2 B L D B R' D F B2
y x' // inspection
U l U y2' R' U l' U2 x' // cross
U2' R' U R // 1st pair
R U' R' U R U2' R' U R U' R' // 2nd pair
y' U y' U' x R' U R U' x' R U' R' // 3rd pair
y U (R U R' U')2 R U R' // 4th pair
U' r' U r2 U' r2' U' r2 U r' // OLL
U3 R R2' U' R2 U R U R' U' R U R2 U' U R' U' R U' R' U2 // PLL
View at alg.garron.us
y x' // inspection
U l U y2' R' U l' U2 x' // cross
U2' R' U R // 1st pair
R U' R' U R U2' R' U R U' R' // 2nd pair
y' U y' U' x R' U R U' x' R U' R' // 3rd pair
y U (R U R' U')2 R U R' // 4th pair
U' r' U r2 U' r2' U' r2 U r' // OLL
U3 R R2' U' R2 U R U R' U' R U R2 U' U R' U' R U' R' U2 // PLL
View at alg.garron.us
Code:
[B]Step Time STM stps ETM etps[/B]
[COLOR="red"]Total 14.71 74 5.03 86 5.85 [/COLOR]
Cross+1 3.21 11 3.43 15 4.67
F2L 8.15 43 5.28 52 6.38
LL 6.56 31 4.73 34 5.18
[B][SIZE="4"]%[/SIZE]
Step Time STM ETM[/B]
Cross+1/F2L 39% 26% 29%
F2L/Total 55% 58% 60%F2 R2 U2 B L' B L' F R2 D' F2 R2 D' B' U' B2 L'
y x2 // inspection
U' L' y' R2' D2 // cross
U3' L' U L R' U2 R d' L' U L // 1st pair
U y d' U' R U R' U R U R' U' d' L' U L // 2nd pair
y2' (U' R U R')3 // 3rd pair
y' U R U R' U' R U R' // 4th pair
U2' l' U l U l' U' l y' R U' R' // OLL
U R U' R U R U R U' R' U' R2 // PLL
View at alg.garron.us
y x2 // inspection
U' L' y' R2' D2 // cross
U3' L' U L R' U2 R d' L' U L // 1st pair
U y d' U' R U R' U R U R' U' d' L' U L // 2nd pair
y2' (U' R U R')3 // 3rd pair
y' U R U R' U' R U R' // 4th pair
U2' l' U l U l' U' l y' R U' R' // OLL
U R U' R U R U R U' R' U' R2 // PLL
View at alg.garron.us
Code:
[B]Step Time STM stps ETM etps[/B]
[COLOR="red"]Total 14.28 72 5.04 82 5.74 [/COLOR]
Cross+1 4.47 14 3.13 18 4.03
F2L 9.31 49 5.26 57 6.12
LL 4.97 23 4.63 25 5.03
[B][SIZE="4"]%[/SIZE]
Step Time STM ETM[/B]
Cross+1/F2L 48% 29% 32%
F2L/Total 65% 68% 70%B U2 B L' R2 D' B2 D' L F R U' L2 U2 B' D' F R'
z2 // inspection
U' r U' r' R' U L2' // cross
y' R U R' U' (U' R U R')2 // 1st pair
U' y' R' F' R U R U' R' F // 2nd pair
y2' U U' R' U R U' y U' R U R' // 3rd pair
y' U y' U R' U2' R U' R' U R // 4th pair
U' r U R' U' r' F R F' // OLL
U R U' R' R U R' U' R U R' F' R U R' U' R' f (S' F) F' R2 U' R' U2 U' // PLL
View at alg.garron.us
z2 // inspection
U' r U' r' R' U L2' // cross
y' R U R' U' (U' R U R')2 // 1st pair
U' y' R' F' R U R U' R' F // 2nd pair
y2' U U' R' U R U' y U' R U R' // 3rd pair
y' U y' U R' U2' R U' R' U R // 4th pair
U' r U R' U' r' F R F' // OLL
U R U' R' R U R' U' R U R' F' R U R' U' R' f (S' F) F' R2 U' R' U2 U' // PLL
View at alg.garron.us
Code:
[B]Step Time STM stps ETM etps[/B]
[COLOR="red"]Total 16.36 81 4.95 90 5.50 [/COLOR]
Cross+1 3.09 18 5.83 20 6.47
F2L 7.92 46 5.81 55 6.94
LL 8.44 35 4.15 35 4.15
[B][SIZE="4"]%[/SIZE]
Step Time STM ETM[/B]
Cross+1/F2L 39% 39% 36%
F2L/Total 48% 57% 61%L' D2 R2 B2 D2 B L2 B' L R2 F D' R U' L' D' B' F' U
z2 // inspection
r' U' r' l U' (R' l') D2 // cross
U' U R' U R U' R' U' R // 1st pair
U R U R' U2' (R U R' U')2 // 2nd pair
y' U R U R' x (R' U R U')2 x' // 3rd pair
y' U' R U' R' U y' R' U' R // 4th pair
U' R U R' U U' U R U' R' U' x R' U R U' x' // OLL
U U' R2' u R' U R' U' R u' R2 y L' U L U2 // PLL
View at alg.garron.us
z2 // inspection
r' U' r' l U' (R' l') D2 // cross
U' U R' U R U' R' U' R // 1st pair
U R U R' U2' (R U R' U')2 // 2nd pair
y' U R U R' x (R' U R U')2 x' // 3rd pair
y' U' R U' R' U y' R' U' R // 4th pair
U' R U R' U U' U R U' R' U' x R' U R U' x' // OLL
U U' R2' u R' U R' U' R u' R2 y L' U L U2 // PLL
View at alg.garron.us
Code:
[B]Step Time STM stps ETM etps[/B]
[COLOR="red"]Total 15.11 79 5.23 88 5.82 [/COLOR]
Cross+1 4.37 16 3.66 16 3.66
F2L 9.18 49 5.34 55 5.99
LL 5.93 30 5.06 33 5.56
[B][SIZE="4"]%[/SIZE]
Step Time STM ETM[/B]
Cross+1/F2L 48% 33% 29%
F2L/Total 61% 62% 63%
Code:
Average (5/5)
[B]Step Time STM stps ETM etps[/B]
[COLOR="red"]Total 15.18 76 5.03 88 5.80 [/COLOR]
Cross+1 3.96 16 3.99 19 4.75
F2L 11.09 48 4.35 58 5.19
LL 4.09 28 6.90 30 7.44
[B][SIZE="4"]%[/SIZE]
Step Time STM ETM[/B]
Cross+1/F2L 36% 33% 33%
F2L/Total 73% 63% 65%
CoryThigpen
Premium Member
Nick, is this for real? I tried to do this in reverse and I think it is supposed to be a J-perm. Why choose such a painful alg? Try this: (R U R' F') (R U R' U') (R' F) (R2 U') (R' U')
Divineskulls
Veteran
ReconstructionThank you so much!
Haha, I do use that, I must have screwed up the first few moves and the F. xD
retep
Regular
Wow dominate, one of the most helpful posts I have read, thanks a lot!
Wow dominate, one of the most helpful posts I have read, thanks a lot!
Your signature mentions Chess and Starcraft. I play BW, not SC2, but the same applies:
You can think of the process I described as a speed solving parallel to the common Chess practice mindset of "don't move until you see it". In Starcraft and speed solving, the issue with practicing in this way is that they are real-time. Your opponent in Starcraft is not going to wait for you to think about your next move any more than the timer will in speed solving. If you hesitate while your opponent is acting on their decisions, you can lose a game of Starcraft. Even if your eventual, well thought out decision would have been better than their immediate one, they still made their move first and that is a major advantage.
When practicing Chess, it is so important to allow your mind to adjust to thinking further ahead than it's current ability. I think the usual phrase is "stretching your brain". This is something that can only happen in a real-time discipline when you remove the pressures of both time and speed to allow yourself time to think things through and grow.
For Starcraft, it is important to take note of when during the game you were unsure. Then, fast forward the replay afterward up to that point in the game and pause it. Think as much as you can about what position the game is in. What are the advantages of each player? Think about the strengths of each race, the tech paths so far, the economy, and the structure of the map as well as each player's degree of map control. What would the best course of action have been for either player at this point in the game? Of course, unlike Chess, there is fog of war in Starcraft. After you decide what the best actions would have been for you in that position, hide your opponent's vision and decide whether or not you had enough information up to that point to make that decision during the game. If not, figure out what you could have done to gain that information before the game reached that point. Very importantly, write down your findings and then play some matches to test them.
For speed solving, you have already read my other post. The basic idea is that once you have seen all the information you need for the next step (so, seeing the next corner/edge pair during F2L), you stop and think as long as you need to. This "stretches your brain" so that with enough practice it becomes trivial to see the move you need to make. Since knowing the moves isn't a big help in speed solving without being able to make them quickly, going over the muscle memory in your head to associate it with what you are about to do is crucial. All this tends to happen naturally with a lot of practice, but being more methodical avoids those bad little habits that build up, and speeds up the process greatly.
I have been applying this to guitar recently and it's kind of ridiculous how much faster I'm improving now compared to the last six few years I've been playing. I used to just sight-read the music at a speed that I could handle without mistakes, and slowly increase the speed over time until it is a decent amount beyond full speed (a bit beyond to make playing at full speed trivial).
Now, I look at the first phrase and sight read it without actually playing it, but just trying to "feel" the movements of the whole phrase and thinking about the theory side of it. Then, I play them without looking at the music and just try to ignore the physical movement while thinking only about the dynamics. This has so far resulted in very, very quick and thorough memorization of the whole piece, as well as a stronger understanding of it.
