First Steps with a Quest3...and I need help

User Support Hub Virtual Reality (VR)
, , ,
21

A little more play and I think I have reached the limit without going to 3rd party stuff like OpenXR Toolkit et al.

I’m now at an Oculus Link res of 1.4 and in-sim running at TAA, 110 resolution, 200 sharpening and all sliders on “High” preset. It’s not clear on the instruments but it is just about usable for me, as a choice between using VR & the triple-screens.

I may be wrong but if i want to also play with Steam apps like Assetto Corsa etc, I’ll need to go with Virtual desktop yes? And in doing so I’ll also need to go WiFi6 as VD only uses WiFi - am i correct here?

If so then getting a WiFi6 router as an access point is pretty much the way forwards I think, even if I keep the cable to charge while playing.

22

Forgive the click-baity title, but try this. I made it for the Q2, but it works for the Q3, as well. This was all made while I had my 3080ti / 19-9900k setup. Got me smooth VR experiences even while streaming in VR… Hope it at least helps a bit. :slight_smile:

1 Like
23

No, you can still use SteamVR via cabled Link if you want.

I do personally prefer the wire free experience and then VD is well recommended by most.

I don’t actually have any issues with Air Link - but I do have VD and in general the experience is more straightforward with VD for access to your SteamVR library.

You also have the option of Steam Link for free in the Quest store - worth a try at that price!

I use a WiFi 6 router (not 6E - although both the Q3 and QPro support that) dedicated for the job. It uses a different channel and SSID to the rest of my WiFi so my connection is clear (and in the same room as my PC).

All the best!

1 Like
24

Having done a lot of playing around with mine, VD is the way to go.

2 Likes
25

Update…

I have been messing about and have now got a good WiFi6 connection setup, I have virtual desktop set to Ultra and the bottom encoding option on the list, I think it was something like AV1 10bit?

I also turned the performance overlay.

In-sim, the performance shows as 41FPS taxiing on my home airfield (i can’t fly at present as I’m set up for racing so no yoke and pedals etc) , the latency shows 80ms - i have no idea if this is bad or not?

I have also updated my Nvidia driver to the latest flavour, and set FS2020 to DLAA.

The end result is that I do think the Q3 will work, but, to give it a fair trial I now need to order some custom lenses because I have one eye sharp and one blurry - if i wear my reading glasses, the other eye is sharp and the opposite is now blurry.

I also need to get some back-weight, I have the upgraded strap but it still pulls on my face below my eyes, pulling on the back strap a little helps this.

However, before I order the lenses, I am due for an eye-test so it makes sense to get that done first and get a new prescription.

I have also found the OculusDebug tool now, and installed but disabled OpenXR tools for future use.

26

I use this head strap

https://www.amazon.com/gp/product/B086Y6V2H4/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1

And this battery

https://www.amazon.com/gp/product/B0B7XPZHXQ/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&th=1

Just find yourself a 6 inch (or so) cable to go from the battery to the headset. You’ll also need a thin metal strip to glue or tape (I just used gorilla tape but it’s ugly shrug ) to the battery so it sticks to the magnet on the head strap.

It’s very comfortable and the weight balanced the Quest 3 perfectly. I can wear it for hours with no discomfort and it charges as fast as the Quest drains meaning one battery + quest you’ve got about 5-7 hrs I would guess.

1 Like
27

Good to hear you’re getting somewhere with it.

Remind me, what GPU do you have? And CPU?
I’d think you can probably run Godlike with DLSS Performance or Balanced if you have a 16gb VRAM card at minimum.

Yeah that is the encoder/decoder exclusive to the Q3. I can’t see any difference between that and HEVC 10 Bit, but in theory it should give a bit better clarity.

Either of those is fine. The others (not 10 bit) have banding of colours in areas of subtle gradients (i.e. clouds) so avoid those.

Are you using SSW? Latency is a bit high but really as long as it’s a smooth end result, who cares. It’s not a competitive shooter :wink:

Is it smooth? No hitching / stutters / freezing?

Yes!!! Good call! This was the final step I was missing in all my fiddling. Didn’t even think about upgrading my eyes but I have and it’s made a big difference!

Got lenses that clip in perfectly for the Q3 online for around £70.

The Debug and Oculus Toolkit won’t work alongside VD (I’m sure you know that).

OXRTK does, but as others have mentioned it’s no longer actively developed. The developer is now working with the VD developer so I guess and hope and expect a lot of the useful features of that will come across to VD natively in due course.

Honestly I stopped using the OTK last weekend just to try. It is useful for sure but it’s yet another layer of settings and processing and chance to introduce lag or issues. Trying to go naked for now!

I kind of miss it, but I do think it’s (possibly, maybe) smoother without it. But it’s so highly dependent on where and what I’m flying so it’s probably not really the reason it’s smoother. Darn sim is a slippery fish!!! Probably 99% placebo.

