Quest 3 performance

[nrosko]

I'm new to Q3 coming from an index, just wondering what performance is like? In my index i could manage 80fps without any reprojection. 

The Q3 is another story and as soon as i look at AI aircraft my frames  drop drastically & it just becomes unplayable. 

I have a 4090 with a ryzen 9 5950x3d. 

I almost feel that the Ai has terrible optimization at a distance. 

I'm using virtualdesktop with very fast wifi. 

 

Anything i'm missing here?

Edited February 10 by nrosko

[Aapje]

Something must be misconfigured on your system, or your wifi is not as good as you think, since that setup should cope with it very well.

 

I would personally suggest first configuring it with a good USB cable, and only then try to make it wireless. Wifi introduces all kinds of new potential issues. For example you can use this guide:

 

 

[dryheat94]

Be sure SteamVR resolution is set to 100%, not the default 150%. It's a multiplier and using with VD it must be set to 100% or you will be setting your resolution way too high. You don't mention if you use OpenComposite, but best to get SteamVR setup correctly either way.

 

Open the performance monitor in VD and see what settings show in orange. Orange bad. Also, it should show you at 100% resolution in Performance Monitor while in game. You set the resolution using the Ultra, Godlike settings in VD. You should have no issue using Godlike. For my 4080 I use Ultra.

 

It's also important when using VD that your router is cabled directly to your PC with a Cat5/6 cable. Wireless between router and PC is a no go. Mesh routers are also problematic.

Performance Monitor will lead you to the problem. Look for orange text to find the culprit.

Edited February 11 by dryheat94

[chiliwili69]

12 hours ago, nrosko said:

I'm new to Q3 coming from an index, just wondering what performance is like?

 

The good thing of the Quest3 is that, with twice the physical pixels over the Index, you don´t require more GPU power than with the Index.

Since the Quest3 can run at 72Hz mode (which is visually fine for me) the required GPU power (for SteamVR 100%SS) is 0.67 , versus the Index 0.72.

 

 

So, in terms of GPU with your 4090 you should be plenty of power, allowing you to increase SuperSampling as much as you want (of course there will also a limit).

 

Regarding CPU, your 59503D is as ideal for IL-2 with Index as with the Quest3. So you should not see too much difference. Planes AI in IL-2 can bottleneck the CPU pretty quickly even with the top CPUs.

 

Do you use SteamVR or OpenComposite?

 

In general for the Quest3 I always recommend just to start with the basic setup, avoiding any third party software like VirtualDesktop, Open XR toolkit, OpenComposite, etc which introduce more options and complexity at the settings. Then if the basic setup works correctly you can start playing with the millions of combinations to run Quest3 with IL-2 and judge with your own eyes if the added complexity is worth for you.

 

 

Edited February 11 by chiliwili69

[nrosko]

Thank you for all the suggestions, I was not using open composite so I try that but it didn't help. I managed to discover the issue though. I noticed in virtual desktop the decoding latency dramatically increase when AI was in view. I set my my bitrate from 200 to 100 & it seems to have helped. My max bitrate is at 200 still. I'm using WIFI 6E to stream & router is right next to me there is no dropouts or indication its a wifi issue in VD performance view, I also have a solid wired internet connection at 1GB. I can't see any visual difference between 200 & 100. 

 

I will try with USB to see if it's any better, I did initially try it when i got the headset but visually it looks far worse but i didn't realise you can configure using the ODT. The above video is a good guide. USB is 5mbs so i'm not sure how that compares to a 6e wifi? 

 

I'm also not sure how the AI>package latency>Bitrate settings are related only that the bottleneck of data from the AI is too much to repackage to stream. You would thing having a higher bitrate would help i guess not. 

 

 

[Aapje]

If using USB looks worse, then it is not properly configured for sure. But for USB I would suggest setting H.264 in the debug tool, with at least 500 Mbp.

[chiliwili69]

The encoding is done by the GPU, so this is a bit strange that a CPU intensive task (multiple planes AI) afects how the GPU encode that.

 

You said that reducing encoding workload (from 200 to 100 Mbps, I assume using H265) helped to reduce the issue.

 

The CPU calculates the geometry of the scene (with flying model, damage model, physics and plane AI), and once the scene is calculated then the GPU do the render (calculate the color of every pixel for both eyes) and encode that.

 

So it could be three things:

 

- CPU issue: Not delivering the performance when AI is used. You can run the IL-2 SYN_Vander test on monitor (1080p) just to be sure your CPU deliver a similar performance compared to other similar CPUs. Or perform other public CPU benchmarks. And look temperatures

 

