Frequent micro stuttering in Meta Quest 3
Hello, I've owned a Meta Quest 3 for a few days now. Since yesterday, I've noticed a "micro stuterring" problem that appears when I use the headset in standalone mode. This is the same problem described by pan.c.kaplanis and Renegade_R in this topic (see page 2 and following) : https://communityforums.atmeta.com/t5/VR-Experiences/Some-Quest-3-standalone-games-are-lagging-stuttering/td-p/1100483/highlight/true/page/2 Nevertheless, I'm making a new topic because the previous one was initially about Beat Saber (but it's been diverted to Home), and because the problem is marked "Solved" whereas it's not solved at all in my case. Problem description: In the Home application and standalone games, at certain moments, for example when I crouch or strafe from right to left, "micro stutters" appear. This is very visible on the Home application interface, but you can see it by looking at the background too. It's as if for a very short moment (1 frame) the position of the headset shifts, giving the impression that the image is hopping, before returning to its initial position. It happens very quickly, and the shift is not huge. Nevertheless, the repetition of the phenomenon makes it noticeable. The problem appears when I crouch or strafe to the sides. It doesn't appear every time I do these movements, but it happens regularly. I have the impression that micro stutters appear more often when I'm pointing at something with the controller, and/or when the boundary walls are displayed. The problem is extremely noticeable on nearby objects, but it also affects distant scenery. Unfortunately, when recording video, the problem simply doesn't appear, or appears too subtly. In any case, I'm not able to perceive it on video. I'm convinced that this problem wasn't present 3 days ago when I unpacked my helmet. I think it appeared with upgrade v59 as I found other reports of stuterring appearing at that time. I'm now on upgrade v60 but the problem persists. It's annoying because using the headset is generally smooth, but these micro stutters are so recurrent that they're ruining my life in Quest 3. Incidentally, I have the impression that the problem is also present in PCVR with the Link cable. I have the impression of seeing these micro stutters when I crouch in Half Life Alyx. But here I'm less sure, because I know that in PCVR, problems can come from many places. I really hope that an origin for this problem can be found, as all the posts I see on the net suggest that the problem appeared with update v59 and hasn't been fixed since. I can hardly use the headset at the moment, as this problem is really getting on my nerves.Solved19KViews1like16CommentsObtaining User ID issue after v59, still works on v57-
We cannot obtain Oculus Platform UserIDs on headsets running software v59. Unity integration Oculus.Platform.Users.GetLoggedInUser() returns a user object with an ID of 0. Headsets on earlier software versions (v57 and below) can successfully obtain the User ID. We have access to necessary Platform Features through the meta developer dashboard.Solved2.9KViews6likes6CommentsQuest3 v59 stop retrieving logged user id
Hello, We are using quest3 for the development of a multiplayer game with colocation in unity 2022.3.4. With the update of the quest for v59 the function Oculus.Platform.Users.GetLoggedInUser starts retrieving 0 as result, without any error. Our app has the UserID and User Profile feature granted and we are getting the right values in quest with v57. We already open a ticket in the Developer Support and int Meta Store Support. but they are unable to resolve the issue and redirect us to the forums and documentation. None of those are effective. How can we solve this issue in v59? Thanks773Views2likes1CommentTest users stoped working v59
We are developing a colocation game for quest3 and some off them start updating to version 59. The users assign to those quest3 can´t loggin getting 0 as userId and OCApiEXception with the code 190 when requesting the user proof. We factory reset some quest3 without the actualization to v59 (v57) and use the same users in those equipments and they work just fine. What is the workaround?3.9KViews3likes1Comment