Rubik's Cube Movement by pavel

function u(t) {

c.width=1920 // clear the canvas
for(i=0;i<9;i++)
x.fillRect(400+i*100+S(t)*300,400,50,200) // draw 50x200 rects

} // 122/140

Please log in (or register) to post a dweet (copy-paste the code somewhere safe to save it meanwhile)


    u(t) is called 60 times per second.
    t: Elapsed time in seconds.
    S: Shorthand for Math.sin.
    C: Shorthand for Math.cos.
    T: Shorthand for Math.tan.
    R: Function that generates rgba-strings, usage ex.: R(255, 255, 255, 0.5)
    c: A 1920x1080 canvas.
    x: A 2D context for that canvas.

show FPS hide FPS share 1 remix fullscreen

pavel

function u(t) {

eval(unescape(escape`𩡯𬠨𨰮𭱩𩁴𪁼👦👧🐾𚁫𙐱𝠦𙠱𚱫𙐲𚠮𝀱𝀩𚡧𚁡🐮𝰸𝐴𚠨𪰫𜠯𚀱𚰱𩐳𚠪𚁴𙐱𚠴𛑩𚐩𚐩𛁫🐵𝰻𪐽𛐭𪰾🠴𞱸𛡦𪑬𫁒𩑣𭀨𞐶𜀫𝰰𜀪𦀯𮠭𬰬𝐴𜀫𝰰𜀪𦐯𮠭𬰬𬰪🐲𛁳𚐩𦱘𛁙𛁚𧐽𦱘👦𚁃𚐬𪐭𜠬𩠨𤰩𛁘𛁩𛐲𧐮𬱬𪑣𩐨𭀥𜰩𛁺🐳𚱚𛁳🐹𞐯𮠯𮠻`.replace(/u../g,'')))

Jun 19 2019 3:43 AM UTC

}// 139/140

Please log in (or register) to post as a new dweet (copy-paste code somewhere safe to save it meanwhile).

Rubik's Cube Movement

Show more comments…
u/pavel

191 for(c.width|=f=g=>(k%16&&1+k%2*.414)*g(a=.7854*(k+2/(1+1e3**(t%1*4-i)))),k=57;i=--k>>4;x.fillRect(960+700*X/z-s,540+700*Y/z-s,s*=2,s))[X,Y,Z]=[X=f(C),i-2,f(S),X,i-2].slice(t%3),z=3+Z,s=99/z/z
u/katkip

too good.
u/username

Rubik's Cubes cannot move the middle layer
u/pavel

If you hold the sides the middle moves, no? How could it not!
u/pavel

Here are notation-only moves for(c.width|=f=g=>(k%16&&1+k%2*.414)*g(a=.7854*(k+y*2/(1+1e3**(t%1*4-i)))),k=57;i=--k>>4;x.fillRect(960+700*X/z-s,540+700*Y/z-s,s*=2,s))[X,Y,Z]=[y=i-2,X=f(C),f(S),y,X].slice(t%3),z=3+Z,s=99/z/z
u/username

Technically you are moving both sides at the same time in that case instead of moving the middle layer.
u/katkip

^
u/pavel

That's not what technically means. You have a mental model that only permits sides to move, and you have that model because adding middle rotations would be notationally redundant in that model. This does not mean middle rotations are somehow impossible or that they definitely consists of two side rotations.
u/username

Erm, the middle layer is attached to the core, that is what I mean. It is about the construction of a Rubik's Cube.
u/username

http://www.madehow.com/images/hpm_0000_0007_…
u/pavel

Still seems like this is a matter of perspective. You are chosing a perspective in which the core is always fixed, even though the motion I am describing specifically involves holding the two sides fixed and rotating the core... In my reference frame the core is rotating. So what if the core contains more parts than the side pieces when you take the cube apart?
u/13thptr

that escalated quickly
u/donbright

maybe they dont actually move like this... but they should!


      u(t) is called 60 times per second.
      t: elapsed time in seconds.
      c: A 1920x1080 canvas.
      x: A 2D context for that canvas.
      S: Math.sin
      C: Math.cos
      T: Math.tan
      R: Generates rgba-strings, ex.: R(255, 255, 255, 0.5)

dwitter.net