I'm having an issue with my Oculus controller where the B button becomes unresponsive unless the controller detects that my hand is holding it. This happens even if the controller is turned on and functional for other buttons or actions. Here is what I observed:
- Button B works perfectly when the hand is detected on the controller.
- If I remove my hand or hold the controller in a way that is not detected as "hand held", the B button stops working.
When my hand moves towards or away from the controller, an event is triggered in the console: XrEventDataInteractionProfileChanged. This event seems to influence how interactions are handled, particularly regarding the B button on the controller stopping working. This appears to be related to a change in the controller's interaction profile, which is detected and managed by the system. I'm looking to understand why this event interferes with the functionality of the button and how I could control or disable this reaction to ensure constant interaction with the button, regardless of how close my hand is.
**Questions :**
1. Is this normal behavior designed for security or ergonomic reasons?
2. Is there a way to disable this feature so that the B button can be used at any time, regardless of hand detection on the controller?
3. If this is a problem with my hardware or configuration, what steps can I take to diagnose and resolve this problem?
Any help or advice would be greatly appreciated. Thank you in advance for your support!
I apologize you've hit this issue. This behavior is fixed for v67 where button presses will work normally for unheld controllers as well. We apologize for the delays.
I apologize you've hit this issue. This behavior is fixed for v67 where button presses will work normally for unheld controllers as well. We apologize for the delays.
I'm terribly sorry that you're still seeing these issues. Let me investigate here if there was a problem with the ingestion. Just so I understand, it looks like you're using a Quest 3?
That you understand the benefit of having this possibility, with our solution you place the button on a fire extinguisher and when you use the handle of the extinguisher to press, a small plastic tab comes to press button B. this could also be another button)
Our current system switches from hands to controllers and there the problem is not encountered but there is always a latency time when we finish using the extinguisher and we find no hands to continue other interaction in the game. with the new simulataneity function, this will allow a better experience, being able to use your hands at any time to press an alarm for example and use the fire extinguisher (which presses the B button to initiate an interaction allowing you to see the particles of the real extinguisher appear.
indeed you are absolutely right Mikyjax.the same here in unity editor on windows with the headset connected in link, it works but once the build is produced and launched on the headset.need your hand on the controller to activate the controller inputs.
Apologies for the delays; I've been trying to sort this out on my end and get exact information to give here.
So, I had mixed up the actual release timeline a bit here. The fixes for this will ship in our public release fully in v69. I understand this is still a couple months away and I'm really sorry for the mix up and delayed timeline.
