Frequent micro stuttering in Meta Quest 3

I don't have beat saber unfortunately, so can't compare, but my feeling was that the frame dropping was due to other things going on in a game. When the stutter consistently happens at the same time, I would think that there are other things consistently happening at the time as well. I had believed in the past that starting a new sound playing was one of the things that could cause a stutter. So striking an object or shooting pistol, whatever, if it caused a new sound to be played, it could cause stutter. Sound of course is only one example. Reading something from flash could be another. It could be just about anything.

I'm guessing all these apps make use of meta API calls to do most things, so a game might start having issues even though the game itself was not updated. So playing sounds may be fine in a game with one version of the quest OS and cause a stutter in the next version (just guessing, but I'll bet I'm close).

It is a difficult problem because the game developer has little control over it, and meta can't debug every issue with every game on every update they make. Fingers crossed that it is something obvious that they can fix.

For the record, I was really surprised by the quest 3. I thought I was going to see a marked quality increase to things like frames dropping in games when compared to the quest 2, but when I first fired up the 3, I instead found that it stuttered just as much in the same games as the quest 2 did. I wonder where all the extra processor power is going ...

Hey, did you ever figure out the source of your problem? I too started noticing objects kind of jittering around when turning my head. A few of the scenarios I've noticed are:

• The universal menu or anything in a high contrast scenario. When I was facing a really bright direct sunlight window. Some thin sheer curtains were drawn and the blinds were closed but it still left really bright diffused light. The curtains would glow white and would surely be clipping in a camera. In this scenario the universal menu (among other things) would jump around a lot when turning my head. Facing away from the window fixed that particular issue.
• I had a room setup with furniture, wall art, etc. Later when I came back the boundary was all off and I redid the boundary. The room stuff was still there but all out of place now. It seems like clearing the room data reduced a lot of stuttering.
• I still get some jitters/stutters/micro jumping around here and there. It doesn't happen every time but usually happens when the universal menu loads for the first time and I move my head around, when I have "Glanceable Boundary" turned on and I glance down to illuminate it, and during games when "things happen" scene change, lots of sudden movements of things, etc.

I am also experiencing this exact issue using version 60.0 on my Quest 3. It is most noticeable on the universal menu but is also slightly noticeable on the virtual environment and in some standalone games. It is extremely noticeable on close-up objects when I stream PCVR games wirelessly, through any of the PCVR streaming apps (Steam Link, Air Link, or Virtual Desktop).

It is like a kind of rubber band effect on 3D objects in the game space. The objects seem to skip a frame when moving the headset side to side, and then instantly snap back in place. I tried recording the phenomenon, but it doesn't appear at all in the recording for some reason.

I've been updated to the latest the whole time. Mine kind of stopped doing it though. A little jitter/stutter here and there but nothing like the height of the issue. I'm not really sure why. 

Guys, I also was experiencing stutters like the kind of micro jumps, a judder now and then in the game Lone Echo 2, albeit for apparently a whole different reason and of a different kind. I am using the Oculus cable and I have solely since I bought my Quest 3. Now, this occasional judder drove me nuts. After having read a hundred posts to no avail I had an idea cause someone mentioned switching off HAGS (hardware accelerated GPU scheduling) in a post and the author of UEVRI (Unreal Engine VR Injector) also mentions that you first need to switch of HAGS before VR injection. What HAGS does is it says to the GPU to prepare a frame like a CPU normally does and then the GPU renders it. This is quicker and less laggy, the latency is lower and may accelerate your games when the CPU is weaker. However it can break things as the GPU now has more work to do. Lo and behold, I switched HAGS of, restarted the rig and the stutters are 90 per cent gone! That being said, the textures sometimes do not load completely and are low res and you have to fly close and zoom in on the area for the textures to sharpen, I guess it is bad latency, or, correctly speaking, it is more latency. But the most annoying thing is gone you Guys. That is the main thing. Cheers ,

I receive my Quest 3 the last week and I am sufering the micro stuttering continuously in the standalone mode. I am not downloading anything in second plane. The problem occurrs always a lot of times each minute of use. I don't have activated any low comsumtion mode or anything like that.

My understanding... u Can't just use VD for everything.  Everything has a type of RUNTIME it uses.  VD is OpenVD or VDXR I forget what it is now.  I did notice in the Meta Quest software it would say restore back to Meta runtime.  So it recognized VD was assigned.  SteamVR may do that too.  But if the game is made to use SteamVR I saw that it will just AUTO run.  Then u have to competing runtimes and the games will crash or not even start.  So I don't get how running VD is even an option.  This is all NEW to me btw too.