problems with fast moving object collision in unity (table tennis racket vs ball)

You should change your ball's collision detection mode. You can do that in its inspector or via script. See https://docs.unity3d.com/ScriptReference/Rigidbody-collisionDetectionMode.html.

@imperativity hey :-)

this is my capstone project at udacity vr dev i started in june...
right now i m using steamVR and the rift 2 complete this project in 1 week but then i wanna perfect it and put it also on oculus store, so i will build in also the OVR sdk... y? will it make a difference of how collisions behave? or r u asking coz u can support only projects/devs who develope for oculus store?

@Claytonious hey :-)

i wish it was that easy...

no conventional solutions work,and from what i heard there might b no other solution than creating a physics engine from scratch 2 deal with all the real-life physics i need 2 b able 2 create a 1:1 real-life simulation coz unity's physics engine might not b able 2 deliver...

i just hope there is an easier way,searched everywhere,no1 could help me,so i posted here coz i will develop this game for oculus and i thought it might b a VR related problem other devs here might have run into and solved...coz when i set up a test scene and trigger it by mouse click there r no problems no matter how fast the ball is,it just happens when moving the racket via controllers in VR...

I'm two years late but I'm having the same exact problem. Did you ever find a way to fix it or did you just end up making your own physics engine?

From my understanding you need to use ray-tracing instead of relying on the physics engine to detect when objects intersect. The physics interaction is too temporary for it to detect properly. 

Try to set collision detection on your Rigidbody to continuous dynamic.

If that's not working try to send a ray from the racket and use the hit normal to calculate the direction to send the ball away in.

Hope that puts you onto another direction to try.

Bruh, here's my recommendation:

Under Edit -> Preferences -> Time you will find a Fixed Timestep for calculating Physics. The easy solution is to set the collision detection to Continuous Dynamic and set that Fixed Timestep to like 0.01. BE CAREFUL WHEN YOU DO THIS! This can drastically impact the performance of your game if you load to much into your physics calculations (e.g. calling things on Fixed Update).

If that doesn't work, use Physics.Raycast or Vector3.Distance to constantly check the Distance between the objects and if it's within the threshold, run your logic.

I had this same issue with a table tennis game I was playing around with. I got it working after learning that you have to change the collision type to 'continuous' on both the ball AND the racket/paddle.