But that's why I said roughly. I'm wondering if I'm doing "roughly" enough.

Obviously I need some sort of guideline, otherwise I could be doing 1 solve a week and thinking that was enough.

I know it differs from person to person, but how much were you practising when you sub-1 average?

I got to sub-1 in about a year from my first BLD solve and I can't really tell an average amount of solves/day or week I did during that time because it varied so much depending on the time...(work vs holidays, interest in cubing vs interest in other stuff)

But I think more important is how you practise:

Ollie's tips are very good in that. I personally try to get my memo sub-15 consistently now using the tip number 2. Also learn commutators at least for corners and some advanced M2 for edges.
Then try to do at least a few solves every day. I have noticed that at least for me doing a few solves everyday is better than doing a big session once or twice a week.

Also don't be satisfied with your current times :P Try to push your memo to be faster and try to turn faster and think ahead. This will probably lower your accuracy at first but you WILL get faster this way and you will also get used to it and get better accuracy again after a while...
 
For U2 X-centers and T centers, let's say I get the letter C (I use speffz, so this is a U layer target) in the second letter of letter pair during memo. Should I memo it as A or just remember that I should do the alg for A rather than C? I guess the same goes for r slice targets for r2.
 
Both variants should work just fine. From what I know most people still remember the original letter as normal and then only execute the "opposite" target during execution.
The problem with the first variant is that you always have to think "Oh, ist this my first or second letter?" which can keep you from getting good memo times
 
Should I memo it as A or just remember that I should do the alg for A rather than C?

Memo it as C. You don't need to remember that you will need to do the alg for A, while you are executing you will notice that C is the second target of a pair, and thus you need to do the alg for A.
 
7. 52.22[16.46] D R F' D' F B2 L' U2 R B2 D2 F2 R2 L2 U D2 R2 F2 D R2
8. 1:02.13[20.58] F2 U2 R2 B' D2 F2 R2 D2 F U2 F2 L U2 R B' U2 R F' R' D' U
10. 58.75[17.21] U' B2 F2 L2 D' B2 U F2 D L2 D' F R F2 U2 R' B2 U2 L B' F'
17. 54.74[16.34] U L2 U' B2 F2 D' L2 F2 U2 B2 L' B' R2 F L' U' L' R2 B2 L
20. 55.63[16.38] D2 L2 U2 F R2 U2 F2 R2 B F' R' B' L' F2 U' R U' B' F' U
22. 53.94[14.43] D2 R2 U' L2 B2 F2 D' R2 D' L2 R2 B L2 U F' R' D L U2 R D'
24. 50.07[13.95] L U L F D B U' B' R' U2 F L2 F2 R2 F2 D2 L2 F' U2 L2
25. 50.75[16.84] L2 B' R2 D2 F U2 F2 R2 F L2 F D L2 U2 L2 R' U' R B' F'
26. 1:00.86[15.49] R2 U2 F' D2 B' R2 B' L2 R2 D2 L' U F' D' B R' U2 F' D2 R'
27. 1:00.08[17.34] L2 B2 D B2 U L2 D2 F2 L2 D R2 B L2 B' L' B2 F' L2 B' L2 R

i decided to time my memo. it seems i am pretty consistently sub-20 now. at what memo times did you fast people start switching to comms?
 
7. 52.22[16.46] D R F' D' F B2 L' U2 R B2 D2 F2 R2 L2 U D2 R2 F2 D R2
8. 1:02.13[20.58] F2 U2 R2 B' D2 F2 R2 D2 F U2 F2 L U2 R B' U2 R F' R' D' U
10. 58.75[17.21] U' B2 F2 L2 D' B2 U F2 D L2 D' F R F2 U2 R' B2 U2 L B' F'
17. 54.74[16.34] U L2 U' B2 F2 D' L2 F2 U2 B2 L' B' R2 F L' U' L' R2 B2 L
20. 55.63[16.38] D2 L2 U2 F R2 U2 F2 R2 B F' R' B' L' F2 U' R U' B' F' U
22. 53.94[14.43] D2 R2 U' L2 B2 F2 D' R2 D' L2 R2 B L2 U F' R' D L U2 R D'
24. 50.07[13.95] L U L F D B U' B' R' U2 F L2 F2 R2 F2 D2 L2 F' U2 L2
25. 50.75[16.84] L2 B' R2 D2 F U2 F2 R2 F L2 F D L2 U2 L2 R' U' R B' F'
26. 1:00.86[15.49] R2 U2 F' D2 B' R2 B' L2 R2 D2 L' U F' D' B R' U2 F' D2 R'
27. 1:00.08[17.34] L2 B2 D B2 U L2 D2 F2 L2 D R2 B L2 B' L' B2 F' L2 B' L2 R

