Dynamic bodies clip into static bodies

[aceinetx]

So I'm trying to make a simple platformer using the built in physics and the player clips into static bodies, it is very noticeable on x axis but the clipping still occurs on y axis just not as much.

2026-01-05.22-31-00.mp4

I tried using box2d which solved the issue but it was very tedious to write so I thought the built in physics would be better so I tried using this.
I am aware of substeps fix (set the substeps to a higher value) but to fix the x clipping you need at least 32 substeps which is not a good solution at all. With the substeps fix there is still this bug where if you clip into a wall and hold jump the y velocity would increase rapidly, this is related to how I handle input, I check if the space key is down, not pressed, which is expected and I want to keep this way of input handling (so that the player can just hold space to jump), but because the player is in a static body because of clipping, the player is always on ground which makes the velocity increase on every frame.
I don't want to check for walls (like with a raycast) to fix this bug since it just feels like a hack, you do not need to do that in a normal physics engine.

The game repo: https://github.com/aceinetx/Upright
master branch - box2d physics
ax-physics branch - built in physics with the clipping bug.

Thank you for help!

[aismann]

As I can see you use axmol v2.
I tried it on cpp-tests (modified for this example) and its works as expected:

[aceinetx]

As I can see you use axmol v2.
I tried it on cpp-tests (modified for this example) and its works as expected:

Then I really have no idea why this happens.
Maybe the move velocity is high & I set velocity.x on every frame. Guess I'll wait for v3. I'll also look into cpp-tests to see how the physics are set up there

[aismann]

Then I really have no idea why this happens. Maybe the move velocity is high & I set velocity.x on every frame. Guess I'll wait for v3. I'll > also look into cpp-tests to see how the physics are set up there

I set velocity.x on every frame
why?

Why not look at cpp-test and compare with your code?
v3 internal physics is not ready for using.

@aceinetx
Can you mark this as answer?

[aceinetx]

So after some more digging it turned out to be a chipmunk2d limitation - it doesn't support continuous collision, box2d does which is why I didn't have any issues using box2d. When v3 releases it'll swap the internal physics engine from chipmunk to box2d which hopefully fixes the issue.