Steam + Oculus broken in VR - Only first frame rendered
See original GitHub issueRepro node . -x webvr https://possible-bench.glitch.me/
aframe master from november.
Probably requires an openvr lib update - @modulesio
Will look at this tomorrow.
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
How to (not) solve SteamVR framerate issues on Windows 11
Let me tell my experience in trying to solve the framerate issues with SteamVR in widows 11 when I am using Oculus Quest...
Read more >OCULUS QUEST 2 AIRLINK - Low FPS and Stutters on PCVR ...
oculus #AIRLINK #VRThis video will show you how to fix low FPS and stutters on some PCVR games using the Oculus Quest thought...
Read more >Link graphics vs. Virtual Desktop SteamVR? - Oculus Forum
When I use virtual desktop, and I run STEAM VR, I can get the graphics to look clear and amazing. I check video...
Read more >SteamVR - Steam Community
Grab SteamVR to access and play VR games using your HTC Vive, Oculus Rift, Windows Mixed Reality headset, or any other supported VR...
Read more >Why Is SteamVR Running So Poorly On Oculus Quest?
They all worked perfectly, but then without any warning, things began going wrong—stuttering sound, choppy framerates and a computer that could barely keep...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would try glGetError() to see if something is erroring.
Any GL call can be intercepted here: https://github.com/webmixedreality/exokit/blob/0069e1e774b8415a4c2cc4f7bd6ff375728ba57d/src/core.js#L2001
And if you gl.getError() you can find out which one, and which stack, actually errors, if it’s user code. If it’s not user code it could be something in the libopenvr binding (some different framebuffer post-update or such).
On Mon, Jan 14, 2019 at 7:33 PM Shane Harris notifications@github.com wrote:
I don’t think it was. However, I would consider this issue subsumed by https://github.com/webmixedreality/exokit/pull/787. Oculus was never officially supported before that PR.