Once the shapes are interpenetrating, both wasHorizontalAligned and wasVerticalAligned are going to be true, because they only check for interpenetration in one axis, and the shapes are known to be interpenetrating anyway, and the interpenetration affects both axes, so both checks will be true. This...

You haven't provided a runnable version that can be used to debug. I've made your code runnable by applying this patch: --- ffiorig.lua 2024-05-11 09:47:53.683996392 +0200 +++ ffimod.lua 2024-05-11 09:49:00.158667324 +0200 @@ -1,7 +1,23 @@ -local vec3 = require("math/vec3") -local mat4 = r...

glass2d wrote: ↑Sat May 11, 2024 2:29 am When you say it "works for you" did you add this with no other rounding (Such as the player's physics body)

That's right. The character seems to jitter due to rounding problems and animation problems, but these are unrelated to the movement.

The idea is to round to screen pixels. It works for me, besides the obvious problems inherent to not using an integer scale, which cause image deformation.

OK, try this and see whether it helps: function PlayerCamera:update(dt) local camX = Player.x local camY = Player.y local mapW = Map.width * Map.tilewidth local mapH = Map.height * Map.tileheight camX, camY = self:setBorders(camX, camY, mapW, mapH) camX = math.floor(camX*self.scale + 0.5) / self.sca...

I wanted to have a look at the issue, but RL is keeping me quite busy these days. Could you please indicate what kind of movement you want? Specifically, my understanding is that you have a virtual resolution of 480x270 which is the underlying resolution, and you zoom it e.g. by 4 to get 1920x1080 i...

Gunroar:Cannon() wrote: ↑Tue May 07, 2024 10:43 am Could we just ... try to fix these problems, especially the jit?

No, we couldn't. Different projects, different devs.

What do you mean by jittery? Do you mean it snaps to virtual 480x270 pixels, and you want it to have screen-pixel movement as opposed to virtual-pixel movement? I find it hard to imagine what can be producing the tearing with the data you've provided. If you can, posting a .gif animation would help ...

Why is this not part of Löve already?

Great job. This could be especially helpful to novices who aren't familiar with error reports.

Many people use trig where none is needed. This problem does not need to involve angles at all. The solution in the post you've quoted is simple and elegant.