OpenXR NIS upscaling software - Release thread

We can say one day, “we knew him…” when you’re famous :slight_smile:

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 :slight_smile:
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?

image

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 :slight_smile:

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

Do you have a donate link because you deserve more than just a pat on the back.

5 Likes

The website will have detailed instructions. In the meantime this should give you an idea:

That’s a good idea, but out-of-scope for me. This requires to mod the game itself through the SDK (I think) in order to get this data. Also requires the GPU vendor SDK to access the driver settings (for both Nvidia and AMD). That’s more work outside of my OpenXR layer than in it. Probably a project for a Flight Simulator modder. if someone steps up to do it I am more than happy to show them how to read the upscaling settings etc. But tbh this is the only place my layer would be involved.

4 Likes

Matthieu, this all looks very very exciting. Just curious though, does the reverb G2 support hand tracking or do I have to get leap motion or something?

This is through Leap Motion yes. WMR does not support hand tracking outside of HoloLens products.

cool, thanks.

Makes sense–there’s always added complexity when multiple layers are involved like this. I’d settle for just benchmarking the NIS Config tool settings and spitting out the NIS config settings and performance stats in a CSV format for consumption/charting elsewhere since there’s enough complexity to what you’re adding such that quick comparisons of that may be easier with logged data given you have to constantly ctrl-tab in and out (which, on the Q2 at least, does not always seem to result in getting full performance back).

2 Likes

That’s more realistic. Technically there is already such mode in the OpenXR NIS Scaler project (it’s hidden behind an secret option). I dropped this code in the OpenXR Toolkit but I can consider re-adding it in a later version.

2 Likes

So very exciting for VR users. Thank you for your brilliant app. Now part of my essential VR toolkit! Really looking forward to the update. Will it be this week?

2 Likes

Can someone advise the best way to tell if I have the sharpening too high in NIS scaler? What would I be looking for? It is currently at 90% sharpening with sharpening at 0 in the MSFS config file.