Oculus Link (wired) crashes randomly with all drivers after 566.36 (not
included). Just observed the crash with 576.02. Reverting to 566.36
solves the issue and crashes NEVER happen. However, with 5090 I can't do
that. Specs:5090, 64GB RAM, 9800X3DLa...
Just look at the screenshot. WTF is this and how do I fix it? Same
problem is reported all over Reddit: 1.
https://www.reddit.com/r/OculusQuest/comments/18m8bvr/why_does_oculus_pc_app_show_duplicated_refresh/2.
https://www.reddit.com/r/oculus/comment...
So, I have recently discovered a huge potential problem. I started to
notice that my Quest 2 won't charge - even though it would show that
it's charging both by LED and the battery icon. After using the Link, I
always sit the Quest 2 down and power i...
Yes. Launch PowerShell (with admin rights).Paste and run this: reg add
"HKEY_CURRENT_USER\SOFTWARE\Oculus\RemoteHeadset" /v "numSlices" /t
REG_DWORD /d "3" /fAfter that, you can change the number of slices
via:WIN+R -> regedit -> navigate to
HKEY_CUR...
That's...not really true? The camera placement is not relevant, as
controller camera tracking works in the same way it did back in CV1 days
(if we disable all the AI hand pose tracking on top). The only
difference is that the cameras are now mounted ...
Can't confirm the @maxstep report, v68 PTC - Beat Saber starts just fine
in Meta Quest Link OpenXR environment. Whatever issue @maxstep
experiences is not related to v68 - or is not as simple as that.
No update visible - and I'm on 60.0. Interestingly enough, on Meta's
Germany page (I'm in Germany) the build notes only appear up to 60.0
version. Is there some kind of regional updates lock???
This is completely false information. As outlined in the post, turning
the headset completely off - or putting it on standby - doesn't make it
charge. It stays at whatever the charge was before and doesn't move. As
I've outlined, it even displays "10...
