Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. On February 28th the Feedback website will shut down and be redirected to the Unity forums. See the full post for more information.
    Dismiss Notice
  5. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  6. Unity 2018.3 is now released.
    Dismiss Notice
  7. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

OnTriggerEnter problems ( maybe related to fast moving object? )

Discussion in 'Physics' started by Disastorm, Oct 13, 2018.

  1. Disastorm


    Jun 16, 2013
    Hello everyone. I'm trying to make a rhythm game in VR, so the idea is to have a fast moving object ( currently a sphere ) intersect with the players hands ( also currently a sphere ) and detect it, however some of them seem to be not colliding properly. Here is my current config:

    Beat object ( sphere with kinematic, interpolate, continuous rigidbody and trigger collider )
    Hand object ( sphere with kinematic, interpolate, contious dynamic rigidbody and trigger collider )

    The beat object moves via the rigidbody using the MovePosition method.
    The Hand object is a child of another object that is controlled by SteamVR, so this object does not move via any rigidbody methods.

    I have an onTriggerEnter on both objects.

    What could the issue be in this case? Is it because the hand object is not moving via rigidbody object methods? What would be the solution for this? I suppose if this is the case, I could make the rigidbody get the position of the hands and then do a MovePosition to it, instead of making it a child.