Search results

I haven't really thought about doing that, but I might do it in the future. If anyone else wants to do it, feel free to do it though :)

Thanks! I personally prefer the one I wrote, but the inverse looks just as good.

Nice! I've been thinking about doing that as well.

Thank you :)

If you don't want to make it complicated, I would recommend just rotating. Eventually, it's useful to choose between y L' U L and y' R' U R depending on what's faster to execute or what's better for look ahead etc. (U) F R' F' R is a very nice option as well, and can sometimes be better than...

I guess "building good F2L habits" might not have been the best choice of words, when I think about it. What I meant to say is that I think you think you should at least learn all of the basic F2L cases first, since using inefficient and bad solutions will make look ahead a lot harder.

As you said, it's hard to know where to draw the line. JPerm has a couple of really good videos on look ahead, and if you haven't already seen it, I would recommend watching this:

I think this looks good for the most part! However, keep in mind that it's better to do U' R' U R U' R U R' or U L' U L' U R U R' instead of M U L F' L' U' M' if there are still unsolved adjacent slots. And if the diagonally opposite slot isn't solved, you might want to use something like y' R'...

I have intentionally planned a cross with two opposite edges swapped, but accidentally solved them correctly instead. I didn't realize it at first though, so I searched in confusion for the swapped pieces during OLL, causing me to pause for about 3 seconds. That solve was my first sub 10 ever...

I also forgot to mention another useful technique, where you deduce a front slot corner relative to the edge in the same slot. The idea is to visually see if it makes sense for them to be a connected F2L pair or not. If we ignore the obvious cases where the corner has colors that can't possibly...

Some things (like fingertricks, cube tilting and pauses) are hard to tell from a reconstruction so it's hard to give feedback on everything, but if you don't want to focus on too many things at the same time, you can just practice efficient F2L solutions for a while, since that's definitely one...

Do you have a reconstruction, or at least a list of the scrambles? That would help a lot and make it easier to give good advice.

If you're serious about becoming faster, I would recommend learning how to pair up pieces more efficiently by looking up the best solutions. JPerm has a video that shows most of the important ones, and I would recommend starting from there:

No problem! I just meant that you did D' U D2 instead of just D U.

It would be easier to give feedback if there was a video, but I'll try. Cross looks good (except for the mistake with the D move), and the last layer algorithms look fine. However, you should use U moves instead of y rotations before OLL to adjust the angle. The F2L solutions can be more...

Jperm has a lot of nice videos about look ahead, and this one is specifically about deducing pieces in the back slots:

For anyone interested, I'll explain in more detail how I deduce the front corners without looking at the bottom. For the sake of simplicity, I'm going to assume that the cross color is white, but the same concept can be applied to any cross color. First of all, I can sometimes deduce which...

I've now found this video with a 18/30s execution of OLL 23 and 7/30s pause between OLL and PLL (at 1:41): This is the fastest execution I've managed to find so far, but it's still only about 0.13s faster than the 2-twist execution by Tommy Cherry.

I'm not a ZZ solver, but I'm pretty sure EOCross is pretty advanced and it will take a lot of practice to make it worth using compared to a normal CFOP cross, if it ever can be in the first place. In any case, I don't think it's the best way to start for someone just starting to learn CFOP.

Of course, sometimes you can easily deduce the front slot corners by process of elimination, but I'm just wondering if there are people that deduce them without extra information. For example, I do it subconsiously for easy cases like a solved corner (i.e. when both colors matches with the...