Grift-06 Posted May 9, 2024 Posted May 9, 2024 Hi everyone, I just bought a new VR headset to start, the Meta Quest 2, it’s amazing, good feeling etc… But with the Mirage F1 I have a lot of issue to get something clean, the cockpit is shaking a bit, very hard to see things, it’s like flashing. Anyone has the same issues and have some advices to optimize the VR performance to get something playable in VR ? Thx ! Here is my setup: i5-12400F RTX 3060 ti 8gb 32 Gb Ram Quest 2
diego999 Posted May 9, 2024 Posted May 9, 2024 Try these. I have a similar PC, but with an older CPU (10400), and I'm able to maintain 72fps most of the time, except when on the ground in crowded bases or flying over big cities. 1
Grift-06 Posted May 10, 2024 Author Posted May 10, 2024 11 hours ago, diego999 said: Try these. I have a similar PC, but with an older CPU (10400), and I'm able to maintain 72fps most of the time, except when on the ground in crowded bases or flying over big cities. Thank you very much for this answer! Is the tray tool mandatory to have better performance or not ?
freehand Posted May 10, 2024 Posted May 10, 2024 (edited) 45 minutes ago, Grift-06 said: Thank you very much for this answer! Is the tray tool mandatory to have better performance or not ? You can use oculus debug tool same difference for most setting eg:Fov multiplier e,t,c Location C:Programs, OculusSupport, oculus-diagnostics or similar place. Edited May 10, 2024 by freehand
diego999 Posted May 10, 2024 Posted May 10, 2024 12 hours ago, Grift-06 said: Thank you very much for this answer! Is the tray tool mandatory to have better performance or not ? One of the most critical settings is to limit the fov. Quest 2 has a noticeable portion of the screen you don't even see but it's being rendered anyways, wasting gpu power. Cutting that part out will give you additional performance. It depends on the person. For me at 0.9 I can't tell the difference. At 0.85 I start to notice the black box if I try very hard. At 0.80 I clearly see it's there. Try different values to see what's best for you. If you don't want the tray tool, you can use the inbuilt debug tool as the guy above me suggests.
Qcumber Posted May 10, 2024 Posted May 10, 2024 On 5/9/2024 at 6:15 PM, Grift-06 said: Hi everyone, I just bought a new VR headset to start, the Meta Quest 2, it’s amazing, good feeling etc… But with the Mirage F1 I have a lot of issue to get something clean, the cockpit is shaking a bit, very hard to see things, it’s like flashing. Anyone has the same issues and have some advices to optimize the VR performance to get something playable in VR ? Thx ! Here is my setup: i5-12400F RTX 3060 ti 8gb 32 Gb Ram Quest 2 In addition to the other suggestions you might want to try quad views foveated rendering used in fixed mode. A big performance boost. https://github.com/mbucchia/Quad-Views-Foveated 1 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.
Recommended Posts