

Flyingfish
Members-
Posts
113 -
Joined
-
Last visited
About Flyingfish
- Currently Viewing Forum: Virtual Reality
- Birthday 08/06/1984
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
OpenXR Toolkit 1.3.8 still usable as stand alone (not Steam)
Flyingfish replied to StratosFalcon's topic in Virtual Reality
Thanks for the reply I've sent you a message with hopefully the correct information/files -
OpenXR Toolkit 1.3.8 still usable as stand alone (not Steam)
Flyingfish replied to StratosFalcon's topic in Virtual Reality
Thanks, it's interesting that you don't get stutters when using meta link but I do, we have nearly identical systems. Do you use ASW or is your FPS always at the headset refresh rate? -
OpenXR Toolkit 1.3.8 still usable as stand alone (not Steam)
Flyingfish replied to StratosFalcon's topic in Virtual Reality
It worries me that I need open XR toolkit turbo mode to get smooth performance in DCS. If open XR toolkit stops working with DCS it'll be unusable for me. Does anyone know if this is a problem for all headsets or just meta ones? -
OpenXR Toolkit 1.3.8 still usable as stand alone (not Steam)
Flyingfish replied to StratosFalcon's topic in Virtual Reality
I'm completely reliant on turbo mode to hugely reduce stutters on DCS. Open XR toolkit works very well with DCS. Using a quest pro. -
Stuttering when watching sideway in cockpit dilemma
Flyingfish replied to Thegino's topic in Virtual Reality
If you're using a quest headset try using open xr toolkit and setting turbo mode to on -
VR Quest 3 assets not rendering for both eyes correctly
Flyingfish replied to Lt.Salty's topic in Bugs and Problems
I'm getting this as well. I've only noticed around Berlin. Using a quest pro -
Apologies for the slightly off topic question but I see you've upgraded to a 5080 and you're using Meta link. Are you having any problems using Meta link and the new GPU? The 50 series GPUs aren't officially supported yet by Meta so I wasn't sure if they'd actually work
-
I've had problems with preset k but I managed to get J working by swapping the DLSS file to the previous version (the one with preset J but not K) then selecting preset J
-
Has anyone tried using setting K on a Quest headset using the link Cable? When I do this it forces my headset to 72hz
-
Hi, As per the title my Quest pro is stuck at 72Hz when using Meta link. The Meta link app shows 80Hz and I can change it to different refresh rates on the app but despite that it's still stuck at 72Hz. The problem occurred after I updated to the latest DLSS files using DLSS swapper then I downloaded DLSS tweaks, ran the config and changed the global DLSS setting to K. Ever since making these changes it's been stuck at 72Hz when using PCVR. When I use virtual desktop I can use other refresh rates. Any ideas what I could to to fix it? I really don't like 72Hz, or using virtual desktop Things I've tried Repair Oculus app Roll back to earlier Nvidia drivers Roll back to earlier DLSS files using DLSS swapper Run Disablenvidiasigoveride in DLSS tweaks
-
I tried QVFR with VD and with oculus link cable. There seemed to be less latency when using VD, there's still a bit of a delay with the resolution catching up with where I'm looking but it appeared to be less noticeable than it is when using the link cable. Strangely though my GPU usage is slightly lower when I don't use QVFR at all. I didn't do any in depth testing, I only used task manager to look at GPU utilisation, but when I sat on the runway at Nellis in an F14 the GPU utilisation was 71% with QVFR and 68% without.
-
And if I can get enough of a benefit from QVFR I might be able to avoid dropping into SSW. I'll give it a try and see how it goes
-
I'll give VD a try but unfortunately I don't really like it because I find the ASW to be much worse than when using Meta ASW
-
Does anybody know if there's a way to reduce latency with eye tracking on the quest pro? When I use QVFR I'm able to see the resolution change when I move my eyes
-
Unfortunately this is a problem with RT40xx series cards. Meta have known about the problem for 2 years but haven't fixed it. It might be worth submitting a bug report to meta in the hope that if they get enough they might fix it