I was using the FOV reduction (to gain a bit of sharpness) and the Foveated rendering (to free up the GPU for a higher resolution) then setting custom resolution. And the colour balancing (to make it look more natural) and the motion over-prediction adjustment at -60 or less (to make looking around more stable). It’s the last one I really miss the most so I may go back to it!

1 Like
28

Its a 3080Ti and I think was an I7 12700K but possibly a 12900K

SpaceWarp is disabled.

I’m not done testing yet but 41fps is only 5fps lower than I was getting on the 1440p triples so hopefully I can keep it there.

It did look pretty smooth but really need to get my controls mounted again so I can test fly, I might wait a bit for the eye test though.

29

Use SSW and try 72Hz. It will be more consistent.

Also try OXRTK just for the over-prediction setting if you find the cockpit jerky when you move your head fast or lean. Its magic :wink:

Set a large negative value, at least -50.

Also — and this may just be a quirk of my machine as others don’t seem to need this — but using Riva Tuner Statistics Server to lock my frames to 36 (half the Hz you select with SSW on) completely smoothed everything out for me. If I disable that it’s totally awful.

Worth trying Godlike IMO. Easy to try! It’s significantly clearer looking. Just make sure to restart VD app (in the headset only: Quit > Load again) when you change any resolution type settings for it to take proper effect.

Just check VRAM usage is not going too high in a demanding area like Venice / New York / Tokyo. 90% is good.

1 Like
30

When using VR with opendesktop over wifi, where is the correct/best place to lock the frame-rate?

If using SSW I believe OXRTK Turbo mode has to be off?

I’ve got my eye test booked for later this week :slight_smile:

31

No idea. SSW alone (which should theoretically seek to limit to half the Hz) was not working in MSFS. Locking in Nvidia Control Panel was not as ‘accurate’ as Riva. Riva is the thing that saved me 100%. Strange… but true! :smiley:

It can be on. There are some other things that OTK says break Motion Reprojection. And that may well be the case for other headsets but seems the Meta/VD SSW is not the “same” kind of reprojection, and these things do work. Whether they have any positive effect is a different question. Half of this stuff is placebo / conditional & situational on the sim + fairly random I think!

Good luck with the test! If you want to know, this is where I ordered my lenses from (official supplier for Meta):

1 Like
32

Thanks for the lens link @Baracus250, they came very quickly and do seem to help reduce eye strain a fair bit.

1 Like
33

Great stuff! And better clarity?

I seem to have found a magic button over the weekend with my settings. Pumped up to 3600 ish resolution with online traffic on, all the We Love VFR’s, Mamu powerlines, solar farms, marinas, churches, ski lifts. About 250 other mods active and it’s running really well and looks great!

Still got some hitches but turning everything down or off doesn’t eliminate those still. Mystery but it’s running better than ever now. Watch SU15 destroy everything soon :rofl:

1 Like
34

Why start another thread though? :slight_smile:
We are trying to help for the same question on the other one you started. Shall I get the mods to merge or remove this?

But, essentially, no there is no set path I feel. You have to piece together what works for you and your system and tolerance or preference for what you want from it. All you can do is learn from others ideas, try, tweak and find your own combination.

I am still always fiddling so even if I gave you a “path” today, that might be different tomorrow anyway.

I think the less you NEED to tweak the better though… less layers. I removed Nvidia Profile Inspector from the mix. Just set Anisotropic to 16x on the FlightSimulator.exe and off in the sim. Global texture filter quality to High Performance and Prefer Max Performance on the power plan thing.

Still using OXRTK to increase resolution (around 3500). DLSS (quality setting there or in VD Godlike etc doesn’t matter as OXRTK is overriding it anyway) and not too greedy on in sim settings. If I could find a text list I would paste it here (or there :wink: ).

I sttil find I need OXRTK to get the best out of it. Tried without and I cannot run as high resolution and it maintains smoothness everywhere. In OXRTK: Higher resolution, lower FOV (85%), Mask foveated rendering (preset quality / wide), over-prediciton compensation (in Input) at -90%. No CAS or any other upscaling though. Can’t remember if I am using Snapdragon upscaling now. Just AMD Fidelity at 120 and the VD Sharpening at 70 I think.

Using only 60 bitrate (it looks no better at 200 or 120 for me, but it’s less likely to crackle audio at 60 I think). Bunch of other things I forget now - not on PC today but I will be tomorrow so I can fill in if you still need more pointers.

2 Likes
35

Apologies to all, yes please request the thread merge, my mistake.

It just seems overly complicated to me at present - I am also a fan of using as little as possible in the pathway, never had profile inspector so thats one thing.

Maybe we could use a list of things that do not play together - like sharpening in too many places etc.

