This is my code snippet for 8-dir movement in PICO-8. There are some in BBS like this but I think I have something to add here because:

1 - It doesn't move faster when going diagonals;

2 - It can move at speeds below 1 pixel/frame (sub-pixel movement);

3 - And most importantly: IT DOESN'T HAVE ANY ANNOYING JITTERING (the staircase effect)!!!

Feel free to scrutinize my code and give me any constructive tips. I am still getting started with PICO-8 and Lua.

Either my memory is wrong or browser/pico8 changed, but now the movement is jittery. Not an up-and-down staircase effect but a back and forth along the diagonal.

@merwok:

*"Either my memory is wrong or browser/pico8 changed, but now the movement is jittery. Not an up-and-down staircase effect but a back and forth along the diagonal."*

Not back and forth, but maybe stuttering. This is not an issue. It happens because the speed on the demo is 0.75. If speed is below 1, it means sometimes you don't move this frame. The position is drawn to the rounded values of x and y, which are floating point numbers.

In fact, if speed is equal to any non-integer value, you might think the character's movement is stuttering, like the framerate is inconsistent, when in fact a non-integer speed only means that you don't move a fixed amount of pixels each frame, which can make you feel unconfortable, but mathematically is correct.

I probably don’t know the right technical terms but that’s not what matters — I see is a visual glitch where the movement goes to some pixel, then back, then there again.

(also if we’re being pedantic, numbers are fixed-point not floating-point! :)

@merwok, I dunno what to tell you. I even recorded the movement of the pixel in video and watched it frame by frame to try to detect any backsteps.

The demo below is the exact same but here speed is equal to sqrt(2). This makes xspd and yspd equals to 1 when going diagonals, which is very pleasant to the eye, and equals to 1.41 when going horizontal and vertical, which causes a stuttering effect.

I think this is an intractable problem, because of the resolution and have decimal position values.

Perhaps it would be possible to smooth both vertical / horizontal movement and diagonal movement simultaneously, if you normalized the movement based on frames, so the movement rounding comes out right, but perhaps not. It seems like you'd be limited to a specific speed to get the numbers to round right.

My conclusion is that it is just a limitation of p8 and should be used in a game as a trick for gamers to use to their advantage.

If you set the speed = 1

and spdx and spdy = .75

it creates an even horizontal / vertical and diagonal movement, though vertical movement is not as smooth as the unnormalized movement.

while .75 is not precise in terms of normalization, i think it's close enough and helps create smoother pixel location rounding.

at 30fps though, i still think the unnormalized movement looks better.

How about this, @dariusdan and co ? Instead of moving in floating point, use the timer to handle diagonal moves. 100% U D L R and 75% for UL UR DL DR.

@dariusdan this works great! I tried making my own code to normalize diagonals and get rid of jittering, but it only works most of the time. Sometimes when going SW or NW, the jittering returns, but not always. I don't know why. Here is my code:

cls() function _init() p={x=64,y=64,spd=1.2} end function _update() --variables dx,dy=0,0 prev_diag=diag diag=false --input if (btn(⬆️)) dy-=p.spd if (btn(⬇️)) dy+=p.spd if (btn(⬅️)) dx-=p.spd if (btn(➡️)) dx+=p.spd --normalized diagonals if dx*dy !=0 then dx*=0.707 dy*=0.707 diag=true end --anti-jittering/smooth diags --idea from lazy devs academy --on first diagonal frame --set subpixel position --to center of the pixel if diag and not prev_diag then p.x=flr(p.x)+0.5 p.y=flr(p.y)+0.5 end --update position p.x+=dx p.y+=dy end function _draw() spr(1,p.x,p.y) end |

I'm jealous of your consistent diagonals. I'm trying to reverse engineer your code, but I'm pretty new to coding and can't quite understand it. Would you consider creating a bare-bones version that optimizes for readability for noobs? It could be a valuable resource for us new developers.

[Please log in to post a comment]