slughead Posted December 25, 2024 Posted December 25, 2024 Yup. See how you get along with that. If you're still struggling to stay at 72fps, drop it down to 1.2x. You won't be able to stay at 72fps in all scenarios, especially using MSAA. DLSS will give you a lot more headroom. 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
skywalker22 Posted December 25, 2024 Posted December 25, 2024 Now I have constant 72 fps thx so much mate, really appreciate your help.
slughead Posted December 25, 2024 Posted December 25, 2024 Just now, skywalker22 said: Now I have constant 72 fps thx so much mate, really appreciate your help. Merry Christmas. Don’t forget to order a Slugmouse Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
skywalker22 Posted December 25, 2024 Posted December 25, 2024 7 minutes ago, slughead said: Merry Christmas. Don’t forget to order a Slugmouse Merry Christmas to you two. Why is the slug mouse good for? I heard about it before. found it
slughead Posted December 25, 2024 Posted December 25, 2024 Just now, skywalker22 said: Why is the slug mouse good for? I heard about it before. It allows you to turn your hands into mice to point at cockpit controls and click without fumbling around for your normal mouse. It's currently on a 25% Christmas discount. Full details here: 1 Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
milit Posted December 27, 2024 Posted December 27, 2024 Hi all! I'm totally new in VR having OQ3. I spent a significant time to be acquainted with subject and tunning my system to get the quality/performance balance and now it is almost fine. But one detail I didn't manage to defeat - the far objects looks... blurry? not clean? Any tips, guys, how to make the whole picture clean? I use MSAA x4, no FSR. Config in signature. Thanks! =WRAG=345 R7 5800X @ 4,8 GHz; DDR4 64Gb RAM (+32Gb swap); Radeon RX 6800 16Gb; 3840x2160; Oculus Quest 3; Win10-64
Jive Posted December 28, 2024 Posted December 28, 2024 On 12/27/2024 at 11:25 AM, milit said: Hi all! I'm totally new in VR having OQ3. I spent a significant time to be acquainted with subject and tunning my system to get the quality/performance balance and now it is almost fine. But one detail I didn't manage to defeat - the far objects looks... blurry? not clean? Any tips, guys, how to make the whole picture clean? I use MSAA x4, no FSR. Config in signature. Thanks! There can be a lot of tweaking to find the performance you want and some personal preferences My advice is to open the Meta link software and increase the resolution slider to max and set 72hz Depending on if you're using a link cable, wireless via Meta Link or wireless via Virtual Desktop there'll be different bitrate settings available to you. Higher is sharper although may introduce some latency. I couldn't see your config, sorry I can't be more specific with settings but I like DLAA (DLSS is a little too blurry imo but it's viable) and then being as modest as possible with other settings to save performance. Another option is using OpenXR Toolkit to add some simple fixed foveated rendering or using Quadviews which works in a similar way with finer control. With Quadviews you can choose to downsample the edges of your view and increase the resolution of the middle, if you wanted to. Quadviews is more CPU intensive than FFR in OpenXR toolkit iirc.
Flyingfish Posted January 27 Posted January 27 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 RTX 4090, AMD 9800x3D, 64GB Ram
Qcumber Posted January 27 Posted January 27 10 minutes ago, Flyingfish said: 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 Yes. It is annoying. Particularly as dcs shadows and lower resolution can cause "flickering". There must be away. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
slughead Posted January 27 Posted January 27 15 minutes ago, Flyingfish said: 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 Have you tried Virtual Desktop? I think someone said it's faster. Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now! Slugmouse Demonstration Video
Qcumber Posted January 27 Posted January 27 2 minutes ago, slughead said: Have you tried Virtual Desktop? I think someone said it's faster. VD is a bit faster but still noticeable. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
Flyingfish Posted January 27 Posted January 27 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 RTX 4090, AMD 9800x3D, 64GB Ram
Qcumber Posted January 27 Posted January 27 31 minutes ago, Flyingfish said: 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 Yes. SSW is terrible compared to ASW but VD handles fps lower than refresh rate better than meta. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
Flyingfish Posted January 27 Posted January 27 32 minutes ago, Qcumber said: Yes. SSW is terrible compared to ASW but VD handles fps lower than refresh rate better than meta. 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 1 RTX 4090, AMD 9800x3D, 64GB Ram
Flyingfish Posted January 28 Posted January 28 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. RTX 4090, AMD 9800x3D, 64GB Ram
muzica9 Posted February 25 Posted February 25 Any idea why I can't activate eye tracking in Virtual Desktop? I have eye and face tracking enabled, and eye tracking works with the Link Cable. I just don’t have the option available to check it. missing from the menu
Qcumber Posted February 25 Posted February 25 Looks like you are using an old version of VD. The latest is 1.33.4 (5/2/25). I would advise updating and seeing if that helps. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
muzica9 Posted February 25 Posted February 25 it's latest from meta store. photo is just reference from mbucchia gifhub
diamond26 Posted February 25 Posted February 25 are you using VDXR option in VD stream app? MAIN SYSTEM SPECS: MSI PRO Z690-A WIFI DDR4, Intel Corei7-12700K @ 5.0, 64Gb RAM Kingston KF3600C18D4/16GX, EVGA RTX 3080 FTW3 ULTRA GAMING 12GB, Samsung SSD 970 EVO Plus 1TB, Virpil T50CM3 Throttle, VKB Gunfighter MkIV Ultimate with 20cm extension, VKB T-Rudder MKIV, Quest Pro Laptop SPECS: Alienware X16 R2, Intel Core Ultra 9 185H, RTX 4090 mobile 16GB, 32GB LPDDR5X, 2TB Micron NVMe SOFTWARE: Microsoft Windows 11
muzica9 Posted February 25 Posted February 25 (edited) 2 hours ago, diamond26 said: are you using VDXR option in VD stream app? yes. everything configured like here https://github.com/mbucchia/Quad-Views-Foveated/wiki/Meta-Quest-Pro le: after unchecking and checking eye tracking and face tracking again, I managed to get it working. By the way, that option is now called 'Forward Tracking Data to PC' nothing specifically related to eye tracking anymore. Back to link cable... I’d also like to know how you guys get rid of the annoying on screen message when using the Link Cable: 'Controllers lost tracking,' which stays forever." Also, the controllers seem to lose tracking or have incorrect tracking most of the time. I’m not using them much, only to switch to the desktop and most of the time, I can't use them. Quest is on v72 firmware. Edited February 25 by muzica9
Qcumber Posted February 25 Posted February 25 3 hours ago, muzica9 said: Controllers lost tracking,' which stays forever." Mute all notifications in the headset. There is a single tab in the quick access menu. PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.
muzica9 Posted February 25 Posted February 25 Yeah, I figured that out. The only remaining problem is the controller tracking/wrong position. If the headset or controller goes to sleep, everything goes to hell—the controller pointer ends up all over the place and i can not acces windows. This is driving me crazy, and I don’t know how to solve it. I’ve done multiple factory resets and tried pairing/unpairing the controllers, but the issue persists. It sounds like a firmware or software bug.
VR Flight Guy in PJ Pants Posted February 25 Posted February 25 Some how, I think I have lost eye tracking. I tried recal, but it always says the result is not satisfactory. I Fly, Therefore I Am. One cannot go around not saying "Thank you" every time these days, can't you? YouTube: https://www.youtube.com/channel/UCc9BDi-STaqgWsjNiHbW0fA
Tea-Pig Posted February 25 Posted February 25 13 hours ago, muzica9 said: yes. everything configured like here https://github.com/mbucchia/Quad-Views-Foveated/wiki/Meta-Quest-Pro le: after unchecking and checking eye tracking and face tracking again, I managed to get it working. By the way, that option is now called 'Forward Tracking Data to PC' nothing specifically related to eye tracking anymore. Back to link cable... I’d also like to know how you guys get rid of the annoying on screen message when using the Link Cable: 'Controllers lost tracking,' which stays forever." Also, the controllers seem to lose tracking or have incorrect tracking most of the time. I’m not using them much, only to switch to the desktop and most of the time, I can't use them. Quest is on v72 firmware. I used to have this controller problem until I discovered you can turn them off by holding the menu button on each controller for about 10 seconds. I've not felt the need to turn them back on for nearly a year now. R7-7800x3d, Asus TufRTX4090, 32G Corsair 6GHz DDR5, Quest Pro, Motion Rig (home made), Sidewinder FFB Stick, now trying the Moza but might go back to the Sidewinder, Crosswind Pedals
muzica9 Posted February 26 Posted February 26 (edited) 8 hours ago, Tea-Pig said: I used to have this controller problem until I discovered you can turn them off by holding the menu button on each controller for about 10 seconds. I've not felt the need to turn them back on for nearly a year now. than how do you access windows desktop without taking helmet off? Edited February 26 by muzica9
Recommended Posts