Updated interact in version 2.2

EVG

Member
Good afternoon. I understand that interact was updated in version 2.2. And now, if an interactive object has an interactive parent, then only the parent object's interactive works. How to make sure that both the parent and child objects can interact separately? Sorry for the bad english.
 
You could specify a different interactable ID on the parent compared to the child and then have two separate Interact abilities.
 
Is it possible to prevent child colliders from responding to the interacting parent?
 
There is not currently an option, but you could make the change within Interact.ValidateObject (or subclass to modify ValidateObject). Setting a different Interactable ID is the recommended path for this situation though.
 
Top