However, what we really want is to avoid VREvent_Quit events when controllers are being turned on. We don't want to shutdown our app OR SteamVR.
Unfortunately, we can't replicate this behavior consistently on our dev boxes, but we have seen it in our client's offices and have several logs indicating what is happening.
Any insights on what might be responsible for the VREvent_Quit events in this situation?
We have a user who is seeing a VREvent_Quit event fired when he turns on his HTC Vive controllers. This results in the controller calling the event:
https://github.com/ValveSoftware/steamvr_unity_plugin/blob/29aa1ebe985f69a5dd455a02e52c13c85a6b5240/Assets/SteamVR/Scripts/SteamVR_Behaviour.cs#L243
Even though we disabled this behavior by removing the above highlighted line (and replacing it with logging), it still causes our app to quit. This is probably due to this behavior: https://github.com/ValveSoftware/openvr/issues/1061#issuecomment-469757801_
However, what we really want is to avoid VREvent_Quit events when controllers are being turned on. We don't want to shutdown our app OR SteamVR.
Unfortunately, we can't replicate this behavior consistently on our dev boxes, but we have seen it in our client's offices and have several logs indicating what is happening.
Any insights on what might be responsible for the VREvent_Quit events in this situation?