Thank you "CubeNovice" and "Xishem" this will most surely help me in my blindfolded journey!
I will try to do that but how do you differentiate between corner and edge memo?
What you could do (and what most BLD solvers do) is solve the groups (corners and edges) in the reverse order that you memorize them. For example, I memo edges, then corners; and solve corners then edges. This lets me use a weaker, but faster memo system for corners, so I can solve them while they're still in my short-term memory.
And, to answer your question, I never confuse edge and corner memo :)
 
there is no faster method. 3OP uses less moves but Old Pochmann is very fingertricky with super easy setup moves and room for optimization. Both can be part of sub45 solves.
 
im gonna desagree with Rpotts but:
3OP is the best method behind BH!!!
and is much funnier too
BTW
3OP or op?
op is Ts method or something?
 
Last edited by a moderator:
OP = Old Pochmann which uses T, J/L and U perms to solve edges and Y perm (minus the first and last F moves) to solve corners. It's commonly considered the best method for beginners to learn but has a very high move count, often taking 200+ moves for a single solve.
 
I would say that 3OP probably has slightly higher potential for speed from what I've observed. However, I strongly recommend Old Pochmann as you will want to move on to 3 cycles without orienting first, and Old Pochmann will use an identical memorization system, whereas 3OP will not.
 
which "algorithms" do you have trouble with?

Btw the way he deals with parity is silly, just use U' F2 U M2 U' F2 U

EDIT: oh you mean the M slice targets, personally I just use M2, U2 M' U2 M' and M U2 M U2 and just deal with the flipped edges at the end, like on Pochmann's tutorial.
 
Target FU and BU have all these awkward F turns.

EDIT: Oh yeah, you already explained that...
 
Yea I don't really like the algs either, so I choose not to use them. It does mean that sometimes i end up with 4 or even 6 edges to flip at the end, but that's not too hard.
 
TuRBo is hard. Even if you know algs, aren't you messed up with setup-moves?It takes me long time to configure which setup move i should do and which alg to use. How fast can anyone do edges with it?Does smbd set WR or NR with that? (sorry for too many questions)
 
TuRBo is hard. Even if you know algs, aren't you messed up with setup-moves?It takes me long time to configure which setup move i should do and which alg to use. How fast can anyone do edges with it?Does smbd set WR or NR with that? (sorry for too many questions)

TuRBo is not hard bro. You have to do setup-moves in almost all methods except pure BH (and even there there are lots of shortcuts if you do setupmoves). You only need like 0-3 setupmoves and these should become second-nature after a while. How long have you been training?

If you do not like the idea of setup-moves I can recommend you 3OP for corners or M2 for edges. If you need more help feel free to PM me so we can chat on Skype/Messenger.
 
TuRBo is hard. Even if you know algs, aren't you messed up with setup-moves?It takes me long time to configure which setup move i should do and which alg to use. How fast can anyone do edges with it?Does smbd set WR or NR with that? (sorry for too many questions)

I highly recommend you don't stick to strict TuRBo. It will be A LOT easier if you can do the algs from different angles. So all you have to do is get the 3 pieces you wanna cycle on the same layer
 
TuRBo is hard. Even if you know algs, aren't you messed up with setup-moves?It takes me long time to configure which setup move i should do and which alg to use. How fast can anyone do edges with it?Does smbd set WR or NR with that? (sorry for too many questions)
At first TuRBo is difficult, but it shouldn't take long to recognise setup moves fast. If you haven't looked at this already, it might help.
 
which "algorithms" do you have trouble with?

Btw the way he deals with parity is silly, just use U' F2 U M2 U' F2 U

EDIT: oh you mean the M slice targets, personally I just use M2, U2 M' U2 M' and M U2 M U2 and just deal with the flipped edges at the end, like on Pochmann's tutorial.

Yes, but that's only good for solving edges first. Solving corners first and doing that will mess up your M slice. I'd rather do an R-Perm with a safe solve.
 
it's not a higher risk, it's just during parity the M slice is off on the first shot in a pair rather than the second. I rarely DNF because of parity.
 
Speed wise, would corner comms, or edge comms speed my times up? Currently using M2/OP. I'm thinking corners, since M2 is only slightly slower than comms.

I believe my execution time is near maxed out. If I could somehow get higher TPS I could improve it.
 
Back
Top