Long delay for Touch disconnection event to be notified
Hello. I'm working on a title for Oculus Rift and Touch. We recently switched to the oculus SDK 3.4.1
Since the switch, we noticed a long delay (few seconds) between a controller disconnection and when this is reported to the game (in the order of seconds).
This happens when the controller either runs out of battery or the battery is removed (the latter being the easiest way to test the issue).
We believe disconnection used to be reported a lot quicker in previous version of the SDK/driver.
We are working in a proprietary engine and we check the connection state by:
- Verifying we have a valid input state (obtained with ovr_GetInputState)
- Checking the flag for the specific controller (left or right) is set in input_state.ControllerType
Has the behaviour changed in the latest SDK/driver? Is there, maybe, a better way to check for a disconnection of the controller?
Thanks in advance for the answer,
Best Regard,
Samuele
Since the switch, we noticed a long delay (few seconds) between a controller disconnection and when this is reported to the game (in the order of seconds).
This happens when the controller either runs out of battery or the battery is removed (the latter being the easiest way to test the issue).
We believe disconnection used to be reported a lot quicker in previous version of the SDK/driver.
We are working in a proprietary engine and we check the connection state by:
- Verifying we have a valid input state (obtained with ovr_GetInputState)
- Checking the flag for the specific controller (left or right) is set in input_state.ControllerType
Has the behaviour changed in the latest SDK/driver? Is there, maybe, a better way to check for a disconnection of the controller?
Thanks in advance for the answer,
Best Regard,
Samuele