Oculus 3 RTX 4070ti Issues

[Fergi19]

I’ve spent over a month trying to dial in my O3.  I get really long game pauses in MP and visuals are cartoonish at best. Game pauses typically happen when there are more objects present or things happening, I.e. near the carrier group or after takeoff from an airport but not typically when attacking targets. 
 

The good news is that frame rates are 90 in single player and 45 in MP.

 

PC is i7-12700, RTX 4070 ti 12 gb, 64 GB DDR 4. I’m on a 1 gig via Ethernet internet connection. 

 

I really appreciate any wisdom from the masses!

 

[Qcumber]

7 hours ago, Fergi19 said:

I’ve spent over a month trying to dial in my O3.  I get really long game pauses in MP and visuals are cartoonish at best. Game pauses typically happen when there are more objects present or things happening, I.e. near the carrier group or after takeoff from an airport but not typically when attacking targets. 
 

The good news is that frame rates are 90 in single player and 45 in MP.

 

PC is i7-12700, RTX 4070 ti 12 gb, 64 GB DDR 4. I’m on a 1 gig via Ethernet internet connection. 

 

I really appreciate any wisdom from the masses!

 

If you are getting cartoon images you res might be too low. Make sure you set the resolution slider to the right in the oculus app to max out the resolution. Then use oculus tray tool or oculus debug tool to set the supersampling to 1.2 or 1.3. Keep DCS PD to 1.0. See if that looks any better. Are you using airline or cable? The pauses might be latency issues. 
 

 

[Fergi19]

1 hour ago, Qcumber said:

If you are getting cartoon images you res might be too low. Make sure you set the resolution slider to the right in the oculus app to max out the resolution. Then use oculus tray tool or oculus debug tool to set the supersampling to 1.2 or 1.3. Keep DCS PD to 1.0. See if that looks any better. Are you using airline or cable? The pauses might be latency issues. 
 

 

Thanks... I'll give those a try.  I'm using a cable, it tests well on the Oculus App.

[Fergi19]

I've made those changes, also upgraded to the Oculus cable which tests slightly better at 1.6 gb/s vs 1.3 that I got with the other cable.  Pauses seem to be better but not completely gone.  The visuals are still pretty crappy though.  I'd really like to be able to read the cockpit without zooming and the outside visuals need some improvement too.  Frames in  MP are still around 45 and around 90 in SP.

[Qcumber]

35 minutes ago, Fergi19 said:

I've made those changes, also upgraded to the Oculus cable which tests slightly better at 1.6 gb/s vs 1.3 that I got with the other cable.  Pauses seem to be better but not completely gone.  The visuals are still pretty crappy though.  I'd really like to be able to read the cockpit without zooming and the outside visuals need some improvement too.  Frames in  MP are still around 45 and around 90 in SP.

Something isn't right. You should be able to see the cockpit instruments easily without zooming in with the settings I suggested. Do you use OXRTK? If so then you can see the actual resolution if you set it to FSR or NIS. With the changes I suggested your Res should be about 3500x3500 pixels (approx). That's more than enough for a crisp cockpit. 

In terms of the pauses. Is this regular stutters? What do your latencies look like on the DCS overlay? Have you got a lot of spikes? A regular pattern off increasing latencies? 

 

[Phantom711]

Have you checked, if this is really your fastest USB-Port?

Oh and even though not directly related to your problem…definitely try the 72Hz mode. You are more likely to match 72 FPS than 90. So there is also lesser cases where it drops into ASW. 
This is also why you get 45 FPS in MP. Your PC simply can‘t achieve 90 FPS so it drops to half rate ASW. Now this could still be the case even with 72Hz, but not as often.

 

Edited February 16, 2024 by Phantom711

[Phantom711]

I just tested my connection with the official Oculus Link cable…I got 2.7GBps…just for your reference.

[whitav8]

Try running at 72Hz ( 36 FPS ) and using Virtual Desktop (Godlike mode 3000x3000 res) using a Wifi5 AX ($50) or wifi6e AXE second router ($150) setup as an Access Point (reserved static IP, DNS) connected by 1Gbps cable to first router which is connected to PC with 1Gbps cable. See Virtual Desktop Discord for example routers

DCS Settings:

VR Tab        Pixel Density 1.2->1.3   and enable HMD mask

System:  Res of Cockpit Displays: 1024 ,   Antialiasing off,     Upscaling: Off,        Shadows: Flat Only   Flat Shadows Blur: Off,     Civ Traffic: Off,   Water: Low    

                Lower Forest and Scenery Detail,   Rain Droplets: disabled

