Quest 3 / DCS Setup Assistance

[SnowTiger]

I have been away from DCS for several years. I started flying again recently and then purchased the Quest 3 and a Data Cable.
I have done some flying with minimal issues but I could use some help tweaking things for better clarity (especially in the cockpit).
There are few other VR related things I could use some help with too to make my transition smoother such as Hand Controllers or Not ? Zoom Function. Hotas setup with VR related things that might be necessary ?

I do have a Good PC System (specs below) so I'm hoping somebody with a "Quest 3 and with Similar PC Specs" might be willing to be HIRED to spend an hour or two online with me some afternoon later this week possibly (or whenever).

If anyone that fits that requirement is available, I'd be grateful for you time. Please PM me with best time (time zone) and days when we could connect and an indication on Fees.

Thanks in Advance.
 

[av8orDave]

I’m not worthy of being hired, but I have basically your system and I’m glad to share my settings. I have a Q3, a 7950X, a 4090, and 64G of DDR5.

I generally use the link cable, but sometimes I use Virtual Desktop. More on that in a minute. When using the link cable:

- fire up the Meta app o your desktop and make sure the Q3 PD is set to 1.0 and 72hz.

- fire up Oculus Debug Tool; set PD to 1.8, turn off ASW (disabled), set bitrate to 500.

- in DCS, use DLSS quality, high textures and high terrain textures, medium water, high visibility distance, medium shadows, medium clouds, and play with the other settings to your liking.

See how it looks, monitor and adjust.

If you want a much simpler experience, you’ll need a dedicated router, download the Virtual Desktop streamer app, and Virtual Desktop. With your rig, you can then pick the H264 codec, run it at about 300 bitrate, set it at “godlike”, and enjoy.

Hope it helps. If you have questions, I’m glad to answer.

[SnowTiger]

