Garf's Progression Thread - Beating Hard Levels in GD (Hardest is Bloodbath)

Garf is (and you are)...


  • Total voters
    63
Oh, now I get it. You were saying "Valk 3" to me, not TheEpicCuber.

The Valk 3m was never a budget cube. Qiyi was trying to make the best of the best for one of the fastest cubers. It wasn't something they tried to cut corners on and make a quick buck. 3x3's are way different than big cubes. You can use most 3x3's since the Valk and still get the same times, the same isn't true for bigger cubes where hardware has improved dramatically since 2019.

(If you want to reply to more than one message just press "Quote".
Fair point
 
Alright, so I have a plan to be able to solve 4x4 OLL in 1-2 steps:
1. Recognize the case (parity or non)
2 Step 1: Solve Oll, or do set-up case Step Two (if there is parity) solve parity, (then undo setup, if done.

Basically, I will need to be able to recognize 172 cases for Oll on 4x4. Here's how I worked it out:
I know some cross oll parity cases for 4x4 already. For L shapes and Line shapes, there are 3 possible edges that can flip before the L/Line case becomes a cross case; and 4 different cases for each dot oll case before it becomes a cross case. So (30*3) + (12*3) + (7*2) + (8*4) is equal to 172. Of course many cases will end up having the same case, so the number will go down. Maybe I just have to learn half of what I said if half, or a quarter, or whatever; is oll, and the rest is oll parity cases
 
BTW: check out this background for cstimer:
Screenshot 2021-10-07 9.37.57 PM.png

Heck yeah...
 
Alright, so I have a plan to be able to solve 4x4 OLL in 1-2 steps:
1. Recognize the case (parity or non)
2 Step 1: Solve Oll, or do set-up case Step Two (if there is parity) solve parity, (then undo setup, if done.

Basically, I will need to be able to recognize 172 cases for Oll on 4x4. Here's how I worked it out:
I know some cross oll parity cases for 4x4 already. For L shapes and Line shapes, there are 3 possible edges that can flip before the L/Line case becomes a cross case; and 4 different cases for each dot oll case before it becomes a cross case. So (30*3) + (12*3) + (7*2) + (8*4) is equal to 172. Of course many cases will end up having the same case, so the number will go down. Maybe I just have to learn half of what I said if half, or a quarter, or whatever; is oll, and the rest is oll parity cases
Actually, is it more important to be sufficient in 3-2-3 edge paring, or should I keep Oll parity optimization as a major goal?
 
Alright, so I have a plan to be able to solve 4x4 OLL in 1-2 steps:
1. Recognize the case (parity or non)
2 Step 1: Solve Oll, or do set-up case Step Two (if there is parity) solve parity, (then undo setup, if done.

Basically, I will need to be able to recognize 172 cases for Oll on 4x4. Here's how I worked it out:
I know some cross oll parity cases for 4x4 already. For L shapes and Line shapes, there are 3 possible edges that can flip before the L/Line case becomes a cross case; and 4 different cases for each dot oll case before it becomes a cross case. So (30*3) + (12*3) + (7*2) + (8*4) is equal to 172. Of course many cases will end up having the same case, so the number will go down. Maybe I just have to learn half of what I said if half, or a quarter, or whatever; is oll, and the rest is oll parity cases
Aside from the 57 usual OLL cases, there are only 54 OLL cases that have OLL parity.

I don't know if anyone's got an up-to-date list of algs for those, but here's one by TDM.
 
Back
Top