Move count for speedsolvin' 3x3

[miniGOINGS]

May I suggest to you the Y perm that I use? Its very fast for both 2H and OH.

R2 U' R' U R U' y' x' L' U' R U' R' U' L U

Is 14 moves.

Sorry, it won't work, I have to have the cube ready for LSE.

Oh yeah you use petrus. My mistake.

Roux actually.

To anyone who might have good algs... Thanks.

Double Phail on my part.

Haha yea, don't worry about it, but nice alg, I may use it for something I'm working on.

 

[masterofthebass]

Y perm for Roux:

R' U L' U2 R U' x' U L' U2 R U' L

gogogo

 

[waffle=ijm]

45-50 is my average in STM.

 

[DavidSanders]

I would say 60 is my average number of moves per solve. That could go down a little if I would just learn full OLL and a few of the tricky F2L cases.

 

[rubiknewbie]

Normally around 50-65. When there is a long PLL like Y-permutation then sometimes can't help but exceed 60.

If I do slowly and think of shortcuts and stuff sometimes can do 40+ but in the heat of the moment unlikely to get the optimum moves so 50+ should be average.

 

[hawkmp4]

I forgot to post my own move count...
Roughly 60. I do a 3LLL and I'm guessing that's where most of my moves come from. F2L could use a bit of optimisation too.

 

[rubiknewbie]

I'm off topic a bit, but I love the sune, it's so damn fast!

That's like saying you love Michael Jackson when everyone is talking about the NBA championships.

 

[Zane_C]

I'm off topic a bit, but I love the sune, it's so damn fast!

That's like saying you love Michael Jackson when everyone is talking about the NBA championships.

Yes, that's why I said it's off topic.
How's this, I love the sune, it is an effective OLL case and has not much moves.

back to topic:
Keyholes are good, they should cut my moves down slightly. multisloting looks complicated.

 

[JLarsen]

I got 58 on a random scramble I just tried. I'll do another.

52...

63

There's a good range for you. I tend to kind of brute force blockbuilding though. I determine what I'm going to do during 2x2x3 before i even get there, and the lack of delay makes up for the brute force nature of my solutions.

 

[rubiknewbie]

Although it is possible to do less moves, I end up purposely doing some longer algorithms to reduce cube rotation after I watched some of badmephisto's videos. He had 2 11-move algorithm for F2L that I use/plan to use.

 

[hawkmp4]

I got 58 on a random scramble I just tried. I'll do another.

52...

63

There's a good range for you. I tend to kind of brute force blockbuilding though. I determine what I'm going to do during 2x2x3 before i even get there, and the lack of delay makes up for the brute force nature of my solutions.

How exactly is your solution 'brute force'?

 

[LNZ]

For the very first time, I slow solved a 3x3 to get a half turn metric move count.

Here is the results:

Bottom layer cross: 12
Keyhole F2L: 39
Top layer cross: 06
OLL (1 alg): 08
PLL (2 algs): 17

Total: 78

Used 2-look OLL/PLL and a black Ghosthand for the run.

 

[Ness]

Okay, I also just counted my moves in one solve.

1. block: 8 moves
2. block: 10 moves
3. 2-look corners: 8 + 14 moves
4. rest: 20 moves
= 60 moves

The 1x2x2 block was very easy to see (4 moves) and i spent half a minute looking for a good second block solution. 3. / 4. would have been the same at full speed. first and second block would probably be about 10 moves more....
So, I continue practicing tracking pieces.

 

[Cyrus C.]

Right now in a speed solve:

2x2x2 - 8 moves
2x2x3 - 8 moves
Good edges/bad edges - 10 moves
Finish F2L - 15 moves
OLL - 7 moves
PLL - 10 moves
Total - 57 moves

If I'm going slow & trying to build blocks & stuff correctly.

2x2x2 - 6 moves
2x2x3 - 6 moves
Good Edges - 8 moves
F2L - 10 moves
OLL - 7 moves
PLL - 10 moves
Total - About 50 moves

When I was on Fridrich I had about 65 moves on average.

 

[Edmund]

Probably like 60 for me.

 

[Inf3rn0]

Just did a solve - 76moves.

Im curious i think im going to do more.

EDIT: 61

 

[Zubon]

I just did 3 slow solves using my normal method. Going slow, I saw some shortcuts which I wouldn't have seen going fast so I ignored them.

1. 57 moves
2. 61 moves
3. 53 moves

A lot of people are trying to use advanced F2L methods, double insertion or excessive use of free slots. Sometimes I think that just pure speed helps me rather than thinking about tricky shortcuts that save one or two turns but force me to regrip or use awkward moves.

 

[Zane_C]

Petrus looks very effecient, I think I'll stick to fridrich. I'm starting to use keyholes now to shorten the insertion of corners.

 

[rubiknewbie]

I just did 3 slow solves using my normal method. Going slow, I saw some shortcuts which I wouldn't have seen going fast so I ignored them.

1. 57 moves
2. 61 moves
3. 53 moves

A lot of people are trying to use advanced F2L methods, double insertion or excessive use of free slots. Sometimes I think that just pure speed helps me rather than thinking about tricky shortcuts that save one or two turns but force me to regrip or use awkward moves.

I get 57,57,42,50 but doing it slowly. 50-60 is normal for Fridrich.

In speedsolving, I want to use keyholes badly but always miss them or by the time I see them, it is always "ah screw it, let's move on" :fp. It might be the fact that they often end up in the wrong hand position.

The problem with speedsolving is that it is difficult to balance move count with finger-tricks and lookahead.

Give me 2 minutes and I can do all the efficient moves

 

[Zubon]

I just did 3 slow solves using my normal method. Going slow, I saw some shortcuts which I wouldn't have seen going fast so I ignored them.

1. 57 moves
2. 61 moves
3. 53 moves

A lot of people are trying to use advanced F2L methods, double insertion or excessive use of free slots. Sometimes I think that just pure speed helps me rather than thinking about tricky shortcuts that save one or two turns but force me to regrip or use awkward moves.

I get 57,57,42,50 but doing it slowly. 50-60 is normal for Fridrich.

In speedsolving, I want to use keyholes badly but always miss them or by the time I see them, it is always "ah screw it, let's move on" :fp. It might be the fact that they often end up in the wrong hand position.

The problem with speedsolving is that it is difficult to balance move count with finger-tricks and lookahead.

Give me 2 minutes and I can do all the efficient moves

Recently I have been taking advantage of the keyhole method in my Fridrich solves. If I have the corner piece oriented and in position in FRD AND the edge piece is in the top layer AND the slot in BRD is free, I use a quick fingertrick of (UD')RU'R'D' to insert the edge.