• Welcome to SpeedSolving.com — the world’s largest puzzle community!

    You’re currently browsing as a guest, which means you have limited access to discussions, resources, member profiles, and community features.

    Join 50,000+ cubers and puzzle enthusiasts from around the world to ask questions, share solves, improve faster, and be part of the community.

    Registration is free, fast, and easy — create your account today.

    Already a member? Log in here to hide this message and start participating.

[Help Thread] Redi Cube Discussion and Help

I'm averaging around 16-17 seconds with a quite basic method me and Rob Yau came up with. It involves solving the first layer as normal and then reducing it down to 2 gen.
 
I'm averaging around 16-17 seconds with a quite basic method me and Rob Yau came up with. It involves solving the first layer as normal and then reducing it down to 2 gen.
I was just about to point out that you have the UWR on speedsolving.com
 
Oooh, nice. Care to explain further, or give an example solve or two?

Here's a more in-depth explanation: first you make the first layer as normal. Then you would solve one of the corners + the E layer edge that would go beneath it. Then you would solve the same pieces for an adjacent corner + the U edge that goes between that corner and the previously solved corner. At this point you should have two sides solved. To solve the remaining 2 corners and 5 edges you match up an edge to each corner and then you end up with a 3 cycle, which you then solve. A lot of the time a few pieces of the last step will already be solved and you can just solve it intuitively. A lot of the time it is very beneficial to preserve blocks so that the last two layers can be solved very quickly.
 
Here's a more in-depth explanation: first you make the first layer as normal. Then you would solve one of the corners + the E layer edge that would go beneath it. Then you would solve the same pieces for an adjacent corner + the U edge that goes between that corner and the previously solved corner. At this point you should have two sides solved. To solve the remaining 2 corners and 5 edges you match up an edge to each corner and then you end up with a 3 cycle, which you then solve. A lot of the time a few pieces of the last step will already be solved and you can just solve it intuitively. A lot of the time it is very beneficial to preserve blocks so that the last two layers can be solved very quickly.

Very cool. Pretty similar to my method; I just solve all E-layer edges and U-layer corners before moving onto the last layer. Seems like yours is better though; I think I'll try it out. Thanks for sharing! :)
 
How're people fingertricking this? Any tips / setup?

I'm fingertricking it pretty similarly to the way I fingertrick Pyraminx. Very few actual flicks, and more wrist turns (but not the bad kind). Since a lot of the solve incorporates some form of sledgehammer or another, I generally fingertrick those by just holding the two corners that are being turned and rotating in the appropriate direction.
 
Hate to double post, but this is pretty unrelated to my last post. Just got a 9.43 UWR single! The solve flowed really well and was decently lucky, but I didn't have any skips or anything. I'm averaging around 18 now. :)
Nice, beats my 9.89 from 2 minutes ago :eek:
 
Got my redi cube! It's a fairly easy solve XD. I might start timing it soon. It's soo smooth. How are people scrambling it on Cs?
 
If someone can explain this notation to me, I'll have a fast random-state scrambler written by tomorrow.

With rubikskewb, you hold a corner in front so on both layers you have a front, left, right, and back corner. Capital letters (F, L, R, and B) mean turning a top layer corner clockwise, and lower case letters are the bottom layer corners.
 
With rubikskewb, you hold a corner in front so on both layers you have a front, left, right, and back corner. Capital letters (F, L, R, and B) mean turning a top layer corner clockwise, and lower case letters are the bottom layer corners.

Cheers. I'll link it when I'm done.

E: Bummer, it's not as fast as I thought it'd be. Scrambles are also a lot longer than optimal (~20 moves).

E2: And here it is. (Average 16.5 moves, 0.15 second per scramble.)
 
Last edited:
10.067 L l' f r b' f' r' b B R B F R' F

PB, beats my second best time by 7 seconds, and about thrice as fast as my average. This thing is fun.
 
Back
Top