i decided to time my memo. it seems i am pretty consistently sub-20 now. at what memo times did you fast people start switching to comms?

I'm not that fast and I don't know about memo times but I started to switch to commutators when I averaged something like 1:20-1:30
 
UF - l' (B' R B U R2 U') r2 (U R2 U' B' R' B). I guess there should be l in the end.

Indeed, there should be an l in the end.

And one more: shall I do alg for UF or another if I am after first r2? I hope you know what I mean, I just started to learn M2/r2.

UF is not in the r-slice, therefor you must always use the alg for UF. Only the algs for FU and BD need to be swapped if you have done an odd number of r2-turns.
(!!! I hope you understand the difference between UF and FU. UF is in the l-slice, FU is in the r-slice.)
 
Last edited:
What is a good parity alg for M2/OP if M2 buffer if UF?

Do you execute edges first or corners first?

What I would do is:
1. memo edges first then you know if you will have parity or not.
2. memo corners and in case you have parity memo so that UBL and UBR are swapped.
3. execute corners
4.execute edges.
5. After last edge target shoot to UB (but since that is uneven target you actually need to do the alg to shoot to DF)
6. Do y(T-Perm)
7. ???
8. Profit
 
What difference does it make if you execute corners first or edges first?
You have to fix parity differently depending on which piece type you solve first. Using M2/OP and solving edges first, you do U' F2 U M2 U' F2 U (or D' L2 D M2 D' L2 D) between edge and corner execution. But if you solve corners first, doing that will leave your M slice off by M2 before you solve edges, and edges end up not being where you memorized them, which you could use, but you'd have to execute M slice targets as the opposite target if they are the first target of the letter pair (instead of the second target like when you don't have parity). Another reason I like solving edges first is that the memorization of the piece type you solve first and execute last has to be remembered longer. Corners are less to remember, so they're easier to remember for a longer time. Edges have more pieces to solve, so solving them immediately after I memorize them means I probably won't forget them, because they were what I just memorized.
 
Last edited:
But if you solve corners first, doing that will leave your M slice off by M2 before you solve edges, and edges end up not being where you memorized them, so that doesn't work

What, why doesn't that work? I use this and it works. You just need to keep track of the M-slice for the UF and DB pieces, which you also have to do if you don't have parity.
 
What, why doesn't that work? I use this and it works. You just need to keep track of the M-slice for the UF and DB pieces, which you also have to do if you don't have parity.
You could do it by executing DB and UF switched and BD and FU switched, but I think that creates extra unnecessary thinking, because what you execute is different from what you memorize. I used to do this sometimes in multi BLD, but now I've switched because it slows me down a little having to think about doing the opposite target, however it is possible to use it.
 
Do you guys think that occasionally pushing farther beyond the number of cubes you are comfortable with can help for Multi? Like say, I've never attempted more than 3 cubes, and what if I decide to do 6? Obviously if you're comfortable with 9 you're probably not going to go do 18, but since I'm at smaller numbers now, I thought this would be a decent example. I've heard mixed things about this, so that's why I'm asking.
 
Do you guys think that occasionally pushing farther beyond the number of cubes you are comfortable with can help for Multi? Like say, I've never attempted more than 3 cubes, and what if I decide to do 6? Obviously if you're comfortable with 9 you're probably not going to go do 18, but since I'm at smaller numbers now, I thought this would be a decent example. I've heard mixed things about this, so that's why I'm asking.

Just go and try 6 cubes and see how that goes. If you don't get all of the cubes solved, take a break and then try again. It gets easier everytime you try.
 
What is the rule here: You are doind multiblind and you have two cubes off by one move. Are they both just +2 or is it only one cube +2 and the another is *unsolved*?
Regulation H1d) Time penalties for the puzzles of the attempt are cumulative.

This means if you have two cubes each off by one move, the penalty is +4 seconds, however both cubes count as solved in your score.
 
Do you guys think that occasionally pushing farther beyond the number of cubes you are comfortable with can help for Multi? Like say, I've never attempted more than 3 cubes, and what if I decide to do 6? Obviously if you're comfortable with 9 you're probably not going to go do 18, but since I'm at smaller numbers now, I thought this would be a decent example. I've heard mixed things about this, so that's why I'm asking.
I'd only ever done 3 at home, then I tried 6 in comp. I got 3/6. But at home it doesn't matter how bad you mess up so I would try as many as I can be bothered doing and can probably fit into an hour.

My multi PB was 3/3 then I got some more cubes and got 10/10 straight away so it can't hurt.
 
Back
Top