What are the fundamentals of a good solve

[GAN 356 X]

What makes a good solve? Is it good look-ahead, good flow, high tps, or is it a lucky last layer?

 

[MarkA64]

Cross
Cross to F2L transition
Knowing F2L algs
F2L pair management
Lookahead
Last layer recognition

 

[Filipe Teixeira]

nah, more like:

spam tps
p a u s e
spam tps
p a u s e
spam tps
p a u s e
spam tps
p a u s e
spam tps
p a u s e
spam tps
p a u s e
spam tps
solved

 

[SM cubing]

whatever gets you sub 7s

 

[Cubeguy11]

Good tips and look ahead

 

[Owen Morrison]

In my opinion a good solve has these fundamentals:

• an efficient cross
• no pause or little pause between cross and F2L
• efficient F2L pairs
• no pause or little pause between each F2L pair especially between the first and second pairs.
• no pause or little pause between F2L and OLL
• no rotations during last layer (except for algs that require a rotation, E perms, V perms etc.)
• fluid execution of last layer algs

If a solve has all of these things it should be a pretty good solve.

 

[GAN 356 X]

whatever gets you sub 7s

But Feliks gets sub-5's every now and then, so there must be something that separates them from the rest

 

[Aerma]

But Feliks gets sub-5's every now and then, so there must be something that separates them from the rest

Feliks has incredible look-ahead and knows more tricks/techniques that 99.999% of cubers.

 

[MarkA64]

One thing that helps get a good average is recognizing when a solve is going well. So I like this discussion.

 

[icarneiro]

Look ahead and advanced F2L + fingertricks
Done

 

[Triangles_are_cubers]

for Roux its like:

1. Efficient and Fluid F2B
2. Little to no pause between FB and SB
3. Fast CMLL recognition
4. Fluid CMLL execution
5. Fast LSE recognition
6. High LSE TPS

 

[GAN 356 X]

One thing that helps get a good average is recognizing when a solve is going well. So I like this discussion.

Sometimes you can just tell your gonna get a pb. For example my 12.784 single (B' D L' F D L B L B2 D2 F2 B2 R L B2 D2 R' D L') I could see after about 5 seconds that I would have a good chance of beating my pb. It definitely could have been better if I hadn't of gotten a G perm and an OLL I dont know.

 

[Escher]

Remembering to use inspection efficiently, economy of motion, few 'collisions' between your pairs (i.e. solving one pair doesn't make the subsequent pairs more difficult), predictable last layer with highly reliable cases.

 

[Billabob]

Low movecount, high TPS.

In a good solve you should manipulate your next cases by using a different solution for your current case. You should also do this with the highest TPS that allows you to execute without pausing (going faster will introduce pauses and slow you down).