Hey guys. I'm having trouble learning EO line. My first try took me about 5 minutes to identify bad edges. (8). I reoriented them and tried to reorient 2 while making my line. Did not work, i then ended up having 4 more bad edges than last time. Any help on making the line or any simplified eoline rules?
For rules, you can't beat the tutorials by asmallkitten and Conrad Rider that
@GenTheThief mentioned above. I remember making lots of mistakes when I started out. With lots of practice, the mistakes become rarer. I remember that out of my first dozen solves, I got EO wrong more than I got it right. Now I make a mistake once every couple hundred solves.
What helped a lot was ignoring mistakes in EO when building F2L. In other words, if you see an edge is bad, just insert it flipped. Then when you get to the last layer, it's much easier to see which edges you got wrong. Make a note of the edges you got wrong, then solve the cube and apply the same scramble again. Count the bad edges, this time paying special attention to edges you got wrong, and try figure out why you got them wrong.
There are five possible reasons for getting an edge wrong :
- The edge was bad, but you missed it in inspection
- The edge was good, but you incorrectly identified it as bad in inspection
- The edge was bad and you recognised it as bad, but the solution you came up with didn't flip the edge.
- The edge was good, and you recognised it as good, but the solution you came up with unintentionally flipped the edge.
- Your F2L solution used F, M or wide moves which can flip edges.
You will need to figure out which of these mistakes you are making. One suggestion is to stop and do the EO recognition after each step. This can help you figure out where you're going wrong (although if your recognition isn't right to start with, don't trust it too much)
Depending on how fast you are, you may find it worth doing edge only F2L solves to save time. Do EOLine, then solve the 6 F2L edges ignoring the corners they are supposed to connect to. This makes it incredibly easy to spot mistakes, and takes about a third of the time of a full solve.