Why is your F2L slow?

[Nestor]

All of the previous... around 10" for F2l but I have a terrible terrible cross and LL which pushes me to 24" avg.

 

[oll+phase+sync]

What anys me about my F2L

1. not finding a pair

2. doing more F and B moves than normal

3. When pieces hide in a foreign slots, I pull them out for move cout optimal Slot-in afterwards. but often that requires rotations or lot of F / B moves.

 

[ElectricDoodie]

2. doing more F and B moves than normal

I didn't know people actually did F and B moves during F2L.

 

[Hyprul 9-ty2]

I didn't know people actually did F and B moves during F2L.

If I'm not wrong B moves aren't very common, but F moves are.

 

[Kirjava]

B moves are the sh*t in algs.

 

[uberCuber]

4. Pauses

My lookahead is not that bad so I won't include that

I would like to know your reason for bad pauses if it isn't bad lookahead.

well to be fair, consistent turning can get you 10 seconds F2l. So I would say anything over 15 seconds is slow.

edit: and i meant 15 seconds entire solve. my bad.

I can get a 10-second F2L without getting a 15-second solve. Slow/Fast F2L doesn't say all that much about last layer speed. I don't see why you mention full-solve times when the question was simply about F2L speed.

I didn't know people actually did F and B moves during F2L.

It's called edge control.
R' F R F' etc.
I would agree though that B moves are not that common in F2L, but what Kirjava says about B moves in algs is :tu

 

[ElectricDoodie]

It's called edge control.
R' F R F' etc.
I would agree though that B moves are not that common in F2L, but what Kirjava says about B moves in algs is

That's true. F moves aren't too weird to use, but a B in my F2L would throw me way off.

And B moves during PLL is fine with me.

 

[Mike Hughey]

This annoys me to no end. Roux users are like Mac fanboys.

Yeah, but Roux users are fun to race with when you rush the inspection time on them.

 

[ssb150388]

My F2L is slow because of not-so-optimal handling of the not-so-good cases.
TPS is not bad because I just use R/L/U in F2L. (Inspired by Faz \m/).
and of course, sometimes I forget to look ahead.

 

[ilikecubing]

I would like to know your reason for bad pauses if it isn't bad lookahead.

With lookahead i know where the pieces of my next pair have gone,but there is a slight pause in recognizing the EO and thinking about starting moves which are to be done after seeing the pair

 

[uberCuber]

With lookahead i know where the pieces of my next pair have gone,but there is a slight pause in recognizing the EO and thinking about starting moves which are to be done after seeing the pair

Lookahead shouldn't just see where the pieces are but also how they are oriented. There is little point in looking ahead if it doesn't allow you to continue without pausing.

 

[FatBoyXPC]

Yeah, but Roux users are fun to race with when you rush the inspection time on them.

Or when you just make them stick to 12s (Jt at minimum), unless they have an easy first block. Give him time to pre-plan out his whole first and/or second block and of course he'll fly That's like saying "let him plan out his entire F2L and see how fast he is"

 

[jack3256]

Between cross and the first pair even though I solve it on the bottom

 

[Vinny]

Definitely cube rotations...

It'd be interesting if this was a poll to sort of compare everyone's reasons.

 

[Pyjam]

My eyes are too lazy during F2L, instead of looking ahead I look at the pair I’m currently solving (even if I can do it with my eyes closed).

For this reason, I chose to apply a personal method: after the cross, I orient the edges (like in ZZ but much easier), then I solve the F2L.

The Pros:
– The difficulties are separate in two stages : orientation then F2L.
– It forces my eyes to be very active while orienting the edges.
– It simplifies the F2L cases. So I’m more confidant and I have a better look-ahead.
– Possibly, it prepares me a little for the EO step of ZZ.
– Very useful for OH beginners. I now have a decent PB.

The Cons:
– The OLL is reduced to the second step of 2-look OLL. So, you can’t include new OLL algs.
– Per se, it’s not a good speedsolving method, but it’s not its goal.

I opened a thread on this subject.
http://www.speedsolving.com/forum/showthread.php?28340-Fridrich-with-early-edges-orientation

 

[chris410]

My cross needs work so the transition is slow, easy cross I can usually find the first pair however, most solves I can only spot a corner. Simply finding the pieces and inefficiency in some cases. I am working on simply slowing down and focusing on "smooth" solves with minimal pauses so my times are up and down. Of course, my times are horribly slow compared to most of the forum however, I cube for pure fun and self challenge so, I am ok with my speed compared to others.

 

[Chapuunka]

When I'm using ZZ:
-Lack of practice (not used to looking in all those places for pieces)
-Too lazy to plan out the line part of EOline = huge pause

When I'm using CFOP:
-Cross-to-F2L transition
-Lockups because I don't slow down enough
-When I get lazy and stop trying to look ahead

 

[24653483361]

Well lookahead is probably a big thing for me.
Also the transition from cross to f2l takes me like 5 seconds to find a pair.

 

[Anonymous]

When I'm using ZZ:
-Too lazy to plan out the line part of EOline = huge pause

This doesn't have to happen. Because of bad habits, I often don't even bother to locate the line edges before I start solving, but I always find them as I execute EO and then solve them. Usually, there's no pause. I / people in general should still plan out the line part of EOline in inspection anyway, though.

 

[ryo]

Roux users are like Mac fanboys.

This. Make my day.

My F2L sucks because :
- Either I'm not concentrate or I'm to lazy for a good look ahead.
- I slow down to search a multi-slot / an OLL skip / a shortest way to make the pair.
- Turning speed is not that great.