Blindsolving Accomplishment Thread

Edit: Actually, it's strange - now I can't even find a video of his that shows that pattern - all of them look like they're review 2, then review 8. I wonder if I just saw it wrong, or if there's one of his videos where he really did it the way I saw it.

Maybe you got it from me. I suggested it some weeks ago. It worked perfect for me, when doing 13 cubes. But it was horrible with >20 cubes. I forgot way too many. Now I end the usual (1-1-4) reviews with a big review with all-1 cubes.
 
Just finished my TuRBo-system for corners (3 days of work).
It was a lot of fun but also very exhausting.
Now i can finally start practising..

Dennis
 
Linearly scalable, you say? Why don't you just try like, 18/18 sub-hour? :P

Because I'm chicken.

Actually, I want to get 8/8 first, then I'll go for 16, hoping to get sub-50.

And Marcin, sorry I misjudged; I still don't know how I got it so wrong. Now I have to decide whether to switch to your actual current system or not. I probably will switch. And I guess with the last review, it's not actually linearly scalable; I may try leaving that out.
 
Three days?? How advanced is this system?! :D
And for eveybody else who is interested in my TuRBo system, that i learn at the moment:

Basically, its the normal TuRBo system. But the problem about TuRBo are the setup moves because you have to think about the changing orientation, when setting up the 2 corners to the 2 spots, too much. So i made a list with every possible case (378). I always use 2 setup moves, only for 2 corners, i need 3 setup moves. I have a program where i wrote down every possible case, wich means, every image (378 of course).
I also invented 18 images for the 18 different algorithms. Then i added the name of the cases to every image.
I learned every case the past 2 days, so i know that image 235 is case no 12 for example. Now i have to get used to all the 21 possible setup moves. I can practise to find the belonging algorithm to every case with this program now.

For example:

The program says image "barn" and then i say its algorithm "chocolate" (7th TuRBo algorithm).
I know the setup move is R'F2, because it logical but of course i will get used to set up everything without thinking at all (only 21 possibilities, like i said). And of course i know, that "barn" is DRB-DLF.

Basically, i only have to get used to this:

1. Set up every possible case VERY fast and to undo everything VERY fast, too.
2. Thinking about setting up the next case, while undoing the present one.

Finding the belonging algorithm to the present case takes me already less than 0.5 seconds i would say.

Greetings, Dennis
 
Last edited:
Basically, its the normal TuRBo system. But the problem about TuRBo are the setup moves because you have to think about the changing orientation, when setting up the 2 corners to the 2 spots, too much. So i made a list with every possible case (378). I always use 2 setup moves, only for 2 corners, i need 3 setup moves. I have a program where i wrote down every possible case, wich means, every image (378 of course).
I also invented 18 images for the 18 different algorithms. Then i added the name of the cases to every image.
I learned every case the past 2 days, so i know that image 235 is case no 12 for example. Now i have to get used to all the 21 possible setup moves. I can practise to find the belonging algorithm to every case with this program now.

Oh my.
In full BH you have 15 or 18 algs (I don't remember exact number). Each alg can be executed normal or reversed; normal or mirrored; and with arbitrary cube rotation.
So for every of 378 cases you just have to learn an alg (one of 18), a cube rotation and flags (mirrored/reversed/none/both).
If you were capable to learn your system for TuRBo, you are really capable to learn this for BH, but that will bring you more benefit, and your setups for TuRBo will become useless, when you know BH.
 
3BLD PB avg of 5: 48.75, 52.89, (58.49), 56.51, (47.59) = 52.72

I was not lucky at all I think, I just somehow did better then usually :-).
 
Oh my.
In full BH you have 15 or 18 algs (I don't remember exact number). Each alg can be executed normal or reversed; normal or mirrored; and with arbitrary cube rotation.
So for every of 378 cases you just have to learn an alg (one of 18), a cube rotation and flags (mirrored/reversed/none/both).
If you were capable to learn your system for TuRBo, you are really capable to learn this for BH, but that will bring you more benefit, and your setups for TuRBo will become useless, when you know BH.

Thank you. You are the first person who explained BH to me in like 3 sentences.
I didnt KNOW, that BH works exactly like that, but i TOUGHT so.
I dont really like cube rotations that much. XY', ZX, YZ' or whatever is also a kind of setup-move i think. And doing R2F-algorithm-R2F' takes the same time as if you would do: YZ'-algorithm-ZY'. At least i think so.
Anyway, i guess i will learn BH one day. But i just started to learn TuRBo. So i should stay with that for the moment. And somebody (maybe it was even you) told me, that i can add more and more BH cases in the future, until i am full BH. So i dont think, that its a waste of time or anything. Right?

Greetings, Dennis
 
However, thinking about BH as intuitive algs and Turbo as memorized ones, it does.

Even if im a noob when it comes to BH:
You have to "learn" at least SOME algorithms for BH right? And there at least as many as for TuRBo (wich is not a lot).
The rest in TuRBo is more or less intuitive, too (setups and one of the algorithms). So where is the difference?

Greetings, Dennis
 
Back
Top