Meta Quest 2 Controllers Acceleration
Hello, I'm trying to access linear and angular acceleration of Meta Quest 2 controllers. Here's the code I'm using: OVRInput.GetLocalControllerAcceleration(OVRInput.Controller.RTouch); It always returns vector with all components set to 0 for both controllers. The velocity/position works well. I'm using Oculus Integration package v47.0 and Unity 2021.3.17f1.
Which input system to use with Movement SDK
I'd like to experiment with the Movement SDK. The readme indicates Oculus Integration is a prerequisite.and that package uses the new input system (UnityEngine.InputSystem). The Movement SDK, however, is uses the old input system (UnityEngine.Input). Which system should I use?
OVR UI Helpers - Raycast LaserPointer and cursor not displayed in Quest build from Unity 2019.3.0f1
Hi all, really hoping someone might have experienced this same problem and found a fix, as it's really frustrating to not understand WHY this is happening. I'm Using Oculus Link and Unity to iteratively develop and test (using the play button in unity, which automatically plays on the USB connected Quest). I'm following the guidance for using UI helpers on a canvas object and have had no problems with being able to interact with all aspects of my UI using the touchcontrollers and the included raycast and linerender "Laser Pointer" script. The problem i'm having is when i come to do a build. Everything builds fine, with no errors but when I play it on the quest, the laser pointer/ line renderer not only doesnt show up it doesnt give me any interation with the UI when running on the Quest. Even stranger is the fact that when I plug my Quest back into the PC and start developing again in Unity, the problem then appears there. None of the UI interaction is working and the line renderer doesnt show up !? The only way to get the functionality back is to exit Unity and reload the scene. Everything then goes back to normal.... until I do a build again!? This may well be a Unity issue, I'll be asking kindly on their forums too, but would appreacite any advice or if anyone else has experienced these kinds of UI interaction problems with a Quest Build? Thanks in Advnace Andi
Using OVRInputModule with 2 controllers.
Hello. I am trying to figure out how to use the OVRInputModule in my game with 2 controllers. I want to have 2 laser beam that comes out of each controller, very similar to how the UI works in the dashboard. However, I can only get one laser to move and be attached to its controller at once. This is my hierarchy. And these are the details of my EventSystem In the OVRInputModule, if the RayTransform and Cursor are set to the ConquestOVRLaserPointer that is a child of the RightControllerAnchor, the laser attached to the right controller will move when the right controller does, but the left laser will not move. If, on the other hand, I set the RayTransform and Cursor to the ConquestOVRLaserPointer that is a child of the LeftControllerAnchor, then the laser attached to the left controller will move when the left controller does and the right laser will not move. Since there is only one on RayTransform and Cursor slot, how do I get it so that the lasers attached to both controllers can move at once? Thanks for any help John Lawrie
