Meta Quest 3

[Skanky]

Hello.

Im trying out a set of Quest 3 VR, but i dont get any good resolution. 

The instruments for ex is blurry and the views out of the cockpit is blurry and hazy.

I have tried all the Hz settings for the VR (70,80,90 and 120Hz), but doesnt get any good picture. 

The FPS is around 25-40. 

Anyone who can give some good advices?

Cheers

 

My comp specs:

 

AMD RX 6900 XT

AMD Ryzen 7 5800X 8-Core Processor 3.80 GHz

ROG Strix X570-F Gaming

G.Skill Trident Z RGB DDR4-3600 64GB RAM

Edited July 9, 2024 by Skanky

[unlikely_spider]

Not sure if your frames will tolerate this comfortably, but what I do:

• Increase resolution in the Oculus app all the way to the right
• Increase PD in DCS to 1.2 or 1.3
• Don't use DLSS

Instruments are good for me with those settings only. I'm using a 4080 though.

[AlessandroFuBu]

Hi, i have the 4080 and what i do is

- standard resolution in oculus app with 72hz

- increase pd in dcs to 1.3

-no anti aliasing (DLSS is really bad in Vr)

 

Il 09/07/2024 at 19:46, unlikely_spider ha scritto:

Not sure if your frames will tolerate this comfortably, but what I do:

• Increase resolution in the Oculus app all the way to the right
• Increase PD in DCS to 1.2 or 1.3
• Don't use DLSS

Instruments are good for me with those settings only. I'm using a 4080 though.

do you use ASW or MSAA with this settings? what about shadow and do you have shimmering? thanks
I like to try sometimes DLAA because helps with shimmering but I feel reduce the cockpit resolution and I struggle reading the content of MFD

[Maddaawg]

I would like to know how your connecting the Q3, VD, Steam, WiFi with Meta Link or USB with Meta Link? Are you running bin-mt\dcs.exe bin\dcs.exe?

Your specs are similar to mine. I have mine connected through USB on Quest Link. I run MT and set the Quest resolution to 72hz and PD of 1.3. My PD in DCS is still 1.0 and I run MSAA at 2x.

I had a very smooth run in an FA-18 cold Start in Afghanistan. I used that and it's pre determined way points to test multiple settings and connection methods. VD use to be my go-to, but that did not work in Afghanistan. Also, I am using no ASW and I was getting 36 40 fps. I'm not sure this would hold up in MP though.

When I get home I'll screen shot my settings. Oh, gages are clear.

Edir: I had disabled ASW in OTT and the Quest is ignoring the setting. Dev notes on his site there may be issues with Win 11. ODT also doesn't work and neither did ctrl + numpad 1. 

Edited July 19, 2024 by Maddaawg
ASW settings ignored

[splash]

In my case, I use the default settings in Meta Quest application, i.e. 72Hz and 1.0x resolution. Besides, I configure one of these two options:

 

- set PD to 2.2 in DCS VR settings

- set PD to 2.2 in Oculus Debug Tool or Oculus Tray Tool

In Oculus Debug Tool I currently have Encoder Bit Rate set to 960 but I don't see differences at 0 (200 Mbps). With 960 sometimes I have sound stuttering.

I don't use DLSS, just DLAA. My card is a 4090.

[Phantom711]

@splash

2.2 is crazy high. Do you really feel that you need that? 
I have mine set to 1.7…and that is also with a 4090 and using Quad Views on a QuestPro.

vor 5 Stunden schrieb splash:

 

In Oculus Debug Tool I currently have Encoder Bit Rate set to 960 but I don't see differences at 0 (200 Mbps). With 960 sometimes I have sound stuttering.

Maybe rather try the middle ground then…I have mine set to 500.

The differences are very subtle and you won‘t notice a difference in all situations. I only noticed, after I tried Virtual Desktop, which simply looked better and I couldn‘t tell why until I tried increasing the bitrate on Quest Link.

There is less color banding and I feel like terrain at a distance looks better.

[Maddaawg]

On 7/17/2024 at 4:30 PM, Phantom711 said:

@splash

2.2 is crazy high. Do you really feel that you need that? 
I have mine set to 1.7…and that is also with a 4090 and using Quad Views on a QuestPro.

Maybe rather try the middle ground then…I have mine set to 500.

