Accidently solving parity

[shnabz]

Hey guys,

I learned 3x3 and still consider myself a beginner, I don't know all the jargon and such, I just know basic algorithms that allow me to complete the 3x3 cube.

Anywho, I got a 4x4 cube and learned how to solve it, it seems though that edge and corner parity is the only part where i need to memorize an algorithm, which i really dont want to do. I have found a neat way of fixing both parity errors with a simple method that doesn't really involve memorizing an algorithm, which is nice, but to get to that stage I have to have the cube 'in a certain way' and I cant figure out how to do it. Sometimes I accidently change which edge has the parity error, and sometimes i actually even solve the parity error without even trying to, all im trying to do is set the cube up in a way that allows me to use my parity solving method. It's to do with the yellow cross bit, I kind of pretend that the parity error isn't there and continue solving corners normally, sometimes I get the yellow cross and sometimes I dont, but if i keep fiddling around with f r t -r -t -f enough then it ends up working. Does anyone know what this is?

 

[Chrizz]

Corner parity can be easily avoided by solving using OLL and PLL. Edgeparity happens because there are 2 of the same edges, and if you flip one edge, another edge will flip too (if you use reduction, that edge will have the same colors. The easiest way to fix it is with an algorithm, but if you really don't want to do that you can redo the edgepairing step, which takes a lot of time. Personally, I use this algorithm to swap an edge pair, it's pretty long (all OLLparity algs are long), but pretty easy to remember: (r2 U2)2 (r U2)2 r' U2 B2 U' r' U B2 U' r

Btw what do you mean with t ? I'm assuming with f you mean the front layer or the innerfront layer, same thing with r, but I don't know what you mean with t.

but if i keep fiddling around with f r t -r -t -f enough then it ends up working.

 

[shnabz]

Corner parity can be easily avoided by solving using OLL and PLL. Edgeparity happens because there are 2 of the same edges, and if you flip one edge, another edge will flip too (if you use reduction, that edge will have the same colors. The easiest way to fix it is with an algorithm, but if you really don't want to do that you can redo the edgepairing step, which takes a lot of time. Personally, I use this algorithm to swap an edge pair, it's pretty long (all OLLparity algs are long), but pretty easy to remember: (r2 U2)2 (r U2)2 r' U2 B2 U' r' U B2 U' r

Btw what do you mean with t ? I'm assuming with f you mean the front layer or the innerfront layer, same thing with r, but I don't know what you mean with t.

Sorry, I meant U, sometimes i call up 'top'

I think I figured out my problem, i never had parity error, i just missed a step out and thats how i accidently 'solved' the non-existent error.