-
-
Notifications
You must be signed in to change notification settings - Fork 993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CollisionTracker collisionValidity is this behaviour intended? #2046
Comments
I just find out there should be more component involved in the set up.
Two issues I can see then.
|
I'm not sure what the issue is here? The rule is to make sure a Collision Tracker cannot pass the message on to a Collision Notifier Not to check if a collision can occur between two objects. Can you provide a really simple explanation as I may not be understanding fully? |
I understand that the rule is to make sure a Collision Tracker cannot pass the message on to a Collision Notifier. I notice that RightInteractor's Collision Tracker, when collided with WellBase (with a IgnoreInteractorCollisionTag), the message is also passed on to collision notifier. The forwarding source validity rule is to ignore interactor collision tag. Its intention is clear that any touching "target" having that tag should not emit collision message. But because it is checking the "source", interactor never had the ignore tag and collision message is always emited. There is no trivial logic error in the touch/grab interactions because the Active Collisions Container has a ActiveCollisionValidity rule that says only accept (InteractableFacade, ClimbInteracbleFacade, ControllableJointDriveContainerTag). WellBase has not one of them so it is not touchable. yet the collision message is emitted. |
Environment
Steps to reproduce
Expected behavior
I expect the intention of the set up is to check whether the 'target' can be touched (emit collision event) rather than always check on the 'source'.
Current behavior
The source checking has very limited use.
The text was updated successfully, but these errors were encountered: