Corners First Method

[Kieran]

Hey,

I currently use a corners first method, one which only requires about 30 algorithms, and I can average about 45 seconds with it (with a new cube) But with my current cube, only about a minute 20 as it locks the whole time which is terrible for slices.

Just wondering if anyone could give me any tips, or could help me with the Waterman (learning of it) or knew of an optimized corners first method?

Cheers

 

[TMOY]

First, you can try to lube your cube, or loosen it (if possible), or whatever makes it less horrible on slices.
Recognition on first 8 edges is important too since it's usually the slowest part of a corners first solve. If you are able to solve several of them with only one look it will greatly improbe your times.

 

[Lucas Garron]

http://lmgtfy.com/?q=Waterman+method

 

[fanwuq]

I currently use a corners first method and I can average about 45 seconds with it.

Me too! I use Ortega corners and M2 edges. It's almost purely intuitive and probably has sub-25 potential.
It's not exactly a 3x3 speed solving method, but will help a lot if you ever get into 2x2 or BLD.

 

[Kieran]

I am getting a new cube in a few days, So I can't be bothered lubing my current cube. I suppose other than practise, I can't really make corners first much faster than 20 seconds? Does anyone know the move count? I don't use ortegas method, I just made my own algorithms. But I have 26.

It's kind of lame, there isn't much information on CF, yet if you look for Fridrich's, there is infinite amounts of it.

 

[JohnnyA]

Waterman's method is sadly under-used ... but there is a reason for that. Corner's first methods generally have fingertricks most people find difficult, and are much more difficult to get very fast. Let me see if I can find the site for Waterman's method I saw briefly yesterday.

EDIT: Found it straight away! http://rubikscube.info/waterman/index.html

This is probably the best link you will find for waterman's method. Gives a history of the method as well as a very nice description of the method.

 

[Kieran]

Yea, that method seems so damn complicated. I have just read through the whole thing and there is about 140 algorithms to learn, which for me, would take about a month. I think I'll see how fast I can get with CF using my method and a new cube, and then move on after I have optimized my algorithms (which sadly means I'll have to write them down).

Thanks.

 

[hooboork]

Hey,

I currently use a corners first method, one which only requires about 30 algorithms, and I can average about 45 seconds with it (with a new cube) But with my current cube, only about a minute 20 as it locks the whole time which is terrible for slices.

Just wondering if anyone could give me any tips, or could help me with the Waterman (learning of it) or knew of an optimized corners first method?

Cheers

I use CF too, know aprox. 15 algorithms and average +- 24 sec. with a terrible cube. I believe it´s all about practise.

 

[somerandomkidmike]

Ok, my advice is that for corners first, you actually don't do the corners first. To succeed with corners first, the MOST important thing to be good at is the First layer (minus one edge for most methods). If you are wanting to be very good, then the order I recommend is:

1) Solve 1 layer (or minus 1 edge) in any way you want (to average less than 20 seconds, this step should take less than 10 seconds). There are pretty much 3 ways you can solve the first layer. The first way is to solve the corners first, then the edges and the center. The advantage of this is that you always need less than 20 moves, and the recognition is very good. The second way is to solve a cross, then solve the corners. The recognition is good for this way, but it can take more than 20 moves. The third way is block-building. This way is very good if you want to use as few moves as possible, but it takes a better recognition. If you use this method for the first layer, then you have to do a lot of work, and you must understand how a rubik's cube works very well.

2) Solve the Corners. The best way to do this is in one algorithm, and learn the recognition described on Waterman's website. This takes a lot of work, and many algorithms. If you don't want to learn so many algorithms, then you can orient the corners first, then permute them. The other option is permute then orient.

3) Solve the rest of the cube however you normally would. This should take very little time, because the turns are all URM moves, and recognition is very good.

The reason I am telling you that this is a better way to solve it is because of recognition. Solving the corners first, then solving the edges does not set you up very well for the later steps.

You do not have to learn all the algorithms in the Waterman method to be a good corners first user, but you have to be very good at doing the first steps. I hope this makes sense/helped in any way.

If you are planning to learn all of Waterman, then I'd say you should learn only the algorithms you require first, then gradually learn the others.

 

[Kieran]

Oh thanks. That actually helped alot. I can do the 4 corners in about 8 seconds, but I then do the opposite corners, followed by all edges and then the final middle layer. But I'll try learn the cases for putting all the edges in for one side, and then the other outside layer cases for flipping it over. Thanks alot.

Do you know the av. move count for waterman?

Oh and do you know another site for The Waterman Method, because that site is good, but has a round about way of explaining it, and I'd just like to read over another site first.

 

[killerman0]

I currently, and always have used the corners first method. The way I do it is corectly place and turn the first 4 corners correctly, then place the last 4 correctly, then turn them the right way, then get the top and bottom edges, (or u can call them the left and right) using logic, then I solve the laft 4 edges in the middle layer. Currently I average about 30 sec. and my times are going down. using a loose cube lubed with silicone spray, you can do the same. for more info, details, or list of algorithms that I use, please feel free to send me a message.