- CPU --> GPU bus: something wrong on the PCI bus? did you place the GPU in the best PCI rack? is bus freq correct?

 

- GPU issue: You can use MSI afterbuner to monitor the load, temps, . You can also try with other encoders like H264 or AV1.

 

I don´t thing it is related to the wifi since you only notice the issue when plane AI is in scene.

 

 

 

 

[dgiatr]

On 2/15/2025 at 9:40 PM, chiliwili69 said:

The encoding is done by the GPU, so this is a bit strange that a CPU intensive task (multiple planes AI) afects how the GPU encode that.

 

You said that reducing encoding workload (from 200 to 100 Mbps, I assume using H265) helped to reduce the issue.

 

The CPU calculates the geometry of the scene (with flying model, damage model, physics and plane AI), and once the scene is calculated then the GPU do the render (calculate the color of every pixel for both eyes) and encode that.

 

So it could be three things:

 

- CPU issue: Not delivering the performance when AI is used. You can run the IL-2 SYN_Vander test on monitor (1080p) just to be sure your CPU deliver a similar performance compared to other similar CPUs. Or perform other public CPU benchmarks. And look temperatures

 

- CPU --> GPU bus: something wrong on the PCI bus? did you place the GPU in the best PCI rack? is bus freq correct?

 

- GPU issue: You can use MSI afterbuner to monitor the load, temps, . You can also try with other encoders like H264 or AV1.

 

I don´t thing it is related to the wifi since you only notice the issue when plane AI is in scene.

 

 

 

 

Hi ,

Can I play il2 sturmovik WITHOUT quest 3 controllers?

Can I start the game WITHOUT them?

I am interested in playing in opencomposite, openxr toolkit...first and then in Steam Vr..

Thanks!

[chiliwili69]

28 minutes ago, dgiatr said:

Can I play il2 sturmovik WITHOUT quest 3 controllers?

Can I start the game WITHOUT them?

 

I don´t use OpenComposite or OpenXR toolkit. I use SteamVR with the AirLink.

 

Within the Quest3 menu I can use my hands to activate the Airlink, but once I do that, then I only need to use one controller to just activate the Desktop, and once in Desktop View within the headset launch IL-2.

 

 

Normally it is not an issue to just use the controllers to launch the game, you don´t need them during the IL-2 game once it is launched.

 

But I need to try another way to launch it wihtout the need of controllers. I will let you know.

[Aapje]

I think that it should work if you play with the cable. Then you can have Link start automatically. Then you just start IL-2 from the PC.

[chiliwili69]

I have tried it with Airlink and I do not need the controller, just my hands.

 

The steps are:

 

1- Launch Meta Quest Link application in the PC

2- Switch on Quest3 and the Quest3 in your head

3- Enable AirLink from Quest3 menu using your hands

4- Take Quest3 out for a moment to see the monitor and launch IL-2 from the PC which will trigger SteamVR.

 

As indicated by Aapje, I think you can have the Airlink to start automatically so the steps would be (not tried myself):

 

1- Launch Meta Quest Link application in the PC

2- Switch on Quest3 (Airlink or QuestLink should autostart)

3- Launch IL-2 from the PC which will trigger SteamVR.

4- Put Quest3 in your head.

[dgiatr]

4 hours ago, chiliwili69 said:

 

I don´t use OpenComposite or OpenXR toolkit. I use SteamVR with the AirLink.

 

Within the Quest3 menu I can use my hands to activate the Airlink, but once I do that, then I only need to use one controller to just activate the Desktop, and once in Desktop View within the headset launch IL-2.

 

 

Normally it is not an issue to just use the controllers to launch the game, you don´t need them during the IL-2 game once it is launched.

 

But I need to try another way to launch it wihtout the need of controllers. I will let you know.

Thank you very much...I am waiting for your news..

[dgiatr]

On 2/15/2025 at 9:40 PM, chiliwili69 said:

The encoding is done by the GPU, so this is a bit strange that a CPU intensive task (multiple planes AI) afects how the GPU encode that.

 

You said that reducing encoding workload (from 200 to 100 Mbps, I assume using H265) helped to reduce the issue.

 

The CPU calculates the geometry of the scene (with flying model, damage model, physics and plane AI), and once the scene is calculated then the GPU do the render (calculate the color of every pixel for both eyes) and encode that.

 

So it could be three things:

 

- CPU issue: Not delivering the performance when AI is used. You can run the IL-2 SYN_Vander test on monitor (1080p) just to be sure your CPU deliver a similar performance compared to other similar CPUs. Or perform other public CPU benchmarks. And look temperatures

 

