You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When implementing a custom interactor that stays continuously active (teleport mode), I found that when the NearInteractor was detected it would switch to the NearInteractor (higher priority) and would stay on the near interactor even when not active.
To reproduce
Steps to reproduce the behavior:
Create a new interactor with a detector that is always on, set it to a lower priority than near interactor.
Activate the new interactor.
Do a near mode interaction (while the other interactor is still valid)
Stop doing the near mode interaction
The near interaction mode stays active even though it is not currently being detected.
Expected behavior
When the lower priority interaction modes are no longer valid it should switch off them.
Your setup (please complete the following information)
Target platform (please complete the following information)
Vive Pro
Additional context
Modifying the InteractionModeManager update loop and SetInteractionMode so that the firsst time a detector triggers it sets the interaction mode for the controllers fixes the problem. The previous code would only reset the default mode if no detectors triggered. If a detector triggers during the update loop it will not switch to a lower priority interactor even if the current mode is higher priority, even if no detector for the existing higher mode is triggered.
The text was updated successfully, but these errors were encountered:
Describe the bug
When implementing a custom interactor that stays continuously active (teleport mode), I found that when the NearInteractor was detected it would switch to the NearInteractor (higher priority) and would stay on the near interactor even when not active.
To reproduce
Steps to reproduce the behavior:
Expected behavior
When the lower priority interaction modes are no longer valid it should switch off them.
Your setup (please complete the following information)
Target platform (please complete the following information)
Additional context
Modifying the InteractionModeManager update loop and SetInteractionMode so that the firsst time a detector triggers it sets the interaction mode for the controllers fixes the problem. The previous code would only reset the default mode if no detectors triggered. If a detector triggers during the update loop it will not switch to a lower priority interactor even if the current mode is higher priority, even if no detector for the existing higher mode is triggered.
The text was updated successfully, but these errors were encountered: