Thank you so much for sharing your knowledge and experience! It is all about the data, and people need to understand that adjustments will be required, and it is pc specific. No solution / settings fit all! I like that you use Voice Attack for commands. How many of them have you programmed so far? As a fellow A320 pilot in the real world, I am also using VR and X-Plane to prepare for my training sessions and also a little fun once in a while! Fly safe!
All good info imho. I mainly use my QPro/rtx4090 with Link for both xp11/12 and msfs2020 and get very good results at 80Hz refresh rate with forced 45fps, asw disabled (= 40fps fixed). Main differences I've found is that I no longer see the need to use OpenXR Toolkit (now unsupported). All I do is adjust ODT pixel density in order to get the best balance of performance and cockpit clarity. For me, with msfs2020 and dlss/balanced this value is 1.20. Also, for me, ODT distortion = Low looks better (less edge distortions) and I leave FOV at 1.0 because anything smaller noticeably cuts off edges (which bothers me). For Nvidia CP I use the same and also change the Quality default below that to High Performance (buys an extra few fps performance/headroom without any visual effects in VR). Like you've said, everyone's systems and preferences will differ so you need to find what works best for you. Thanks again mate and cheers.
What is ODT? When I try ASW disabled, looking at the cockpit dails and moving my head I really notice missing every other frame and get a headache. Do you not have the same noticeable missing of frames?
@@majorswitcher ODT = Oculus Debug Tool (google how to find this in your Oculus program folders). If I only turn off ASW without limiting the fps (Force 45fps, asw = off) it can pick up a few stutters, depending on where I'm flying. If you still get cockpit stutters when moving your head, your graphics setting might be a bit too high.
Awesome stuff, I've been preaching something similar for years! My difference is that I can't fly without ASW, I hate seeing ghosting between frames at 36fps, hurts my eyes. I've been used to a complete smoothness at 72fps, as I was using VR native games before I started simming in VR. Also, I don't wear glasses, and my eyes are probably close the lenses, so as soon as I reduce the FOV H/V to 0.9, I start seeing black bars. Can't even go below that number, it feels like I'm looking through a cardboard box. Will certainly try your method here with SS at 2.0 and reducing the resolution in OpenXR Toolkit. Also, I wonder how this version of the toolkit will work in MSFS? Thanks!
thank you for your detailed explanation. I can get steady 36fps now in my heaviest airplane on detailed scenery. but my gpu load is around 55%. When i increase resolution, fps drops, but gpu load doesn't go much higher, it's still around 60%. how do you think that is possible? so in short: not being able to reach 36fps, while GPU is quite below 75%. this happens especially when I connect to Vatsim and there is activity on the airport. my system is a 7800X3D cpu, 4070 ti super, 32ggb ddr5 ram edit: with the 3jfps tool now i realise my cpu is the bottleneck. which is strange to me because I thought this 7800x3d would be the max and no bottleneck for a long time... edit 2: my system was limited to 60fps, because of my display settings! when I changed that to 72hz, i can achieve that fps, and in vr have stable 36 edit 3: it was all down to vsync. display monitor is back to 60Hz, Nvidia control panel for xplane has vertical sync off, and Vsync in xplane now also off. In 2D mode I now get fps over hundred, and stable 36 in VR!
What people really doesn't sometimes is that all those vsync settings are not applicable to VR. They are made to control your monitor. When we are talking about VR, the only way to have fps synchronization is by using the built in tools of the headset (Oculus Debug tool) etc. Nice to know that you achieve a good result.
@@fsprimoyes I think a lot of people who experience XPlane being so much worse then MSFS don’t realise Vsync is still on in Xplane settings (default), while they are having a 60Hz monitor. This just caps Xplane to 60fps because of the monitor.
Especially in VR , we don't need more than 45fps (1/2 90hz) or 36fps (1/2 72hz) to have a good smooth experience. It's not an action sim like DCS - IL2 etc.
@@fsprimo i’m in doubt now. But I think when vsync was on/ i was capped at 60fps on monitor, my cpu was used full and gpu less then half. Only after disabling the vsync when on monitor i could achieve 100+ fps, my cpu/gpu was balanced, and in VR forcing fps to half the framerate i could use the gpu to its full potential
Obrigado pelo vídeo, não estou usando o X-Plane no momento, mas suas dicas servem para todos os outros jogos em VR. Por acaso tem algum lugar que tenha a lista dos outros parâmetros para setar no arquivo de configuração do Oculos Debug Tool? Preciso saber o comando que desliga o Adaptative GPU Performance Scale. Valeu!
Tem sim, conforme mostrei no video, o texto do arquivo está assim service set-pixels-per-display-pixel-override 2 service set-client-fov-tan-angle-multiplier 0.7 0.7 server:asw.sim45 exit Teoricamente se eu estivesse desligando o Adaptive GPU, o texto completo ficaria assim: service set-pixels-per-display-pixel-override 2 service set-client-fov-tan-angle-multiplier 0.7 0.7 server:asw.sim45 enable-adaptive-gpu-perf-scale off exit
@@fsprimo PERFEITO!!! Obrigado mais uma vez. Com as suas dicas, consegui sair do completamente lixo, para algo próximo ao que tinha em um monitor 4k, no Automobilista 2 e no Assetto Corsa, só tive que deixar o Assynchronous Spacewarp disable, senão fica lento demais. Falta só agora ter paciência e tentar arrumar o MSFS que tb achei horrível no VR.
Olá, ,muito obrigado pelas dicas... tenho um meta quest 3 estou usando xplane 11. Não consigo usar os controles rifts no airbus A320 da Toliss. Os controles são reconhecidos normalmente no app do meta porém no Toliss não. Existe alguma configuração previa?
My quest is on developer mode, It have ADB drivers installed, so with 'scrcpy' , I'm able to send some adb commands to the headset. I created a bunch of *.BAT files that I can call via voice commands. Here the content of some of those batches . "@echo off C:\Users\myusername\Desktop\Docs\Recorder\Batches\scrcpy-win64-v2.0\adb shell setprop debug.oculus.refreshRate 80 exit"
fala comando, eu baixei esse OpenXR ai e nao tem a opçao de custom fov mesmo nao atualizando o OpenXR, sabe me dizer o por que disso? pois so essa versao 0.0.0 que funciona no XP!!
Quando eu coloco em 72hz e coloco a resolução para 1.3x, mesmo Quest link via cabo, fica quase impossível de usar o óculos. Perde muito desempenho, trava horrores na própria dela do Quest links sem nem ao menos ir pra área de trabalho pelo óculos.
Tira o bitrate de 500 pra 100 e faz um teste, vai subindo aos poucos, 100, 200, 300 etc. Faz essa alteração, reinicia o PC e o oculus pra isso aplicar.
Só de colocar o bitrate em 100 acabou com a perda de performance, mesmo no 1.3x em 72hz ... Porém meu menu do openxr não quer abrir no simulador , cada hora uma coisa 😢
Puxa Primo, que aula! Simplesmente fantástico! Parabéns pela dedicação e compartilhar esse conhecimento! Ajudou muita gente!
NOT ALL HEROS WEAR CAPES. Thank you sooooo much for your knowledge. Truly appreciate the help.
Thank you so much for sharing your knowledge and experience! It is all about the data, and people need to understand that adjustments will be required, and it is pc specific. No solution / settings fit all! I like that you use Voice Attack for commands. How many of them have you programmed so far? As a fellow A320 pilot in the real world, I am also using VR and X-Plane to prepare for my training sessions and also a little fun once in a while! Fly safe!
I almost included all commands, callouts and task sharing from my company's SOP in voice attack.
Wow great video. You talk way too fast for me, but playing at .75 speed worked perfectly.😂😂😂
I use to watch videos at 3x so I just speeded up this video a little to be able to stay in less than 30 minutes
All good info imho. I mainly use my QPro/rtx4090 with Link for both xp11/12 and msfs2020 and get very good results at 80Hz refresh rate with forced 45fps, asw disabled (= 40fps fixed). Main differences I've found is that I no longer see the need to use OpenXR Toolkit (now unsupported). All I do is adjust ODT pixel density in order to get the best balance of performance and cockpit clarity. For me, with msfs2020 and dlss/balanced this value is 1.20. Also, for me, ODT distortion = Low looks better (less edge distortions) and I leave FOV at 1.0 because anything smaller noticeably cuts off edges (which bothers me). For Nvidia CP I use the same and also change the Quality default below that to High Performance (buys an extra few fps performance/headroom without any visual effects in VR). Like you've said, everyone's systems and preferences will differ so you need to find what works best for you. Thanks again mate and cheers.
What is ODT?
When I try ASW disabled, looking at the cockpit dails and moving my head I really notice missing every other frame and get a headache.
Do you not have the same noticeable missing of frames?
@@majorswitcher ODT = Oculus Debug Tool (google how to find this in your Oculus program folders). If I only turn off ASW without limiting the fps (Force 45fps, asw = off) it can pick up a few stutters, depending on where I'm flying. If you still get cockpit stutters when moving your head, your graphics setting might be a bit too high.
Awesome stuff, I've been preaching something similar for years! My difference is that I can't fly without ASW, I hate seeing ghosting between frames at 36fps, hurts my eyes. I've been used to a complete smoothness at 72fps, as I was using VR native games before I started simming in VR. Also, I don't wear glasses, and my eyes are probably close the lenses, so as soon as I reduce the FOV H/V to 0.9, I start seeing black bars. Can't even go below that number, it feels like I'm looking through a cardboard box.
Will certainly try your method here with SS at 2.0 and reducing the resolution in OpenXR Toolkit. Also, I wonder how this version of the toolkit will work in MSFS?
Thanks!
Yes, I’m using same version for msfs and xp12
As I understand it, this is why the foveal rendering that the Varjo Aero headsets do is advantageous. IF they weren't so pricey......Oh well
yeah, no way to have one of those at home.
But remember, the software need to support this feature to be advantageous. MSFS and X-Plane doesn't have this.
thank you for your detailed explanation. I can get steady 36fps now in my heaviest airplane on detailed scenery. but my gpu load is around 55%. When i increase resolution, fps drops, but gpu load doesn't go much higher, it's still around 60%.
how do you think that is possible?
so in short: not being able to reach 36fps, while GPU is quite below 75%.
this happens especially when I connect to Vatsim and there is activity on the airport.
my system is a 7800X3D cpu, 4070 ti super, 32ggb ddr5 ram
edit: with the 3jfps tool now i realise my cpu is the bottleneck. which is strange to me because I thought this 7800x3d would be the max and no bottleneck for a long time...
edit 2: my system was limited to 60fps, because of my display settings! when I changed that to 72hz, i can achieve that fps, and in vr have stable 36
edit 3: it was all down to vsync. display monitor is back to 60Hz, Nvidia control panel for xplane has vertical sync off, and Vsync in xplane now also off. In 2D mode I now get fps over hundred, and stable 36 in VR!
What people really doesn't sometimes is that all those vsync settings are not applicable to VR. They are made to control your monitor. When we are talking about VR, the only way to have fps synchronization is by using the built in tools of the headset (Oculus Debug tool) etc.
Nice to know that you achieve a good result.
@@fsprimoyes I think a lot of people who experience XPlane being so much worse then MSFS don’t realise Vsync is still on in Xplane settings (default), while they are having a 60Hz monitor. This just caps Xplane to 60fps because of the monitor.
if a 60fps is bad in a flight simulator, o gosh, we need to get a life 😂
Especially in VR , we don't need more than 45fps (1/2 90hz) or 36fps (1/2 72hz) to have a good smooth experience. It's not an action sim like DCS - IL2 etc.
@@fsprimo i’m in doubt now. But I think when vsync was on/ i was capped at 60fps on monitor, my cpu was used full and gpu less then half. Only after disabling the vsync when on monitor i could achieve 100+ fps, my cpu/gpu was balanced, and in VR forcing fps to half the framerate i could use the gpu to its full potential
Obrigado pelo vídeo, não estou usando o X-Plane no momento, mas suas dicas servem para todos os outros jogos em VR.
Por acaso tem algum lugar que tenha a lista dos outros parâmetros para setar no arquivo de configuração do Oculos Debug Tool?
Preciso saber o comando que desliga o Adaptative GPU Performance Scale.
Valeu!
Tem sim, conforme mostrei no video, o texto do arquivo está assim
service set-pixels-per-display-pixel-override 2
service set-client-fov-tan-angle-multiplier 0.7 0.7
server:asw.sim45
exit
Teoricamente se eu estivesse desligando o Adaptive GPU, o texto completo ficaria assim:
service set-pixels-per-display-pixel-override 2
service set-client-fov-tan-angle-multiplier 0.7 0.7
server:asw.sim45
enable-adaptive-gpu-perf-scale off
exit
@@fsprimo PERFEITO!!!
Obrigado mais uma vez.
Com as suas dicas, consegui sair do completamente lixo, para algo próximo ao que tinha em um monitor 4k, no Automobilista 2 e no Assetto Corsa, só tive que deixar o Assynchronous Spacewarp disable, senão fica lento demais.
Falta só agora ter paciência e tentar arrumar o MSFS que tb achei horrível no VR.
Olá, ,muito obrigado pelas dicas... tenho um meta quest 3 estou usando xplane 11. Não consigo usar os controles rifts no airbus A320 da Toliss. Os controles são reconhecidos normalmente no app do meta porém no Toliss não. Existe alguma configuração previa?
Aqui sempre foi conectou, voou ! nunca tive que clicar em nada.
se voce deixar o cursor ativo, os botoes nao funcionam no VR, caso esteja habiitado, pode ser isso
How do you do with voiceattack to select the refresh rate 72hz or 80hz. Could you see your code to do that? Thank you very mutch
My quest is on developer mode, It have ADB drivers installed, so with 'scrcpy' , I'm able to send some adb commands to the headset. I created a bunch of *.BAT files that I can call via voice commands.
Here the content of some of those batches .
"@echo off
C:\Users\myusername\Desktop\Docs\Recorder\Batches\scrcpy-win64-v2.0\adb shell setprop debug.oculus.refreshRate 80
exit"
@@fsprimo Thank you very mutch indeed 👍
so then is the reason that i cant use open xr toolkit right now in xplane due to the update from oculus ive tried to get it to work but no luck :/
Mega updated the software and it’s working again
fala comando, eu baixei esse OpenXR ai e nao tem a opçao de custom fov mesmo nao atualizando o OpenXR, sabe me dizer o por que disso? pois so essa versao 0.0.0 que funciona no XP!!
O XPlane não suporta
@@fsprimo meu monitor é 1080p, se eu baixar no xplane para 720p muda alguma coisa no VR?
@@NOOBGAMER-or5ze não
@@fsprimo nem abaixa o consumo da GPU por isso?
@@NOOBGAMER-or5ze Absolutamente nada. O que está consumindo é a saída de Encode e Decode da GPU pra rodar o Quest ! faz o teste ai vc mesmo.
does it work with pico 4?
Try it!
Quando eu coloco em 72hz e coloco a resolução para 1.3x, mesmo Quest link via cabo, fica quase impossível de usar o óculos. Perde muito desempenho, trava horrores na própria dela do Quest links sem nem ao menos ir pra área de trabalho pelo óculos.
Quanto % de GPU está atingindo quando isso acontece?
Tira o bitrate de 500 pra 100 e faz um teste, vai subindo aos poucos, 100, 200, 300 etc.
Faz essa alteração, reinicia o PC e o oculus pra isso aplicar.
@@fsprimo vou fazer o teste e vejo quantos % está em uso e já mando aqui
Só de colocar o bitrate em 100 acabou com a perda de performance, mesmo no 1.3x em 72hz ... Porém meu menu do openxr não quer abrir no simulador , cada hora uma coisa 😢
@@renan7937 Para x-Plane, O openxr tem que ser exatamente o que eu disponibilizei no link da descrição do video.