what needs improvement?

[MYKE]

thees are my times from 5 solves

cross F2L OLL PLL
4.04 16.90 1.79 11.74
8.26 15.85 4.31 3.07
4.63 16.27 3.68 4.80
5.35 17.42 5.12 5.80
4.41 13 5.11 5.52

what is it specificly i need to improve on?

bere in mind i am currently learning all of the OLLs and have one G perm left to learn.
MYKE...

 

[Pedro]

thees are my times from 5 solves

cross F2L OLL PLL
4.04 16.90 1.79 11.74
8.26 15.85 4.31 3.07
4.63 16.27 3.68 4.80
5.35 17.42 5.12 5.80
4.41 13 5.11 5.52

what is it specificly i need to improve on?

bere in mind i am currently learning all of the OLLs and have one G perm left to learn.
MYKE...

is that right? 0.o 11 seconds?

is that F2L the 4 pairs or cross+4 pairs?

you should work on looking ahead during F2L, moving smoothly, not like 'move really fast, stop, look, move really fast, stop, look..'

and on the PLLs...top guys can do it in like 2 seconds or less...

 

[MYKE]

the F2L is with the cross already done.
yeah i'm working on looking ahead more with F2L.

yeah, it is 11 seconds, i fumbled it so much.

 

[badmephisto]

your cross doesnt look too good. Biggest improvements can be made in F2L at this point. Your OLL/PLL times will go down by themselves too. Your times appear to be quite proportional though, so it doesnt look like you have a single area where you need terrible improvement. I'd say just practice more..., its looking good

here's a question though: how did you measure individual times for all parts? I'm thinking of better ways of doing that and nothing seems to work... best thing i could think of was using my foot for the keyboard and write up a simple timer program that would make sense of that. But my foot is really clumsy and I end up pressing spacebar twice, or even 0 times instead of once... annoys me

 

[MYKE]

i did cross - stop timer - start timer - F2L - stop timer - start timer and so on... 5 times

 

[badmephisto]

i did cross - stop timer - start timer - F2L - stop timer - start timer and so on... 5 times

hmm... sounds like an ok plan... the only problem with that is that there is no flow to the solve, and the transition times, as important as they are, end up being distorted a little. I guess you have to take care to not look ahead as well, while the clock is off. I suppose that could be a temptation

 

[Pedro]

you can use the timer at rubiks.tw, it has 'break-down' option

 

[Todd]

F2L definately, the OLL an PLL are not that bad - could do with some improvement obviously but you will gain the most from F2L.

You can do a 4 or 5 second last layer and still have a bad time because of your F2L.

 

[zigzagchris]

someone should try makeing a breakdown code using a mic