Forum Discussion
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
3 Replies
- Sorry, I read the version number from the license page and doesn't correspond with the SDK version number. We are currently on SDK 1.19. I noticed there's a 1.20 available and I'll give it a try to see if I can reproduce the issue
- I just tested with version 1.20 and the same issue is present. If I remove the battery while the stick is moved, the driver will keep sending new messages for about 7 seconds before notifying of the disconnection
- Thank you very much for confirming this information. Would be possible to know if the behaviour has changed and, more importantly, if we should expect such a long delay to stay in the SDK for future versions?
