Well, I think I’m really under 20 fps! But surprisingly it’s not the bad. The frame rates for me are less important than being able to see instrumentation.
I’d like a 3070+ card but the prices are insanity at the moment.
After an intense day of testing and bug fixing, the OpenXR toolkit release is right around the corner. In a few days, you will be able to download and use the new software. While waiting, here is the full list of changes (from both the NIS Scaler and the Hand Tracking layers):
Changes in Beta #2
- Add support for AMD FidelityFX Super Resolution (FSR).
- Add support for DX12 (experimental).
- Add configuration via in-headset, on-screen menu.
- Add FPS counter and performance overlay.
- Add World Scale override.
- Add Prediction Dampening (reduce shaking).
- Make in-game hotkeys customizable.
- Integrate new project logo.
- Add an option to disable the layer without having to uninstall it.
- Upgrade to NIS 1.0.1.
- Configure the NIS shader to use optimal compute scheduling based on the GPU brand.
- Add debug message to investigate swapchain issues with certain OpenXR runtimes.
- Moved logs and screenshot into subfolders in
%LocalAppData%\OpenXR-Toolkit(no filesystem clobbering). - Try to load hand mappings configuration file from
%LocalAppData%\OpenXR-Toolkit\configs(which is user writable). - Fix “index tip tap” hand gesture.
- Allow multiple gestures to be bound to the same controller input.
- Tentatively fix loss of tracking/loss of synchronization with the emulated controller.
- Add controller timeout to simulate shutdown of the controller after loss of hand tracking.
- Fix frequent
XR_ERROR_LIMIT_REACHEDerror when using the OpenXR Developer Tools for Windows Mixed Reality.
64 Likes
You’re a real gift to the MSFS VR community.
13 Likes
Very impressive list a new functionnalities!
It’s not a Beta 2, it’s a brand new product 
Swiss knife for VR is there, thank you so much.
2 Likes
That is an incredibly comprehensive tool indeed. Tremendous work Matt. Your contribution is an absolute boon to the VR community and deserves our sincere gratitude. Thank you very much indeed.
3 Likes
Great question…..I was hoping someone would ask that.
A little off topic for Q2 owners, i read recently that switching the headset to developper mode to totally deactivate the guardian can help eliminate some stuttering issues, as guardian take some headset CPU ressources (according to the shape of the guardian). No tested yet.
example : https://www.youtube-nocookie.com/embed/w0PVPRmdtJM
4 Likes
Cant thank this gentleman enough…VR is beginning to look like what it should be in my G2. Thank you Sir !
Will FSR vwork for all users (Nvidia cards)?
We can say one day, “we knew him…” when you’re famous 
4 Likes
yes it should
Amazing! You’re doing Asobo’s job here, enhancing the VR implementation even more than what I’d have thought possible…
Since you mentioned a new FPS counter and performance overlay: Can it show ASW/motion reprojection status as well? The sim unfortunately tends to turn it on by itself even when disabled in the Oculus Tray/Debug Tool, so being able to see at a glance if it’s on or off would be very helpful.
Right now I have to switch between Oculus performance debug overlay and ASW stats overlay. A single, unobtrusive performance overlay with FPS, perf. info and ASW status would be so much better.
Ultimately, if your toolkit could actually override ASW and keep it off if so configured, that would be the perfect solution. May be too Oculus specific, but since Quest 2 is the most popular VR headset, I’m sure it would be helpful to many, so I wanted to bring that up for your consideration.
I cannot believe what I am reading. Thank you for all this work.
Would you mind elaborating on what scenarios would benefit more for nis vs fsr? I imagine fsr would be more beneficial.
Also what can we expect from the prediction dampening? Is this just for controlling the settings in VR or actual head movement dampening across the entire game?
yes, you are truly gift for all of us vr flyers…
thank you for the enormous amount of work you put into this project and I’m curious about what else you can surprise us with
brds
Martin
1 Like
I don’t think that’s possible. This would require to have an API to interrogate the OpenXR runtime. These are typically not exposed to developers and only for internal use.
Yes 100%, all cards.
I think this remains subjective. I am hoping that everyone can find their happiness in the choice between the 2 and the various factor/sharpness settings. But no rule of thumb AFAIK.
It’s VR only and mostly intended to address the issues described here:
5 Likes
Oh thats exactly what I was hoping! Thanks!
Hi - I have been trying the tool, and want to compare with and without. Sounded easy… BUT I cant get the tool to deactivate! Even after restarting the PC and not running the tool, when I go into the sim I still see the effects of the tool (can turn on and off the sharpening effect with CRL-F1). Next stage is to uninstall the tool and see if it realy has gone- but do I then need to edit the registry or OpenXR settings manually? How to do a complete uninstall?
Oculus Rift S, NVIDIA 2060
If you select FS2020 from the list then uncheck “Enable NIS Scaling” you can still do Ctrl-F1 in the game?
I see my mistake now… No I hadn´t unchecked the “enable” box - I just closed the tool and was surprised when its effects were still active after restarting the PC. I guess because of the cfg file? So now I can indeed deactivate it to compare . Thank you for your reply, and for your hard work
1 Like
Can you provide instructions and/or screenshots of how this works? Also, is the FPS and performance stats toggleable and visible from this?
Really excited for the active development this is seeing. You’re a boon to the community.
With the new FPS and performance stats, have you considered adding any sort of “setting snapshot” benchmarking tool? My thought is while flying in a given scenario, a user could trigger something via hotkey or the UI, and it would log the current settings of the config tool, relevant sim settings and sim data (location, weather, traffic etc.), and any other settings accessible (like Nvidia settings), and chart it.
Over time as people tinker with things, you could see very easily on a chart what had the best performance, and perhaps even select one or more chart points to enter a settings “diff” mode and see what was difference.
A part of the challenge with all these layers of settings in different places is benchmarking across them with the added complexity. This could go a long way to solving that.
1 Like