Passthrough Over link Fragmented and Slow
Hello, I have been working on a project using Unity 2022.3.7f and Meta All in one SDK 59.00 with passthrough. Everything in development has been fine and passthrough worked perfectly up until a few days ago the passthrough with no changes now is pixelated and slow. I have tried multiple headsets(2x Quest 3), link cables, ports, reinstalling meta quest link, reimporting all assets. I believe that this is because of a update with meta quest software so I updated the All in One SDK to 68.0 and am getting this error stuck at this point. Tried it additionally on a blank project with the 68.0 MAIO working and it still gives the poor passthrough performance. I AM BEGGING FOR HELP.1KViews0likes3CommentsBuffer-based Haptics are broken for Quest 2
Haptic controller vibrations are a crucial tool for creating game immersion. While simple "buzzes" (a constant vibration amplitude for a specified duration) can be serviceable, modern controllers allow developers to play custom waveforms through the controllers, such as sawtooth waves, sinewaves, and even Audio Clips. This adds texture and nuance to the effect, and is the superior way to play haptics in 2022. After much trying, it appears to me that the buffer-based haptics are fully broken for Quest 2 controllers in the Oculus integration for Unity. I have tried in 3 ways: Using the Unity generic XR system: byte[] samples = new byte[1000]; // This would be loaded with samples to create a custom vibration waveform var handDevice = InputDevices.GetDeviceAtXRNode(hand == Hand.right ? XRNode.RightHand : XRNode.LeftHand); // Pass the buffer into the controller if its "haptic capabilities" say that it supports buffer-based haptics if (handDevice.TryGetHapticCapabilities(out var capabilities) && capabilities.supportsBuffer) handDevice.SendHapticBuffer(0, samples); Using Rift S and Quest 1 Touch controllers, the above code runs successfully. Using Quest 2 and Touch 2 controllers, "supportsBuffer" is false on the capabilities class, and the samples cannot be successfully sent. I know that it is incorrect that the Touch 2 controllers do not support the feature, as I have in a few instances been able to send a buffer to Touch 2 controllers using the below method. Using OVRHaptics: var ovrHapticClip = new OVRHapticsClip(myAudioClipToTurnIntoVibration); var channel = OVRHaptics.RightChannel; channel.Queue(ovrHapticClip); The OVRHaptics class has a function for sending a haptic buffer in through a "channel" (controller). I can actually get this method to work in a test scene. However, it requires me to put the OVR plugin in a legacy setting (Oculus/Tools/OpenXR/Switch to Legacy OVERPlugin (with LibOVR and VRAPI backends) ). If I am not in this setting the function does nothing. In another project, if I set the project to this setting and try to send the haptics buffer, the engine gets stuck in an infinite loop. According to what I can find online, the OVRHaptics class is intended to be deprecated, anyway, so it doesn't seem like a good solution. Using OVRInput: My understanding is that OVRInput is the modern, sanctioned way of sending haptics to Oculus controllers without going through the generic Unity XR system, and they contain a method for a "simple buzz" (amplitude and duration parameters only) via OVRInput.SetControllerVibration. However, they seem to lack any functionality for sending in a custom buffer, unlike the deprecated OVRHaptics. I would love any advice regarding ways I can get this feature to work. I figure I'm either wrong about some of my conclusions above, or the feature is fully broken at the moment -- either way, I'd love to know. Thanks in advance for your help!3.1KViews13likes1CommentOculus Avatar SDK broken model meshes
Hello, i am making a game with Photon PUN 2 and oculus avatar sdk (from 1.30 integration in the store), and when i play, 1/8 times i play i get broken models, they look allright in the lobby, never break, when i join the game and the local avatar is created, it gets broken some times, some times it works allright. Im using VRTK too.459Views0likes0CommentsAngular Velocity, Angular Acceleration Broken? (has anyone gotten this to work on the latest unity?)
I'm using 1.13.0 and my output for Angular Velocity is always 0,0,0. I tried using the example Room and the grabbable and grabber also output 0 as well. I am not sure what to do but from older requests it should be outputting as a Quaternion but other reports say it should be a Vector 3? I am not sure how to get it working?2KViews0likes9Comments