collisions are incorrect

Started by Dobby · 5 months ago · 5 replies · 238 views

#1
Dobby
Member
JoinedApr 2026 Posts10 Score2,650
I'm currently working on a small pool game to get to know the editor better and gain some initial experience with game development.

So far, it's actually going pretty well. I've already added all the balls to the game and can hit the cue ball. But now I'm having a problem where collisions aren't being detected very reliably.

Sometimes the cue ball just flies right through the other balls, especially when it’s struck a bit harder.

What can I do to make the collision calculations more accurate?

In the options, I saw that under Physics, you’re supposed to increase the Sub Steps if you’re having problems there. But I’ve already increased it to 10,000, and it’s still happening. Is there something else I need to adjust?

#2
atalas
Member
JoinedApr 2026 Posts12 Score1,120
#3
Dobby
Member
JoinedApr 2026 Posts10 Score2,650
Thanks for the tip.
But will that actually help in my case?

I’ve seen that before, but the description says it doesn’t work with other objects that have that feature enabled.

If I enable it for all my spheres, then it won’t work anymore, right?

If I only enable it for the white sphere, it should work better. But with the others, it could still happen that collisions aren’t detected. 


Or am I misunderstanding something?
#4
atalas
Member
JoinedApr 2026 Posts12 Score1,120
Hi Dobby,

The EnhancedCCD is exactly what you're looking for, in fact the sub steps was a red herring and would not have helped for the 'tunnelling' effect you're seeing

You're correct in saying turning it on for every ball will not help. From my understanding the cue ball is the worst offender, so I would suggest implementing enhancedCCD on that first and see how far that gets you

If you're still seeing tunneling between balls where neither is the cue ball we can address that then, but there's not much value in accounting for something that we're unsure will ever happen


#5
Dobby
Member
JoinedApr 2026 Posts10 Score2,650
Hi atalas,

Thanks for the help.

I played around with the option earlier and enabled it for the cue ball.

You're right the cue ball is obviously the ball where it happens most often.

It helped right away.

Every now and then I still had issues where the other balls weren’t recognized correctly.
But I’ve got that under control now by simply scaling everything up to make the hitboxes larger, and I reduced the maximum speed for the cue ball on the first shot.

It seems to be running pretty smoothly now.
#6
atalas
Member
JoinedApr 2026 Posts12 Score1,120
Hi atalas, Thanks for the help. I played around with the option earlier and enabled it for the cue ball. You're right the cue ball is obviously the ball where it happens most often. It helped right away. Every now and then I still had issues where the other balls weren’t recognized correctly. But I’ve got that under control now by simply scaling everything up to make the hitboxes larger, and I reduced the maximum speed for the cue ball on the first shot. It seems to be running pretty smoothly now.
Hi Dobby,

Scaling everything up was the next step, good job!
people
Log in to reply
You can't reply if you're not logged in. That would be crazy.