OpenXR Toolkit : Some FSR or NIS or CAS

[Qcumber]

8 hours ago, whitav8 said:

OpenXR Toolkit : Some FSR or NIS or CAS

I guess you mean use these for sharpening?

[iFoxRomeo]

On 2/12/2024 at 1:56 PM, Fergi19 said:

I’ve spent over a month trying to dial in my O3.  I get really long game pauses in MP and visuals are cartoonish at best. Game pauses typically happen when there are more objects present or things happening, I.e. near the carrier group or after takeoff from an airport but not typically when attacking targets. 
 

The good news is that frame rates are 90 in single player and 45 in MP.

 

PC is i7-12700, RTX 4070 ti 12 gb, 64 GB DDR 4. I’m on a 1 gig via Ethernet internet connection. 

 

I really appreciate any wisdom from the masses!

 

I have the following specs:

Ryzen 9 5900X, 3080ti, 64GB RAM, Oculus Quest 3. I had a HP Reverb G1 and G2 before.

 

Your system should be at least same or likely better performing than mine.

What does the test say to the 1.6Gbps, is it compatible(green) with this speed?

My settings in OCULUS:

 

 

 

My settings in DCS

 

 

I really don't like the picture DLSS currently produces. Performance gain is great, but the picture even in quality mode is not good. If that changes in the future, I will gladly use it.

 

 

You can set the PD in DCS or the OCULUS software. But be careful to not set horrendous products. 1.3*1.3 will kill your fps. I went with 1.0 in Oculus and 1.3 in DCS. I might change that, as other games don't have a PD setting in game.

Contrary to popular believe it doesn't matter where you set your PD. Only the resulting resolution counts. I currently don't use the OpenXR toolkit. It is installed but deactivated.

Now it is important to use either Oculus debug tool or the tray tool. Unfortunately the tray tool has issues with Windows 11. I haven't found a solution for it, hence I use the oculus debug tool.

 

BUT some settings are saved, some are not. So you have to set them before you start DCS. Settings in the "Oculus Link" area are saved.

 

FOV, Visible HUD is not saved.

You said cartoonish graphics? That was my first thought when I made the first flight with the Q3.

Set "Link Sharpening" DISABLED ! Reduce sharpening in DCS. I have 0.3. Play with that.

FOV is a individual thing. Reduce it as much as possible. But only so much that it doesn't disturb you. I can live with small black areas that are visible, but are not too disturbing.

Why? A FOV of 1.0*1.0(default) renders high resolution images outside of your FOV (which is depending on the distance between your eyes and the Q3 lenses) for nothing.

Play with FOV settings till you find a good compromise.

You gain a lot by reducing FOV:

 

9.114.624 Pixel is the total amount the Q3 has. If you increase PD by 1.3 the PC has to calculate 11.849.011 Pixel (*refresh-rate) per second. In my case I reduced FOV by 0.9*0.62=0.558.

So my PC has to calculate 6.611.748(*72) per second but with a 1.3 times higher PD in the visible area. This gives me headroom in DCS, so that it runs most of the time with 72fps, without the need of ASW. Currently I fly a lot with the old warbirds. So with more modern modules that might be different.

 

Use "Visible HUD" - Performance in the Oculus debug tool to see the headroom and the performance overall.

Make a routine to compare the different settings. E.g.: create a simple mission, where you sit in your ac in the air and fly the same route. Otherwise it is difficult to assess the changes in performance with different game/PD etc. settings.

 

How to start DCS:

Start OCULUS software

Start OCULUS Debug tool

Change the settings like FOV

Activate the link, and you should immediately see the reduced FOV in the OCULUS VR area. If NOT then something didn't work, but you noticed it before launching (and waiting) for DCS to start.

Start DCS

 

Fox

 

[Maddaawg]

On 2/16/2024 at 5:37 AM, Fergi19 said:

I've made those changes, also upgraded to the Oculus cable which tests slightly better at 1.6 gb/s vs 1.3 that I got with the other cable.  Pauses seem to be better but not completely gone.  The visuals are still pretty crappy though.  I'd really like to be able to read the cockpit without zooming and the outside visuals need some improvement too.  Frames in  MP are still around 45 and around 90 in SP.

Start with that cable or USB port. Your about 1Gbps slower than it should be. Are you using a USB C port directly from the MB? 

[BatmanG7]

En 17/2/2024 a las 10:20, iFoxRomeo dijo:

I have the following specs:

Ryzen 9 5900X, 3080ti, 64GB RAM, Oculus Quest 3. I had a HP Reverb G1 and G2 before.

 

Your system should be at least same or likely better performing than mine.

What does the test say to the 1.6Gbps, is it compatible(green) with this speed?

My settings in OCULUS:

 

 

 

My settings in DCS

 

 

I really don't like the picture DLSS currently produces. Performance gain is great, but the picture even in quality mode is not good. If that changes in the future, I will gladly use it.

 

 

You can set the PD in DCS or the OCULUS software. But be careful to not set horrendous products. 1.3*1.3 will kill your fps. I went with 1.0 in Oculus and 1.3 in DCS. I might change that, as other games don't have a PD setting in game.

Contrary to popular believe it doesn't matter where you set your PD. Only the resulting resolution counts. I currently don't use the OpenXR toolkit. It is installed but deactivated.

Now it is important to use either Oculus debug tool or the tray tool. Unfortunately the tray tool has issues with Windows 11. I haven't found a solution for it, hence I use the oculus debug tool.

 

BUT some settings are saved, some are not. So you have to set them before you start DCS. Settings in the "Oculus Link" area are saved.

 

FOV, Visible HUD is not saved.

You said cartoonish graphics? That was my first thought when I made the first flight with the Q3.

Set "Link Sharpening" DISABLED ! Reduce sharpening in DCS. I have 0.3. Play with that.

FOV is a individual thing. Reduce it as much as possible. But only so much that it doesn't disturb you. I can live with small black areas that are visible, but are not too disturbing.

Why? A FOV of 1.0*1.0(default) renders high resolution images outside of your FOV (which is depending on the distance between your eyes and the Q3 lenses) for nothing.

Play with FOV settings till you find a good compromise.

You gain a lot by reducing FOV:

 

9.114.624 Pixel is the total amount the Q3 has. If you increase PD by 1.3 the PC has to calculate 11.849.011 Pixel (*refresh-rate) per second. In my case I reduced FOV by 0.9*0.62=0.558.

So my PC has to calculate 6.611.748(*72) per second but with a 1.3 times higher PD in the visible area. This gives me headroom in DCS, so that it runs most of the time with 72fps, without the need of ASW. Currently I fly a lot with the old warbirds. So with more modern modules that might be different.

 

Use "Visible HUD" - Performance in the Oculus debug tool to see the headroom and the performance overall.

Make a routine to compare the different settings. E.g.: create a simple mission, where you sit in your ac in the air and fly the same route. Otherwise it is difficult to assess the changes in performance with different game/PD etc. settings.

 

How to start DCS:

Start OCULUS software

Start OCULUS Debug tool

Change the settings like FOV

Activate the link, and you should immediately see the reduced FOV in the OCULUS VR area. If NOT then something didn't work, but you noticed it before launching (and waiting) for DCS to start.

Start DCS

 

Fox

 

Fox Hi there.

I see your DCS and Oculus Settings and we have some quite similar settings. However...one question?  What type of plane do you fly at DCS? 16? 18?

The point here Fox is that I haven't got that great resolution as I did with a Reverb G2 in the numbers that are at the left bottom corner of the MFD. Where you see the bullseyes indication. 

I used to see them pretty clear "at the sweet spot" of my G2. Now with my Oculus 3 which I think is great I see the cockpit pretty much clear and way much better than the G2 even when I don't look directly to a specific part or instrument. But....But..... I still haven't got that precise resolution to this this numbers as I used to see it in the G2 and need sometimes to zoom in.   I have attached some pictures of the MFDs and in circles the numbers I am referring to.

Any clues that might help?

Thanks and big hug!!!

[Maddaawg]

1 hour ago, BatmanG7 said:

Fox Hi there.

I see your DCS and Oculus Settings and we have some quite similar settings. However...one question?  What type of plane do you fly at DCS? 16? 18?

The point here Fox is that I haven't got that great resolution as I did with a Reverb G2 in the numbers that are at the left bottom corner of the MFD. Where you see the bullseyes indication. 

I used to see them pretty clear "at the sweet spot" of my G2. Now with my Oculus 3 which I think is great I see the cockpit pretty much clear and way much better than the G2 even when I don't look directly to a specific part or instrument. But....But..... I still haven't got that precise resolution to this this numbers as I used to see it in the G2 and need sometimes to zoom in.   I have attached some pictures of the MFDs and in circles the numbers I am referring to.

Any clues that might help?

Thanks and big hug!!!

 

 

The G2 has better clarity in the sweet spot than the Q3 though the Q3 has higher clarity throughout the rest of the lenses. I came from a G2, if I look right at numbers and dials, they were clearer, but I always had to look right at them.

[prometheus122]

I’m using quest 3 with rtx 4070 (not Ti, and a Ryzen 5800x3d cpu) and it works pretty well using virtual desktop, pretty much as described earlier in this thread.

 

I tried using oculus initially but could never get a decent result, too many moving parts . VD simplifies the process…just need to configure DCS, and the open xr settings (for sharpening and upscaling)

 

I made a short vid for a friend to compare with his set up….. although I improved performance since then with some tweaks

 

[BatmanG7]

En 13/5/2024 a las 23:52, Maddaawg dijo:

The G2 has better clarity in the sweet spot than the Q3 though the Q3 has higher clarity throughout the rest of the lenses. I came from a G2, if I look right at numbers and dials, they were clearer, but I always had to look right at them.

Sure……agree.  Any clue on how to get the best sharpening and resolution for the Q3 on those numbers?

[Maddaawg]

2 hours ago, BatmanG7 said:

Sure……agree.  Any clue on how to get the best sharpening and resolution for the Q3 on those numbers?

Not really, I'm just working on my settings as I was teaching myself in 2D first. It will depend a lot on your system specs. There are several helpful threads here under Virtual Reality. Questions for settings are split amongst using VD, Wireless MQ Link or Wired MQ Link. If using the Meta Quest Links, then there are some configurations to be made with Oculus Tray Tool. I've been using VD so I am not familiar with that tool.

In your forum settings, you can look for the signature settings and put your system specs there and that will help others to help you.

[iFoxRomeo]

On 5/14/2024 at 4:52 AM, BatmanG7 said:

Fox Hi there.

I see your DCS and Oculus Settings and we have some quite similar settings. However...one question?  What type of plane do you fly at DCS? 16? 18?

The point here Fox is that I haven't got that great resolution as I did with a Reverb G2 in the numbers that are at the left bottom corner of the MFD. Where you see the bullseyes indication. 

I used to see them pretty clear "at the sweet spot" of my G2. Now with my Oculus 3 which I think is great I see the cockpit pretty much clear and way much better than the G2 even when I don't look directly to a specific part or instrument. But....But..... I still haven't got that precise resolution to this this numbers as I used to see it in the G2 and need sometimes to zoom in.   I have attached some pictures of the MFDs and in circles the numbers I am referring to.

Any clues that might help?

Thanks and big hug!!!

Hm. I have to check that.

The 16 and 18 are full of spiderwebs in my hangar

Did you try to increase the Res. of Cockpit Displays?

Edited May 17, 2024 by iFoxRomeo
typo

[BatmanG7]

En 16/5/2024 a las 2:52, iFoxRomeo dijo:

Hm. I have to check that.

The 16 and 18 are full of spiderwebs in my hangar

Did you try to increase the Res. of Cockpit Displays?

 

Is at Max.  There goes pics of my settings IFox

En 15/5/2024 a las 22:49, Maddaawg dijo:

Not really, I'm just working on my settings as I was teaching myself in 2D first. It will depend a lot on your system specs. There are several helpful threads here under Virtual Reality. Questions for settings are split amongst using VD, Wireless MQ Link or Wired MQ Link. If using the Meta Quest Links, then there are some configurations to be made with Oculus Tray Tool. I've been using VD so I am not familiar with that tool.

In your forum settings, you can look for the signature settings and put your system specs there and that will help others to help you.

Thanks...will try

[iFoxRomeo]

On 5/17/2024 at 9:21 PM, BatmanG7 said:

Is at Max.  There goes pics of my settings IFox

Thanks...will try

Just tested the 16 and 18. It appears to be the same for me. But I can't remember how "clear" those numbers were with the reverb.

Why do you use LOD switch factor "2"? Do you see a difference between "1" and "2"?

[Maddaawg]

On 5/17/2024 at 12:21 PM, BatmanG7 said:

Is at Max.  There goes pics of my settings IFox

Thanks...will try

Why are you forcing IPD to 57.5? Can't you just set the Q3 to 57 or 58 and see which is best? I'm not sure what effect the forcing IPD has but try adjusting your Q3 first for best results.

