Try Jolt if you don't need mobile builds yet. https://github.com/godot-jolt/godot-jolt
Thanks, I found that myself also and keep in mind. I briefly tried Jolt in the test scene I made for the glitch and it seemed to work more consistently.
Nah I don't believe it's normal. I just tried reproducing on 4.1.2 and it works fine on 60 ticks. I'd say try pushing a minimal project to a public repo on github or something that illustrates your problem. If we can't help you then, surely Godot Engine contributors would use it to fix an underlying issue in the engine.
It's a bit hard to reliably reproduce, but when I knock down the boxes on their broad side, there's usually at least one exhibiting this behavior. https://github.com/Walop/godot-physics-glitch
OK well you're not doing anything wrong. It's just that the default Godot physics server needs work. For what its worth, in this example that you've shown, the problem can be amended if you do the following:
In Project Settings -> Physics -> 3D
You can also enable Continuous CD in the Rigid Bodies but that usually just helps with detecting collisions in fast-moving bodies.
Your other option is to replace the default GodotPhysics3D with another one, as has already been stated.
I wouldn't recommend submitting an issue to the developers. I'm pretty sure they're aware of the physics server shortcomings.
Ok, thank you. I'll look into those.
Welcome to the programming.dev Godot community!
This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.
Make sure to follow the Godot CoC while chatting
We have a matrix room that can be used for chatting with other members of the community here
We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent