Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Thanks.
This is a very common problem with physics engines and fast moving objects. I thought that it was well callibrated in the game, but on the other hand if you loose a frame just before the impact then this may happen.

I had to create an option to reset the ball position.

About the problem with physics, if you are using Unity3d, it´s better use AddForce instead of Transform.translate, I´m saying because I had this problem once.

(+1)

I am using Godot and I am using apply_impulse ( I used apply_force too but I didn't like the results).

The problem with physics engines in general is that they move the objects in the physics step and then apply forces to separate the overlapping objects (collision reaction). This way if an object is moving too fast there is a possibility to pass through an object or stuck inside. The solution to this is to make more steps for the fast moving objects. Godot have this but the physics engine is locked with the frame rate, this means that if you loose a frame the crucial moment then you may have a problem like this.

This is how I remember things worked for Bullet at least, cause I have read some of the presentations and techniques back in the days of the first versions. I also remember similar things about the first presentations of Box2D. Godot's physics engines are like striped down versions of Bullet for 3D and Box2D for 2D.

I Unity I do not know what they used, but I remember that they had good reaction for fast moving objects.