The differences are very subtle and you won‘t notice a difference in all situations. I only noticed, after I tried Virtual Desktop, which simply looked better and I couldn‘t tell why until I tried increasing the bitrate on Quest Link.

There is less color banding and I feel like terrain at a distance looks better.

When I try and set my bit rate to anything, I get a registry error.

[splash]

On 7/18/2024 at 1:30 AM, Phantom711 said:

@splash

2.2 is crazy high. Do you really feel that you need that? 
I have mine set to 1.7…and that is also with a 4090 and using Quad Views on a QuestPro.

Maybe rather try the middle ground then…I have mine set to 500.

The differences are very subtle and you won‘t notice a difference in all situations. I only noticed, after I tried Virtual Desktop, which simply looked better and I couldn‘t tell why until I tried increasing the bitrate on Quest Link.

There is less color banding and I feel like terrain at a distance looks better.

I'm not sure if I feel differences from 1.5-1.7. The same for the encoder bitrate.

Instead, in flight simulator 2020 I cannot get good visuals except if I use VirtualDesktop.

2 hours ago, Maddaawg said:

When I try and set my bit rate to anything, I get a registry error.

nullAre you using this screen? Try to write some value (500 for example) and leave the window open. For 600, 700, etc. you need to write the value in elsewhere and paste in the field.

[Tomcat388th]

These are the setting I use with my Q Pro  via link cable I lock my framerate to 45 fps or enable force 45 with ASW on the debug tool. Very good visuals and really smooth SP & MP. Radeon 6950xt.  The FOV Tangent Mult really helps with the FPS

J

Edited July 19, 2024 by Tomcat388th

[Ahdidaas]

thanks for posting y'all!  I have a q-pro, 4080ti and i9 64GB, and keep struggling to find the sweet spot.  Seems like when I find it, I change something else and lose it, or I get all caught up in tweaking per plane (apache seems to be pretty non-performant).

Gonna dup the settings above and see what happens. Ty!

Edited July 19, 2024 by Ahdidaas

[Maddaawg]

15 hours ago, splash said:

nullAre you using this screen? Try to write some value (500 for example) and leave the window open. For 600, 700, etc. you need to write the value in elsewhere and paste in the field.

 

Ok thanks but the error is in OTT. I am currently back to VD though as I could not get Quest Link to stop with ASW. I tried both ODT and OTT and ctrl+numpad 1. If I open the OTT menu in game, then I can get it to turn off ASW but I still can't get the bit rate set as seen in my screen grab. ODT will not shut off ASW either, its says its off but its not though I can cut/paste the bitrate there.

[Tomcat388th]

@Maddaawg   I have always had troubles with the Tray Tool lossing its setting ,getting corrupt and not working so I have stuck with the Debug Tool. You may have already tried it this way but I'll post anyway just in case.

This is how I change my bitrate if needed. As you can see in the screen shot I have notepad with the different bitrates and on the left Debug tool. On notepad highlight the bitrate then right mouse click and copy like you usually do. Then over on the debug tool left click the encode bitrate and backspace until blank  Now hit Ctrl V to paste in your number. For some reason debug wont let you paste it in using the mouse no idea why

Hope it helps

J

Edited July 21, 2024 by Tomcat388th

[Maddaawg]

1 hour ago, Tomcat388th said:

@Maddaawg   I have always had troubles with the Tray Tool lossing its setting ,getting corrupt and not working so I have stuck with the Debug Tool. You may have already tried it this way but I'll post anyway just in case.

This is how I change my bitrate if needed. As you can see in the screen shot I have notepad with the different bitrates and on the left Debug tool. On notepad highlight the bitrate then right mouse click and copy like you usually do. Then over on the debug tool left click the encode bitrate and backspace until blank  Now hit Ctrl V to paste in your number. For some reason debug wont let you paste it in using the mouse no idea why

Hope it helps

J

 

Thanks, I'll do that if or when I return to using Quest Link. Trying out VD for a while.

[MilesD]

Don't forget the FOV Tangent Multiplier.
I run mine at 0.8;0.8. It reduces the number of pixels being processed by 36% without compromising anything.
I wear glasses and 0.8;0.8 is my max before I start seeing a flat edge at the top or right side of FOV.
This allows max render resolution in the oculus app. I don't add any upscaling in DCS.

Edit: missed it was already mentioned.

Edited July 21, 2024 by MilesD

[Jive]

On 7/20/2024 at 2:55 AM, Maddaawg said:

