have you followed the instructions here, in particular the step where you tune FS2020.cfg file to emulator the Q2 controller (otherwise defaults to HP controller). Missing that would explain the lack of interaction.
1 Like
I did not! TY for the link. Wow, that’s intense to setup. Are there any out of the box defaults or do I have to map from scratch?
How well does it work at this point? Something you use all the time instead of controllers now? Can I raycast?
I followed these settings for OpenXR Toolkit for my 4090/G2. Resolution 5000 x 5000 'ish and DLSS Balanced (yet to compare with DLSS Performance). Fantastic results and the best ever clarity/performance/visuals yet. Like a new headset. Thanks to Open XR Toolkit.
4 Likes
Except there’s still no fix for glass cockpit clarity with DLSS.
When using supersampling and CAS DLLS blurriness for EFIS is pretty much non-existing. TAA is best but DLSS can be very close. Yes, you need a beefy graphics card to achieve this, so unfortunately it is not a ‘fix’ for those that don’t have the required GPU power.
1 Like
Is the new CAS mode basically the same as FSR@100 plus whatever sharpening value you set? Because the FSR sharpener is also CAS, right?
Not the same. FSR uses a different sharpening technology, called Robust Contrast Adaptive Sharpening (RCAS).
CAS definitely has more of an impact than FSR.
1 Like
Hey all,
There will be a minor update 1.2.3 released soon (hopefully before xmas) with the following:
- Fix Turbo Mode crashes in Flight Simulator 2020.
- Do not display CPU frame time in the overlay when it cannot be determined reliably.
- Add a “target frame rate” option to have the overlay give headroom based on a desired frame rate.
- Add an option to cull hidden area mesh (mostly for iRacing, only supported on certain applications).
- Workaround to OpenComposite issue with DCS on WMR (timeout error).
- Workaround to Oculus OpenXR issue with OpenComposite ACC (call out of order).
The last 3 changes are not really applicable to flight sim, and are meant to address other common issues in other applications.
The overlay changes are meant to address confusion caused by the “CPU bound” message and incorrect readings while in Turbo mode, in cases where the CPU frame time cannot be reliably measured from outside the game. The value of rdr CPU will still be displayed in those situations, but app CPU will be omitted. The “bound” messages and headroom messages will only be displayed if the CPU frame time is available and the user configured a target frame rate.
30 Likes
Any update on the two WMR motion reprojection improvements you mentioned earlier in the videos?
1 Like
My understanding is the resolution override in the Toolkit is essentially the same supersampling as dragging the OpenXR slider. The difference here, is that OpenXR is global, where the Toolkit setting will be applied to that application. (In this case MSFS)
Regardless, I was apprehensive to try this because I was getting pretty fantastic results with 200% OXR and DLSS Quality. But for kicks, I set OXR to 100% and used the Toolkit override (mostly because I wanted to see the actual resolution numbers) and set it to 5000x4800’ish. I disabled OXR Toolkit CAS and re-enabled FSR with no upscaling, because I wanted to use the RCAS instead, to reduce wobbles/shimmering. CAS, particularly the built-in MSFS CAS sharpening creates bad shimmering for me. Anyway, with cranking the resolution to 5000x4800’ish, and setting DLSS to balanced (I even went with Performance to see if I could retain visual fidelity) I was able to gain a big enough performance gain, that I could enable DX12 and still lock 30-45FPS with MR. And with FSR sharpening at 100%, I was shocked to see really impressive clarity even when setting DLSS to performance. DX12 is now loading a lot more in to VMEM which my 4090 can handle and there is a noticeable improvement with transitions in to/over airports. This is the first time I have been able to use DX12 effectively and so far I’m impressed with it.
So @MickT1701 's suggestion actually works. Again, will really only apply to those with something like a 40xx series GPU because you are super sampling like crazy. I never bothered trying anything near 5000x5000 because it just seemed absurd lol. And it is, if it weren’t for the DLSS upscaler and my 4090. I’m going to keep flying with these settings for a while.. so far very promising.
New version 1.2.3 is out now: https://github.com/mbucchia/OpenXR-Toolkit/releases/download/1.2.3/OpenXR-Toolkit-1.2.3.msi
- Fix Turbo Mode crashes in Flight Simulator 2020.
- Do not display CPU frame time in the overlay when it cannot be determined reliably.
- Add a “target frame rate” option to have the overlay give headroom based on a desired frame rate.
The changes below are not applicable to MSFS:
- Add an option to cull hidden area mesh (mostly for iRacing, only supported on certain applications).
- Workaround to OpenComposite issue with DCS on WMR (timeout error).
- Workaround to Oculus OpenXR issue with OpenComposite and ACC (call out of order).
- Fix screenshot showing both eyes with certain applications (eg: iRacing).
I will not be paying too much attention during the holidays, so in case of issues, please kindly file a report on GitHub, and revert to 1.2.2. Don’t forget Safe Mode if you need to get out of trouble.
Happy holidays!
25 Likes
As it should be. Go enjoy the holidays and take a much deserved break! Happy Holidays Matt, thank you for all you do and the awesome year!! Going to install the new version now. 
3 Likes
I’m not familiar with what CAS is. Can you elaborate? I know there’s NIS and FSR upscaling in OXRTK, and DLSS within the sim. I don’t know how to enable CAS, or what RCAS is or when I should be using these. Right now my issues are trying to get better performance, increased cockpit clarity and sharpness on a 3080, 5800X box with a Q2. Ideally I’d love to get rid of the shimmering as well.
Anybody else who has updated to 1.2.3 experiencing crashes with FFR? I can’t enable this anymore because I will get a CTD within 5-10 seconds. This has never happened before. Might have to revert to 1.2.2…
This is strange. I’ve heard of a crash in MSFS when enabling the new “Cull outer mask” which is not needed in the first place in MSFS. So make sure you don’t have that On.
Well I have “Disable Mask (HAM)” turned on in SYSTEM. When this is on, the option for mask culling under FFR disappears from the menu entirely. But I double checked anyway by disabling HAM under system and the culling option appeared under FFR and is not enabled, so i’m good there.
Just tried it again, and as soon as I toggled Fixed Foveated Rendering to on, immediate CTD. I toggle this off and on all the time depending on the conditions. Never seen this happen.. ever.. until the 1.2.3 update tonight.
Cool yes that is expected.
That I have no idea, I did many toggle on/off of FFR as part of testing and not seen that. One possibility would be to reset all OpenXR Toolkit settings and then redo settings one at a time until we see what makes it crash.
Yup. I am heading out of town for Christmas, so I wont be able to test until I get back. Will post my findings next week!
I tried the new 1.2.3 version today with great success. I’m glad to see the CPU bound message gone, more so because the reddish text colour in which it was displayed was quite distracting.
I was also able to use turbo mode for the first time without CTDs. Well I did have one CTD with it but it was after going out and back in to VR and changing OXR render scale in between, so I was pushing my luck. Turbo worked fine for two 10 minute flights and netted a 10-20% performance boost. I’ve no idea what it does, but now that its working and actually ‘turboing’ I like it.
Thanks for all your efforts over the year with this excellent tool @mbucchia. Take a well earned break, you’ve deserved it!