OpenXR Toolkit (upscaling, world scale, hand tracking...) - Release thread

When I first use toolkit sharpening, on G2, CAS was less shimmering, but NIS at similar levels made for shimmering that was horrible. 65-90% range. Felt like double sharpening or something like that. Bucchia wrote somewhere he enjoyed NIS at 20-35% and I tried it. Less is better. Bucchia enjoyed 20% and he was right. I know nothing about settings in pimax or pitool. NIS runs on Nvidia hardware, and works well with dlss. Both Nvidia solutions

If you have a rtx4090 and a good cpu like my i913900k , like I have, or newer AMD x3d you’ll have the best right now imho.

I just upgraded my 3090 to a 4090 and would be curious to hear what you or others suggest. I wasn’t immediately blown away with my current settings now running on a 4090, but I haven’t tried Motion Reprojection or Turbo Mode yet. I have a i9 12900K, 64G DDR5.

What headset do you use? Is your 4090 utilized 90-100%? If not:

  • switch from DLSS (if you use it) to TAA
  • apply resolution override in OpenXR Toolkit (up, to supersample)
  • increase LOD,
  • crank most of your in sim settings to ultra (keep clouds at high).

push your 4090 to the limit, above 90% to unleash it’s full potential. This is what you paid for.

Thanks. Reverb G2. My GPU is running at like 40%, but I’m only getting 40 FPS on average and it goes down to ~20 when landing at a busy airport. My LODs are pretty high (at max or near max).

As a fellow 4090 user, I’d say your next logical upgrade would be a nice new i9 14900k. Flight sims like msfs are still sooo very much single-core heavy that better/faster will always help quite a bit. I’m even seriously considering upgrading my i913900k to one, also with faster (+6500) ram (currently 32Gb 5200ram).

I see you have a G2 so I’m sorry I can’t advise you on settings for that since I don’t have one. I’m sure other G2 users will chime in and help. Good luck mate and cheers.

You are likely CPU bound with TLOD that high. Even with a 4090 and a 5800x3D, I have my TLOD set around 120 so I can run my Pimax Crystal at native resolution (which I cap at 45fps). I run a mixture of ultra and medium, this makes me GPU bound with a bit of headroom for the CPU; the GPU runs close to 100%.

For G2 which I also have the 4090 allowed me to supersample above native resolution to get far better resolution and sharpness in the sweet spot.

Regarding the latest 1400K chips, reviewers are saying it’s hardly any better than the 13900K.

As long as FS does not improve its VR, we will always be able to have racing horses, the track will remain for mules…

Yep, TLOD’s effects are awful. I run terrain LOD at 100 even on a 7800x3D because I don’t see much difference when going up a few tens, but performance definitely suffers.

My take on TLOD (above 300, clearly beneficial, the most notable difference is the tree draw distance in the mountains for example at LOWI) with Crystal, 7800x3D and 4090:

Interesting, I thought tree draw distance was determined by the trees setting? If not, what does that one even do? Density?

Random question I asked myself earlier: Does Turbo Mode interact with the “VR Prerenderes Frames” (1-4) setting in the Nvidia CP in any way? Possibly even override it? Or are they completely independent and complement each other?

It’s completely unrelated

Do you have a recommendation for that Frames setting when it comes to minimizing stutter? Theoretically the more prerendered frames, the less stuttering should occur, no?

I did lower my LODs and even switched to DLSS Performance. That gave me 60+ FPS in Turbo mode but on final approach to a relatively simple airport (KSNA), my FPS drops to 15 with stuttering.

Hard to say. Some airports just do that in the sim, more so with complex airliners. I can fly into major airports here in Oz or around Rome say and have no issues at all, but in Tokyo say, I get a stutter fest. At London Heathrow all the photogrammetry lowers FPS, but it’s still flyable for me. It’s more to do with the sim, rather than any particular headset.

Cross posting from Pico 4 thread…

Today I installed the new release of VD with the OXR runtime included. Is SSW supported with the release version? With it enabled (which is my preferred usage) i was getting nasty jitters when moving my head around… it seemed like the Pico wasn’t providing Headset postion change data for image reprojection. When i disabled SSW, it was fine. Also, should i make any settings changes now that SteamVR is eliminated?

Edit: Mark at flightsimhanger indicates that the Beta software didnt support SSW (for quest 3 at least). Is that the case still for the release and does it apply to Pico 4 as well?

I’ll need to test out the official release version with SSW to see - I never had any issues with the initial standalone beta plugin and SSW. Do you have Turbo mode enabled in OXRTK? I believe that breaks motion reprojection.

No turbo mode. Never had luck with turbo in the past.

Did quite a bit of testing, bottom line is I get much smoother performance with SteamVR regardless of SSW on or off. I imagine it’s somewhere in my settings, but why fight an already excellent experience?