- CPU --> GPU bus: something wrong on the PCI bus? did you place the GPU in the best PCI rack? is bus freq correct?

 

- GPU issue: You can use MSI afterbuner to monitor the load, temps, . You can also try with other encoders like H264 or AV1.

 

I don´t thing it is related to the wifi since you only notice the issue when plane AI is in scene.

 

 

 

 

Hello to all!

 

For a few months now I switched from G2 to Quest3. Generally I am satisfied but I have one issue though. When I used G2 I had openxr-open composite and openxr toolkit at about 2600 resolution with 2xMSAA and 90 fps. Never had a problem with fps drop in Berloga mutiplayer server despite the number of total planes ( AI and human players ).

 

Now with Quest 3 at about 3000 resolution and 72 fps in opencomposite mode and 2XMSAA ( all other graphic settings the same as with G2 ) I suffer from regular fps drop even if the total planes are only 10 in Berloga, especially when there are sudden explosions or close intensive dogfights.

 

I have the same cpu ( Intel 13900 ) and gpu Nvidia rtx 3090 ti supreme x as before.

 

Do you think it's normal for the GPU not to be able to maintain 72 fps at 3000 resolution and 2XMSAA ( I have no shadows or mirrors , clouds to medium.. )

 

What solutions do you propose? Should I overclock my gpu if I want to stay at 3000 resolution and 2XMSAA?

 

Thanks!

 

Edited July 15 by dgiatr

[chiliwili69]

On 7/15/2025 at 2:38 PM, dgiatr said:

For a few months now I switched from G2 to Quest3. Generally I am satisfied but I have one issue though. When I used G2 I had openxr-open composite and openxr toolkit at about 2600 resolution with 2xMSAA and 90 fps. Never had a problem with fps drop in Berloga mutiplayer server despite the number of total planes ( AI and human players ).

 

Now with Quest 3 at about 3000 resolution and 72 fps in opencomposite mode and 2XMSAA ( all other graphic settings the same as with G2 ) I suffer from regular fps drop even if the total planes are only 10 in Berloga, especially when there are sudden explosions or close intensive dogfights.

 

Doing some numbers I see:

 

With G2: resolution at 2600 (This is 68% SS in SteamVR) is a total of 13.3 million pixels, and at 90fps you demand to the GPU to render 1.2 Gpixels per second.

 

With Quest3: resolution at 3000 (This is 210% SS in SteamVR) is a total of 19.7 million pixels, and at 72fps you demand 1.42 Gpixels.

 

So, with the Quest3, even at 72Hz you are demanding a bit more to your GPU. In addition to that, the GPU has to do the Encoding work (do you use H264 or H265 codec?) which is also an extra thing.

 

I think that 150% SS is quite OK for the Quest3 (this is what I use for my Quest3 with a 3080). You will render 14 million pixels and at 72Hz this is 1 Gpixel/s.

 

 

If this doesn´t solve your problem, then the bottleneck should be in the CPU. You can run fpsVR tool to monitor the CPU and GPU frametimes. (you can also do that with SteamVR frametimes visualizer)

[dgiatr]

2 hours ago, chiliwili69 said:

 

Doing some numbers I see:

 

With G2: resolution at 2600 (This is 68% SS in SteamVR) is a total of 13.3 million pixels, and at 90fps you demand to the GPU to render 1.2 Gpixels per second.

 

With Quest3: resolution at 3000 (This is 210% SS in SteamVR) is a total of 19.7 million pixels, and at 72fps you demand 1.42 Gpixels.

 

So, with the Quest3, even at 72Hz you are demanding a bit more to your GPU. In addition to that, the GPU has to do the Encoding work (do you use H264 or H265 codec?) which is also an extra thing.

 

I think that 150% SS is quite OK for the Quest3 (this is what I use for my Quest3 with a 3080). You will render 14 million pixels and at 72Hz this is 1 Gpixel/s.

 

 

If this doesn´t solve your problem, then the bottleneck should be in the CPU. You can run fpsVR tool to monitor the CPU and GPU frametimes. (you can also do that with SteamVR frametimes visualizer)

Hi Chiliwili69,

 

Thank you for your recommendations..as usual you get into the point of the issue.

 

Indeed I saw that it's a gpu higher demand issue so after done some gpu over clocking I see that I don't suffer from fps drops so often ( i regularly check gpu temps..). I haven't completely eliminated the problem though. I use h264 codec, what else should I change ( bitrate , e.t.c ) in case I switch to h265 codec to see if it's better for me?

 

Thanks!

 

Edited July 17 by dgiatr