Quest 3 - Airlink freezing and stuttering/shaking after any small movements
I've recently bought a Quest 3 and it works fine in most games, however a couple of them seem to have a constant issue: After about 5-10 minutes of comfortable playing through Airlink the game would suddenly freeze and, upon waking up, the tracking becomes very shaky and extremely sensitive to the smallest of movements. Turning the headset off and on temporarily fixes the problem, but after a few seconds the image freezes again at which point the problem repeats up until the game is restarted. Turning off Asynchronous Spacewarp in the debug tool seemed to have fixed the issue completely in TWD Saints & Sinners, however it is still occuring in Into the Radius regardless if ASW is turned off or not
Quest Link via cable low performance after update
I'm really upset with the performance of Quest software nowadays. I was playing Alyx, Metro and Beat Saber a while ago with zero issues (recommended settings and 600mb bitrate on debug). For some reason, after some updates, I'm getting unplayable stutters even on the Link menu while using the headset. Nothing changed on my hardware. I'm still playing all my flat games on 2k with high fps, so why they reduced my recommended settings and I'm getting really bad fps even on 0.7x? RTX 3080, RYZEN 9 6900HX, 32GB RAM, WIRED LINK 3.2 GBPS
Quest Build Stuttering + Peripherals Black after Oculus Update ( Unity )
Hello. I am using Unity 2019.3.15 to create a Quest build. I'm new to this. But I have meticulously followed all the suggested configurations and settings before proceeding with programming. After practicing on smaller stuff and after 3 full days of starting and then realizing I needed to start over, I got everything finally working smoothly. As I work, I test the build by staying connected to my PC via USB and via Link. Then sometimes I build to the headset just to double check everything. I was happy with my build and even tested basic functions on friends and family. Everything was working perfectly but then Oculus pushed an update through and then my next build became stutter/juddery. The field of view is also much smaller. The only changes I made in Unity were to the UI, the audio and to some capsule colliders for improvements so I don't know what could possibly be the problem. I was confused about the update because I'm almost certain that I already did an update a short time ago. One for desktop software, and maybe twice for my headset. Could it be that because I am building via Link connection that it's causing a problem with my Quest build? Please help, I was supposed to present today and now I'm stuck. More details about my scene... I have 2 video clips that play on awake in different locations of the scene embedded into screen models as textures. Basic terrain with a few trees painted with Poly brush. VERY minimal animated characters for atmosphere. I don't have a very good understanding of shaders and textures so I wonder if, I've used some incompatible asset or something.Low poly-count indoor scene with performance issues while looking outside the room (weird pattern)
Hey there, Sorry, couldn't make a good title for this long post. To start, I have a discussion (https://forums.oculusvr.com/community/discussion/62088/experiencing-some-lags-stutter-in-games-apps-laptop-gtx-1060-is-hardware-the-problem#latest), that explains my problems while playing the Oculus Home app and Robo Recall. The lags/stuttering do not make them unplayable but is noticeable. The takeaway could be that my hardware is, in fact, the problem. Here's the build (if you didn't see in the other post): It's a Laptop i7 7700 HQ 2.8 GHz 32 GB RAM GTX1060 GPU headset pluged in usb 3.0 (but says 2.0) - using an usb 3.0 extension because the usb close to the HDMI is under an Asmedia controller with compatibility issues 1 sensor in usb 3.0 1 sensor in usb 2.0 it was expensive (I'm in Brazil) Secondly, what I've already tried: Set windows settings to performance over quality Disabled USB power saving in windows settings Went to Devices panel and turned off USB power saving option in every USB device possible Disabled windows defender while playing/working (I have no other anti-virus) I have no recording apps or anything with overlay issues that I've read about Disabled game overlay in GeForce Experience Set performance option in Nvidia Cotrol panel Now talking about Rift and Unity. I read about performance and optimizations and first I have to say that I did nothing about that in this scene that I'm going to show. I wanted to understand the need for optimization before optimizing. In unity docs they say you can get away with from 1 to 2 million vertices in view. I setup a scene with a maximum of 56k vertices in view. Why? Because I had one with 250k max and the stuttering was really noticeable, so I did cut a lot of heavy things. So how the scene is setup? Unity 2017.3.1f1 Only baked ligthmap No realtime shadows, because no realtime lights 1 non-directional lightmap of 4096x4096 (better than many of 1024x1024?) Forward rendering - tried with deferred too, with the same result Stereo rendering mode - tried single pass and multi pass, with the same result Two baked reflection probes (box projection) 6 point lights (baked) 1 directional light (baked) Camera (center eye anchor in a OVRCameraRig prefab) - not using Skybox No atlas for the textures used (the ground and one wall paper on the wall) - image below Too many materials? Lighting settings: Player settings: Here tried GPU Skinning, Graphics Jobs, with same results. Model hierarchy: The selected object has a mesh renderer as it's children. (the grouping can affect batching?) So, let's see the problem in video. I have three in youtube (linked below) In Unity without the profiler (with stats): https://youtu.be/-RjO3wu6l3Y In Unity with the profiler (with stats): https://youtu.be/lq7bQodU_Ho With a build (Fantastic quality) https://youtu.be/umb17rUJCOk I tried with lower quality, but the problem persist. When I crouch and stand up it happens too (simulating the pattern shown in the videos above). No problems when the view is restricted inside the room. When I look "outside" through the glass door (transparent material with reflections) the problem occurs. Disabled Static and Dynamic Batching once to see what happened, and the stutter happened on the glass door, instead of when moving the head to face the table. I read that the unity Skybox is a problem. I supose I'm not using it. I really want to understand what is going on here, before I try to optimize without knowing what to. Again, too low-end hardware?