Thank you kindly. I will try your settings out, most of which I believe I already have set but I was using the Oculus Debug app but wasn't sure it was actually doing anything. It also appears that the settings I've input do not stay set. In other words, I have to input those setting each time I want to fly.
I have noticed a couple things you have recommended which I will try which differ from what someone else had recommended (re: Oculus Debug tool) such as Bitrate which someone else suggested 900 vs 500 you mention. Now I don't know what ANY of these settings do but I'm willing to try anything to get the most out of my headset. I will set it to 500 as you suggested.
BTW - I was told I should put 800 (or something like that ... I can't remember now) in the very first line re: Pixels Per Display Pixel Override.
Whatever I did input there, never stays. It always reads 0 (zero) every time I open the debug tool. Is there a way to save the settings ?

I'm also curious where to find "PD to 1.8, turn off ASW (disabled)" because I don't see them in the debug tool ? I'm including a Screenshot to show my Debug tool window.
Once set, should these settings remain OR will I need to input these settings each time I fly using the Link Cable ?

Here's another question. My Data Link Cable has a USB C  port near one end for Charging (which I thought the Link Cable did among other things). Somewhere along the line I either Read or saw in a Video that suggested I can Plug the Quest 3 charging cable and adapter into that port. I have done that a couple times but then I get a message about 10 minutes into flying that says "something like" "Your Cable has Gotten Wet therefore .. something or other .. is being turned off" which seems to imply the Charging feature is turned off.  I don't know because it's all Greek to me.

Thanks again av8orDave

Edited February 9 by SnowTiger

[SnowTiger]

I figured out what/where the "set PD to 1.8, turn off ASW (disabled), set bitrate to 500" settings go.
I have attached another screenshot of the revised Debug screen.
PS> The other person had me set the first line to 1.200000. I have revised it to reflect your suggestions. Thanks again for that.
I guess I'll have to input the 1.8 each time I open and use the Debug tool right ?  OR Is there a way to save it ?
Also, I didn't realize that the Debug tool was required to remain Open while playing (albeit Minimized) ? I never even had it on during my last couple flights so I'm interested to see what it's like with the Debug tool open which I will be doing very soon today.
Thanks again.

[av8orDave]

2 hours ago, SnowTiger said:

I figured out what/where the "set PD to 1.8, turn off ASW (disabled), set bitrate to 500" settings go.
I have attached another screenshot of the revised Debug screen.
PS> The other person had me set the first line to 1.200000. I have revised it to reflect your suggestions. Thanks again for that.
I guess I'll have to input the 1.8 each time I open and use the Debug tool right ?  OR Is there a way to save it ?
Also, I didn't realize that the Debug tool was required to remain Open while playing (albeit Minimized) ? I never even had it on during my last couple flights so I'm interested to see what it's like with the Debug tool open which I will be doing very soon today.
Thanks again.

Correct, looks like you’re getting it figured out. Unfortunately the settings in Oculus Debug Tool are not “sticky”, i.e. you’ll have to enter them each session. 
 

For the bitrate, you can run up to 960. If you want to try this, you have to type “960” into an app like notepad, copy the 960, and paste it in. It is a workaround. The Debug Tool won’t let you type a number that high directly in, but will let you copy it. I do run 960, although any benefit over 500 is pretty negligible, if perceptible at all.

[Qcumber]

11 minutes ago, av8orDave said:

Unfortunately the settings in Oculus Debug Tool are not “sticky”, i.e. you’ll have to enter them each session

You can use Oculus Tray Tool to set keybinds to toggle ASW. And you can select 960mbps from a drop down menu. 

[Gman109]

Do I understand correctly that for Quest 3 users for DCS that you don't need the OpenXR toolkit?  Am I good to go with just the Occulus Debug tool?

[Roosterfeet]

I have a Quest 3 and I don't use Openxr tool kit. It causes DCS to crash when I remove the headset.

OpenXR turbo mode helps with stutters while using ASW and I use Quadviews for that when I like. Quadviews and I aren't getting along at the moment.

 

Edited March 5 by Roosterfeet

[sleighzy]

8 hours ago, Gman109 said:

Do I understand correctly that for Quest 3 users for DCS that you don't need the OpenXR toolkit?  Am I good to go with just the Occulus Debug tool?

Correct. OpenXR Toolkit not needed.

[SnowTiger]

On 2/9/2025 at 11:20 AM, SnowTiger said:

I figured out what/where the "set PD to 1.8, turn off ASW (disabled), set bitrate to 500" settings go.
I have attached another screenshot of the revised Debug screen.
PS> The other person had me set the first line to 1.200000. I have revised it to reflect your suggestions. Thanks again for that.
I guess I'll have to input the 1.8 each time I open and use the Debug tool right ?  OR Is there a way to save it ?
Also, I didn't realize that the Debug tool was required to remain Open while playing (albeit Minimized) ? I never even had it on during my last couple flights so I'm interested to see what it's like with the Debug tool open which I will be doing very soon today.
Thanks again.

I have since discovered some things that made a HUGE difference in my graphics. First of all, I don't put ANYTHING in the Pixels Per Display Pixel Override slot any more. I leave it a Zero which is what it defaults to every time I restart it anyway. I have also increased my Encode Bitrate (Mbps) to 900 and today I adjust the "Graphics Preferences" SLIDER all the way to the Right or 1.5 (off hand I don't remember what the resolution is now but it's maxed out). It greatly improved my graphics and actually seems to be more in tune with what I'd expect if plugged directly into my GPU.
The only shortfall from doing this (that I've found so far) is that now I get a bit of a stutter when I move my head too quickly and mostly only when looking outside the cockpit.
I'm sure there is something I could tweak to make it better. I just hope I find said solution .. before it makes me puke !
In DCS I've also reduced Sharpening to 50% whereas I had it at 1 (slider all the way to the right previously). I don't know if this helped or did anything but it was a suggestion in the video that showed me how, why and where to adjust the Graphics Preferences (slider). Here is the video link if you care to see for yourself. Essentially, it's all Greek to me but that one thing has done more for me than the last month of farting around changing settings.
https://youtu.be/51oc4lrYB4E?si=OjRIyyhUtyEJ16ad
PS: I do NOT use SteamVR. I only currently use my Quest 3 for DCS Standalone and that's it.