Varying Times

thelurch1986

Regular
Joined
Mar 23, 2009
Messages
49
Location
Florida
I did 15 solves in a row and while some of the times are roughly the same, a lot of them vary, and some drastically.. is this a sign that I am slowly working towards the faster times and every once in a while I still get a slower time? Or does this mean that I am getting lucky and I am really a slower solver?

Cross F2L LL Total
Solve One: 5.54 26.13 12.34 44.01
Solve Two: 7.10 19.12 21.82 48.04
Solve Three: 6.18 25.68 22.28 54.14
Solve Four: 4.79 22.79 16.93 44.51
Solve Five: 10.46 27.40 10.85 48.71
Solve Six: 4.50 20.24 16.43 41.17
Solve Seven: 6.67 15.71 16.64 39.02
Solve Eight: 6.92 22.51 14.56 43.99
Solve Nine: 4.51 23.24 14.01 41.76
Solve Ten: 11.01 18.84 19.74 49.59
Solve Eleven: 4.96 25.48 17.20 47.64
Solve Twelve: 9.31 24.06 16.12 49.49
Solve Thirteen: 9.81 22.99 20.32 53.12
Solve Fourteen: 6.65 20.43 17.14 44.22
Solve Fifteen: 9.26 20.96 14.12 44.34

Cross Avg F2L Avg LL Avg Total Avg
7.18 22.37 16.70 46.25
 
Sorry it pasted without the spacing, first number is cross, then F2L, then LL, then Full time. At the bottom is the average of each step for all 15 solves.
 
inconsistency is probably caused by the fact that you don't know a lot of LLs, but mainly that you're not looking ahead in F2L
 
I actually do use 2 Look OLL and PLL. Definately on the look ahead, I am trying to work on it but currently having problems using it effectively, should I go for 2 Look Last Layer already?
 
NOOOOOOO!!!!!!!!!! 2LLL is not needed yet. Well, you could start working on your PLLs but don't do them all at once. When you look ahead slow your turning down so you never stop turning. and go to youtube and search badmephisto f2l. i'm assuming you haven't watched his videos if your asking this stuff.
 
I wouldn't go for two-look last layer just yet. For now you should just practice cross and F2L. Try to look ahead (understand your F2L cases well enough that you can try to find the next couple pieces while you are solving the current pair) and work on your turnspeed. In particular you might want to learn and practice fingertricks (doing two or more moves in a tiny fraction of a second). Four-look last layer can get well under ten seconds - learning two-look last layer is quite a hassle, and you definitely don't need it to go faster. The most important thing right now is lookahead and turnspeed, not learning tons of algorithms.
 
3LLL isn't a bad option, I did that first; and I'm still not sub-20 yet (I got one average of 24.30 of 5, but ehh, I had a good day xD).

Try learning some special F2L cases that you don't know / can't figure out how to solve intuitively. It becomes infinitesimally easier to solve F2L faster knowing all the hard cases by heart; that way you can practice lookahead! :)
 
I wouldn't go for two-look last layer just yet. For now you should just practice cross and F2L. Try to look ahead (understand your F2L cases well enough that you can try to find the next couple pieces while you are solving the current pair) and work on your turnspeed. In particular you might want to learn and practice fingertricks (doing two or more moves in a tiny fraction of a second). Four-look last layer can get well under ten seconds - learning two-look last layer is quite a hassle, and you definitely don't need it to go faster. The most important thing right now is lookahead and turnspeed, not learning tons of algorithms.

Best advice here. People today don't seem to get the idea behind lookahead over algs. I see too often people who average the same times giving people advice. It makes me chuckle.
 
My times varied by a lot too until recently.. I think it's just like that when you're above 30 second average.. Since you most likely don't know full PLL at that point, and you sometimes get 3 Look OLL (FUR RUF, FRU URF, All edges OLL)..

I think once your times start to even out (Finishing full PLL helped me I think), you'll slowly progress and chip away at your times, instead of those huge time jumps you get between 30seconds and 1min+ (50sec average and 42second solve out of nowhere, then 45 second average 2 days later for example)
 
Back
Top