You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v53 on the Quest 2 is causing flashing pixels, tearing and stuttering with the v53 update. Its was perfect with v51. I can midigate it a little by turning the resolution down and it does seem to go away with FFR off but I cant run it like that.
I KNOW for a fact that the issue is realated to something thats changed in v53 since I was able to downgrade to v51 when it was on the PTC but now v53 is official and can downgrade anymore. It happens with v54 ptc also. These graphical issues make alxr not usable at any useful resolution. I wish the Discord was still up so at lease i wouldnt feel like im alone with these issues :(
The text was updated successfully, but these errors were encountered:
@korejan Thank you!!!!! Reading that made my day Korejan! Truth is you got the best software out for AR and mixed reality and we really appreciate the work you put into these releases.
If you have trouble reproducing the problem, turn up your resolution to 125 or 150 percent depending on your system power and try with FFR on then try it off. There is some info in the v54 megathread on metas offical PTC forum posts that I dont understand in the last few pages but I know you'll know what they are talking about. That MAY help, but again, im just an end user so this side of things is not my bag.
v53 on the Quest 2 is causing flashing pixels, tearing and stuttering with the v53 update. Its was perfect with v51. I can midigate it a little by turning the resolution down and it does seem to go away with FFR off but I cant run it like that.
I KNOW for a fact that the issue is realated to something thats changed in v53 since I was able to downgrade to v51 when it was on the PTC but now v53 is official and can downgrade anymore. It happens with v54 ptc also. These graphical issues make alxr not usable at any useful resolution. I wish the Discord was still up so at lease i wouldnt feel like im alone with these issues :(
The text was updated successfully, but these errors were encountered: