Was a bit of work, but managed to run Marble Game Physics on a separate thread now. Jolt plugin never supported that, but the builtin version now does.
Was fairly straightforward, but in some cases, the errors gave me almost nothing to work with.
The more you know: the shape of PhysicsShapeQueryParameters3D should be initialized long before _physics_process tries to use it or jolt will poop itself.
=> More informations about this toot | More toots from memoriesin8bit@mastodon.gamedev.place
@memoriesin8bit
did you get performance gains from this ?
=> More informations about this toot | More toots from kuzkuz@mastodon.gamedev.place
@kuzkuz I mean... considering I have hundreds and hundreds of physics objects - obviously, it's gonna give me some. Not as much as if physics ran on multiple cores itself, but still - it no longer needs to share a core with the main game logic.
=> More informations about this toot | More toots from memoriesin8bit@mastodon.gamedev.place
@memoriesin8bit using jolt and 4.3 atm, so it's good to hear your upgrading is rather smooth all things considered
=> More informations about this toot | More toots from Tearcell@mastodon.gamedev.place
@Tearcell There are two main things to do when updating:
a) Pretty much all Jolt=specific project settings are named different between plugin and builtin. So whatever custom settings you made, you need to make again.
b) No Jolt-specific nodes (hinges) anymore. So if you used those before, you need to revert back to Godot versions.
=> More informations about this toot | More toots from memoriesin8bit@mastodon.gamedev.place This content has been proxied by September (3851b).Proxy Information
text/gemini