Godot

5855 readers

43 users here now

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

Other Communities

Rules

Posts need to be in english
Posts with explicit content must be tagged with nsfw
We do not condone harassment inside the community as well as trolling or equivalent behaviour
Do not post illegal materials or post things encouraging actions such as pirating games

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

Wormhole

!roguelikedev@programming.dev

Credits

The icon is a modified version of the official godot engine logo (changing the colors to a gradient and black background)
The banner is from Godot Design

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

Feyter@programming.dev

Godot 4.1 3D physics jittery at default tick rate (sopuli.xyz)

submitted 1 year ago by Walop@sopuli.xyz to c/godot@programming.dev

6 comments fedilink hide all child comments

I am using Godot 4.1 and after I added the first rigidbodies to my game, I noticed the physics seem really unstable. The floor is a StaticBody with large and 1m thick BoxShape. I have RigidBody objects with simple BoxShape colliders and the thinnest side is 0.3m. Often when I knock them on the floor they do not come to rest, but keep vibrating indefinitely. They are not on top of each other, this happens when a single object is only on top of the static floor. Increasing physics ticks per second to 120 seems to help, but I am not sure how it affects performance and what will be my final targets. Is it normal for the physics to be so unstable and jittery in such a case I would assume to be very simple and mundane at 60 ticks per second?

top 6 comments

sorted by: hot top controversial new old

[–] aventu@programming.dev 3 points 1 year ago (1 children)

Try Jolt if you don't need mobile builds yet. https://github.com/godot-jolt/godot-jolt

[–] Walop@sopuli.xyz 1 points 1 year ago

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.

[–] TsarVul@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] Walop@sopuli.xyz 1 points 1 year ago (1 children)

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

[–] TsarVul@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

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
- Set Time Before Sleep to 0.25 or lower.
- Set Sleep Threshold Angular to 0.1.
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.