I have no issue with OXRTK but do we also need OculusDebugTool as well? Lots of users say to put EncodeBitrate to 500 but not why or if that figure is available inside VDT as well and so on.

I did look at the notes for OXRTK but found it a bit confusing when it got Render resolution, world scale, upscaling and scale/resolution in general LOL

I would of course like any pointers possible, this is a minefield in so many ways :slight_smile:

1 Like
36

No problem, done - - let’s continue here :wink:
There are enough threads about this topic already :wink:

… + …

I’m confused. You are ok with it or confused? lol

If you are using Virtual Desktop (you are now??) then as I said before, you cannot use the Debug tool or the Oculus tools. VD bypasses all of that. Those are just for AirLink or the cable link.

Are you sticking with VD now you got the WiFI working OK?

If so, the bitrate for WiFi is all you can change (I think!). And as I said, it’s down to the eye of the beholder but for me ~60 bitrate is perfectly fine and less “demanding” on the airwaves :smiley:

You can try some of the upscaling methods and just see if you prefer it. With a higher resolution I think I really don’t need those and it runs perfectly fine with everything else I have set now.

What I did was just open the Win + G key (simple performance monitor) to check GPU and VRAM usage, and bump the resolution up and until it was high, but not maxed at 100%. I have around 80% usage and 75% VRAM in a heavy scenario. Could probably push a bit more. If I use DLAA then it’s 100% all the time (but still smooth, actually, just seems like having SOME headroom is a good idea and less taxing on heat and the card in general).

…but YES this WOULD be useful. I really don’t know the answer though. I mean MAYBE I could lower the resolution in OXRTK then use CAS. Is that more efficient? No idea. I tried it and doesn’t really make a notable difference. Does CAS make the GAME forced to render at a lower resolution even if I have 3500 set in OXRTK?

I use Riva Tuner as I mentioned before. By FAR the best (for me and my system). Created a “game”, pointed to the flights.exe, set half my Hz refresh there (36 for 72Hz with SSW on).

Ain’t that the truth!
I got to the point that I man totally fed up with tuning it. I got to a decent enough place now, it’s really more than acceptable and I am just trying to enjoy it now and not fall in to the trap of “what if I try this”.

It’s all for nothing when next day MSFS can just behave differently having made NO changes. Or the next SimUpdate resets everything. At the end of the day, is it smooth “enough” and clear enough for you to enjoy?

1 Like
37

Thanks for the tips so far,

I’m going to go back over my settings from scratch I think. Now I know that the Q3 can actually give the clarity I desire, I just need to concentrate on getting the smoothness.

At present It’s not there, I have seen the clarity but not the smoothness, its very jerky which is off-putting to say the least. My frame rate is around 33-34FPS which is not brilliant and I find that odd as I have it set for a low-end PC presently which makes me think some other setting is not right as I feel a 3080Ti can do better.

I might be able to settle for using the Q3 for helicopters where I’m generally not making “flights” but more just messing about sightseeing etc so my cockpit instruments are of lower value to me, then I can switch back to my triple setup for “serious” flights in GA planes. The good thing is that the Q3 was of such a reasonable cost that I’m not worried about having to use it all the time like I may have been with a Crystal etc at 3x the cost or more.

I’ll get back on later today and start digging at the settings.

1 Like
38

You mean WITH spacewarp on?

You need to get it to be the SAME (exactly the same) as the Hz refresh. Anything else will be horrid in my experience.

1 Like
39

Thats what I’m off to work on now, got a couple of hours spare.

I’ll try and work through the whole pathway from VDT to OXRTK to FS and see what looks odd, i’m sure something is set wrong :slight_smile:

40

Just had a couple of hours messing with settings.

I’ve currently got most of it set as you mentioned @Baracus250

I don’t recall if you touched on TAA/DLSS etc? but i’m currently on TAA.

I turned off “cap frames” in OXRTK expecting to see the raw FPS but, while it has at least now reached 36/37FPS and can hold it, it does not go above so I’m not sure if I have a FPS cap set somewhere else?

At 36FPS it does seem to be usable, at least for helicopter fun; I have the OXRTK performance overlay on and it’s showing around 20-30% CPU and 15-20% GPU overhead which seems ok I think but the FPS still does not go over 36/37.

Any change of TAA render resolution in FS2020 tanks the CPU overhead into the red so it seems I cannot oversample?

SSW is on and set to “Always on” in VDT settings, 60Mbt video rate, variable bitrate.

I’m sure there is a reason it won’t go over 36/37FPS but not found it yet.

Edit,…
I recall setting a render resolution somewhere, very early on, it was at a point where you click on a “headset” icon and choose settings, render res with a slider that was on 1.0 and I think i stuck it on 1.3 - I’ll need to find that again :slight_smile: