After another year of untimed solves I tried going back to timed solves. I was definitely rusty under the 'pressure' of high TPS, and it took several weeks of timed solves to get back into the flow, but I was rewarded eventually with a single excellent session with lots of pb's.

From the same late night session:

Ao5 13.93

Ao12 14.45 PB

Ao25 15.04 PB

Ao50 15.76 PB

#solves 139

Generated By csTimer on 2019-07-16

avg of 12: 14.45

Time List:

1. 12.60 F' U' F2 U F2 U2 L2 B2 D' R2 U B2 U2 L' B2 D' L D2 U' F L

2. 13.71 L2 D' L2 D U2 B2 U' R2 B2 L2 B2 D2 F R B' D B D2 L U F

3. 17.99 R B2 R' U2 L' U' F D R' U2 R D2 R2 D2 R' D2 F2 L2 D2 F

4. 13.70 B2 L2 F' D2 F' R2 F' L2 B2 D2 F D' L R' D2 F2 R F2 D R U

5. 15.12 B R B2 L' F2 R2 U2 R' B2 R' F2 B' R U B2 R2 D2 U R

6. 15.53 U2 F R' D' L2 B2 D2 R2 D' B2 D L2 F2 U' R' B L R B2 R2 D'

7. 14.11 B L2 F L2 F R2 B L2 R2 B' L' U2 F D' F' L2 F U2

8. 14.20 R U2 B2 L2 B2 L' D2 B2 F2 L2 B' D' U' B' D L2 F' R2 U2

9. (11.38) L' D' F' R2 B R2 D2 F D2 L2 B L2 F2 D' U2 R' F2 L' F' D

10. 13.62 F2 L2 U F2 L2 U2 B' L' F2 L2 D2 F' U2 F' R2 B' U2 R2 U2 R

11. (18.01) F2 D2 R F2 D' U2 L2 B2 U' B2 U' R2 F' R2 U B R' F2 D'

12. 13.96 F L' D L2 D2 F2 R2 F2 L2 D B2 R2 F' U' B' L F2 L D F2

Cube was a Gan 356 X.

When I last did timed solves a year ago, I can't recall my exact pb's but I think they were around Ao12 15.40 and Ao50 16.60, so I gained around 1 second off my averages after a year of untimed solves.

The thing that is most noticeable is that it is now possible to make serious errors in the solve and still get 14.XX, and I am now able to get 11.XX with only mildly lucky solves and 12.XX with non-lucky solves. To get sub-11 still requires significant luck and sub-10 solves require very high luck mixed with flawless lookahead. The above set of 139 solves had two 11's and six 12's in the same sitting which also felt very unusual compared to a year ago.

What is disturbing about getting faster is that I noticed that lookahead failures and/or algorithm 'fetch' delays in memory now have utterly dramatic negative consequences. Even pausing for 3/4 of a second has a major negative impact.

What is most frustrating is that even after 3.5 years of speed cubing I still have a number of what I call 'problem-cases.' Algorithm cases where I struggle to fetch the algorithm from memory, struggle to execute it and often screw up, and it seems no amount of drills fixes the problem for those particular 'bad cases.' So far my only explanation is that certain algorithm patterns don't lend themselves to memory and execution and in these cases my best bet is usually to just 'delete' the old algorithm from memory and find a new one which fetches/executes more smoothly, even if the new algorithm is longer and apparently slower than the old one.