Ok thanks but the error is in OTT. I am currently back to VD though as I could not get Quest Link to stop with ASW. I tried both ODT and OTT and ctrl+numpad 1. If I open the OTT menu in game, then I can get it to turn off ASW but I still can't get the bit rate set as seen in my screen grab. ODT will not shut off ASW either, its says its off but its not though I can cut/paste the bitrate there.

FWIW if you enable Turbo Mode in OpenXR Toolkit it should kill ASW

[Jive]

I'm doubting myself now. It came back on even with Turbo mode on. For me it seems that have the Oculus Debug Tool open while in-game and then disabling ASW seems to do it.

[Madman3353]

What’s the best method to connect to the quest 3 VD or link cable? I’m looking to upgrade my GPU either 4080, 7900xtx or wait for the 5xxx series. I see the xtx isn’t on the GPU like for link cable. Where we are today we shouldn’t have to be debugging everything. What would be the least amount or tweaking VD or link cable?

[Mr_sukebe]

I’d be cautious about an AMD GPU.  The impression I get is that the Nvidia cards have an advantage in VR when compared to the differences seen with monitors.

 

Personally, I use a cable, but that’s less about data capabilities and more about ensuring that I can keep charging my QP whilst playing, ie if I need to have it cables to prevent eg battery going flat, I might aswell use data link.

[Phantom711]

vor 12 Stunden schrieb Madman3353:

What would be the least amount or tweaking VD or link cable?

It doesn‘t make a difference really. Keep in mind, that for VD you would most likely also need an additional router.

As already mentioned, with cable, your headset remains the charge for longer.

VD has better codecs, but with an additional program (Oculus Tray Tool or Oculus Debug Tool) you can increase the bitrate so it ends up looking the same on QuestLink for the most part.

[slughead]

3 hours ago, Mr_sukebe said:

Personally, I use a cable, but that’s less about data capabilities and more about ensuring that I can keep charging my QP whilst playing, ie if I need to have it cables to prevent eg battery going flat, I might aswell use data link.

When running wireless, I use a power bank kept in a pocket with a short cable. It keeps my Quest Pro fully charged, which a cable couldn't, even if I use a powered cable running from a main charger.

INIU Power Bank, 20000mAh Fast Charging Portable Charger, 22.5W Powerbank with USB C Input & Output, Battery Pack PD3.0 QC4.0 for iPhone 15 14 13 12 11 Pro Max Mini Plus Samsung S22 S21 S20 iPad etc : Amazon.co.uk: Electronics & Photo

[majorswitcher]

When you use cable, do you have the orange warning in Meta app (connected as USB 2) or is it green/ USB 3?

i have the official Link cable, but its recognised as USB 2. I do have smooth image though

 

edit: I found a (short) good usb-c cable which is recognized as 3 and green. Very good image now, ordered a longer one and will def. fly wired!

Edited October 3, 2024 by majorswitcher

[jurinko]

My Quest3 stopped engaging ASW when getting bellow 72 fps. I used Oculus debug tool, it used to default to ASW off, but now it completely ignores the ASW set to auto.

I tried Oculus Tray Tools, ASW was on Auto by default, I let it run in the background and it worked perfectly. But then I messed with it (tried to make a DCS profile, then deleted it) and now ASW does not engage again. I can set ASW to 45 Hz and it is on all the time, but I want to switch it on only if necessary. Thx, J

 

Edited October 3, 2024 by jurinko

[jurinko]

Well I resigned and mapped the voice commands to engage/disengage ASW ("space", "warp"). I need it only at Afghanistan and Norway low level above buildings and trees. 

[Madman3353]

Does anyone know if there is a way to expand the Horizontal FOV for the Quest 3 in DCS? all i'm wanting to do is be allowed to see behind me when i turn my head to look back with out having to twist my body to much which induces pilot errors, as it sits now if i turn look back the sight picture stops right at the end of the plane (F16c).

[Sr.]

On 10/16/2024 at 8:06 AM, Madman3353 said:

Does anyone know if there is a way to expand the Horizontal FOV for the Quest 3 in DCS? all i'm wanting to do is be allowed to see behind me when i turn my head to look back with out having to twist my body to much which induces pilot errors, as it sits now if i turn look back the sight picture stops right at the end of the plane (F16c).

Not sure if this will work with Q3, but was great on the Reverb G2. Does take some figuring out.