[BatmanG7]

En 20/5/2024 a las 16:43, iFoxRomeo dijo:

Just tested the 16 and 18. It appears to be the same for me. But I can't remember how "clear" those numbers were with the reverb.

Why do you use LOD switch factor "2"? Do you see a difference between "1" and "2"?

To be honest Ifox havent see any diference. It supose that with this LOD  you will be able to see things farther away... Am I right?

En 21/5/2024 a las 3:02, Maddaawg dijo:

Why are you forcing IPD to 57.5? Can't you just set the Q3 to 57 or 58 and see which is best? I'm not sure what effect the forcing IPD has but try adjusting your Q3 first for best results.

I understand that this is the distance between your eyes.. Thats why I put it.

[Qcumber]

On 5/21/2024 at 8:02 AM, Maddaawg said:

Why are you forcing IPD to 57.5? Can't you just set the Q3 to 57 or 58 and see which is best? I'm not sure what effect the forcing IPD has but try adjusting your Q3 first for best results.

IPD set by your headset is different to the IPD in DCS; this sets the perception of scale in the cockpit. I find i need to adjust this sometimes between aircraft. 

[iFoxRomeo]

18 minutes ago, BatmanG7 said:

To be honest Ifox havent see any diference. It supose that with this LOD  you will be able to see things farther away... Am I right?

I understand that this is the distance between your eyes.. Thats why I put it.

You probably won't see a big difference with LOD >1 in the Q3, but it will cost you performance. I have set it to 0.8 iirc.

IPD is the interpupillary distance. You should measure your IPD. There are apps that can do that. Once you did that, set it in your HMD and deactivate force IPD in DCS.

9 minutes ago, Qcumber said:

IPD set by your headset is different to the IPD in DCS; this sets the perception of scale in the cockpit. I find i need to adjust this sometimes between aircraft. 

Negative Ghostrider. The Force IPD in DCS is generally the same as the IPD setting in a HMD. BUT if you set it in your HMD by physically adjusting the lenses AND activate force IPD in DCS it will mess up the IPD for the game. This setting is for HMD that don't have a physical IPD adjustment like the HP Reverb G1. The Q3 has a physical adjustment, so you should deactivate force IPD in DCS and set your IPD in the HMD. If you then adjust IPD additionally in DCS you fool yourself with the cockpit size.

[Qcumber]

8 minutes ago, iFoxRomeo said:

You probably won't see a big difference with LOD >1 in the Q3, but it will cost you performance. I have set it to 0.8 iirc.

IPD is the interpupillary distance. You should measure your IPD. There are apps that can do that. Once you did that, set it in your HMD and deactivate force IPD in DCS.

Negative Ghostrider. The Force IPD in DCS is generally the same as the IPD setting in a HMD. BUT if you set it in your HMD by physically adjusting the lenses AND activate force IPD in DCS it will mess up the IPD for the game. This setting is for HMD that don't have a physical IPD adjustment like the HP Reverb G1. The Q3 has a physical adjustment, so you should deactivate force IPD in DCS and set your IPD in the HMD. If you then adjust IPD additionally in DCS you fool yourself with the cockpit size.

I don't really see that. Adjusting the IPD on my headset has a different effect. If I adjust ipd in game the perception of the size of the cockpit changes. I might be filing my brain but some cockpits feel to large or too small when set at the correct IPD. This does not happen with the HMD IPD. I have a Quest Pro so can easily change this when flying. 

[iFoxRomeo]

1 hour ago, Qcumber said:

I don't really see that. Adjusting the IPD on my headset has a different effect. If I adjust ipd in game the perception of the size of the cockpit changes. I might be filing my brain but some cockpits feel to large or too small when set at the correct IPD. This does not happen with the HMD IPD. I have a Quest Pro so can easily change this when flying. 

Yes IPD setting adjusts the perception of the size of close objects(cockpit). For someone with a small IPD(e.g. little kid with 15 cm IPD) close objects are bigger as for someone with a bigger IPD. You are of course free to set what you want. Just be aware, if you mix physical HMD IPD adjustment AND DCS force IPD you throw the the scale of your virtual world around. For correct size of the cockpit use either physical setting of the lenses on the HMD that has this feature OR use force IPD if you have fixed lenses in the HMD.

Here is an example of a HMD(HP Reverb G1) with fixed lenses where the IPD is adjusted via software, either WMR software or force IPD in DCS. This video is from 2020.