--20cf302d4c4e2f246b04c16bb102
Content-Type: multipart/alternative; boundary=20cf302d4c4e2f246604c16bb100
--20cf302d4c4e2f246604c16bb100
Content-Type: text/plain; charset=ISO-8859-1
Results for CFOP/Friedrich method:
Complete first two layers (2/3 of 3^4) in 377 moves, not bad.
BUT
last layer #moves=f2l #moves (total around 650 moves), *therefore the last
layer method still needs work.*
Also, no shortcuts (e.g. recorded macros, edge turns, vertex turns) were
used.
The edge/corner "parity" problems are inefficient with face-only turns, so
I left them until last, which isn't a good idea.
Identifying the pieces often took a while and positioning 3c/4c pairs too.
Well, I don't know any other methods like roux or petrus so you can try
solving the 3^4 using those methods.
--
while(true)
Console.Writeline("HI!")
--20cf302d4c4e2f246604c16bb100
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Results for CFOP/Friedrich method:
Complete first two layers (2/3 of 3^4=
) in 377 moves, not bad.
BUT
last layer #moves=3Df2l #moves (total ar=
ound 650 moves), therefore the last layer method still needs work.
Also, no shortcuts (e.g. recorded macros, edge turns, vertex turns) wer=
e used.
The edge/corner "parity" problems are inefficient with=
face-only turns, so I left them until last, which isn't a good idea.
Identifying the pieces often took a while and positioning 3c/4c pairs too.<=
br>
Well, I don't know any other methods like roux or petrus so you =
can try solving the 3^4 using those methods.
--