0 Members and 1 Guest are viewing this topic.

It would be hard for a variable to get to 65565, but yeah, I get what you mean, if X increases too much, then it will come back to 0 at an unexpected time (due to 65536 not being a multiple of 96) and the sprite will jump.Maybe there is also a problem when Y>255, then Y+r2>255 and Y+r2 and 63>255 (and only affects the lower byte).

.Sᴇ847A→°SXᴇ8481→°SYFnOff While 1DispGraphClrDraw(Select((getKey(3)+SX+1-getKey(2)??96)-97,PutSprite())?+96)PutSprite()getKey(1)-getKey(4)+SY→SYEndIf getKey(15)Lbl PutSprite→SX64While 1If pxl-Test(-1→r₁, and 0,[AA55AA55AA55AA55])Pxl-On(r₁ and 7+SX,r₁*32/256+SY and 63)EndEnd!If r₁Return

Heu.... /256 can be optimised to /2/2/2/2/2/2/2/2 no ?

and why and 0" ?