Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v53 on the Quest 2 causes flashing and artifacts with foveated rendering #90

Open
Plato115 opened this issue May 15, 2023 · 4 comments
Open

Comments

@Plato115
Copy link

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 :(

@Plato115
Copy link
Author

Please someone help or at least give it a try so I know its not just me

@korejan
Copy link
Owner

korejan commented May 17, 2023

@Plato115 I'll have a look when I get a chance

@Plato115
Copy link
Author

@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.

Again brother, THANK YOU

@Plato115
Copy link
Author

Plato115 commented Jul 7, 2023

looks like the new server has fixed it. testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants