I just wanted to add my thanks for this great tool. It’s amazing as-is and after reading about your planned improvements I’m even more excited for it.
Buried in the thread now, but here is your answer: OpenXR NIS upscaling software - Release thread - #270 by mbucchia
After you install the NIS scaler tool, it has a checkbox if you want to disable it. So there’s no complication with this tool.
When you modify other files, like config files, it does get complicated. I use a tool called OvGME. Basically with that tool you can create a copy of the file you want to modify, then change all the settings in that duplicated file, then with the click of a button in OvGME it replaces the original with your modified copy. To disable your modifications and re-enable the original you un-check it in OvGME. It makes managing all the variables easier because you can easily see all the files you modified in one tool and enable/disable them with the click of a button.
This looks amazingly promising. I might have misunderstood, but is the intent then that the interface is accessible and visible from within VR? You note the mouse/VR controller, but I was unclear about whether the actual settings window would be visible w/o taking off the headset, peeking under it uncomfortably, or pulling up an overlay (inconsistently laggy).
Some additional questions if you don’t mind (I know you must be slammed, but this is exciting stuff!):
What necessitates whether something requires existing and re-entering VR to enable a change?
Can you explain what “World Scale” is? Would changing this make the cockpit (and world) appear larger or smaller?
Do you have a publicly posted roadmap tracker anywhere sort of like the Asobo devs do? Would love to follow along if so.
i have tried the BEta1 wich works very well. FPS are far better, visual quality better for the cockpit but lower for the landscape. i have to make some test to see which set of parameters are the best. Instruments are now very sharp. and when i watch the ground while flying, i have no more stutter. i’m very happy for this
A very big thank to you (and @CptLucky8 even if not involved in this beta1 if i’m good but for the future release to come).
(And if you put a donation/offer a coffee button somewhere, i will be one of the first to click to thx both of you !)
Yes there is a UI you can see without removing the headset
There are 2 classes of things:
a) Things that require the game engine to restart because they change some intrinsic properties such as the rendering resolution. The rendering resolution is something that must be negotiated with the game engine. We can’t just say “hey from now on I impose this resolution”. Restarting VR causes this re-negotiation.
b) Things that are just much more complex for me to implement without requiring a restart. An example is the hand tracking support I’m adding, technically it could be enabled/disabled without requiring to restart, but this would require more complex handling. So it’s not a priority and will require a restart for now. Could change in the future.
Not really. Just these threads on the forum. They just get super hard to follow because too many messages. Someone suggested a Discord but 1) I have never used it 2) I don’t really have time to play with it and learn. I asked for guidance here but did not see any reply: OpenXR NIS upscaling software - Release thread - #428 by mbucchia
Ask to Jean-luc, he is a discord master now
I tried this for two hours last night and to my horror, somethings not right. Although the NIS does improve the clarity when active, but it breaks something else. In other words:
55% NIS (with the NIS turned off) looks FAR worse compared to the 55% scaling within MSFS2020.
Why is this? The NIS effect clearly works, but it appears to cause greater pixilation to start with. The resolutions appear to match (i.e. 55% MSFS = 55%NIS) but it is clearly smoother with good old MSFS At 55%. I think that it has to do with the render pipeline and that the NIS breaks TAA?
First off I want to thank mbuccia. The software clearly works. I may be doing something wrong, but I tested and retested. I also tried 75% MSFS vs 75% NIS (with upscaling off) and again it was clearly worse. Frame rates were the same despite these differences. In any case, I found native 75% to appear to be better than 75% NIS (Without upscale on), which surprises me because the FSR for openVR is a godsend for Elite Dangerous, DCS etc.
CAN ANYONE REPLICATE? I WOULD LOVE FOR OTHERS TO TEST THIS! The images should be the same, but they’re just not?!
Pimax 8k X
Also agree. NIS kills the sharpening. FSR is much smoother. So set the NIS sharpening to 0 or .1 or at most .5 as it was overpowered. The openVR versions from folder were like this as well. FSR 100% sharpening roughly equals only 10% NIS sharpening! Also see my post-reply above about the native NIS appearance (with upscaling off) vs using just the in game slider. I feel like we are getting wool pulled over our eyes, only to then have glasses put on to show the obvious improvement of NIS. Regrettably I feel it is somehow breaking its own benefit
Can you explain what FSR is?
Can someone help me with the resolution values reported by the NIS tool? This is for the Reverb 1.
When using Windows OpenXR I set the developer’s tools to 100 % and the NIS tool reports 3140x 3084.
I now switch to OpenXR via Steam VR where I set resolution per eye again to 100%. Now the NIS tool reports 2204x2160. On the other hand, I can achive a reolution of 3140x 3084 by dragging the SteamVR resolution slider to 204%
My guess, the setting in the Developer Tools if using Windows OpenXR is the combined resolution for both eyes while that reported by SteamVR is (as stated) per eye only (but sholdn’t the resolutions be twice of the per-eye-values in this case?). This would be in line with my observation that 100% in Windows OpenXR gives a better display in MSFS, but lower fps than 100% using SteamVR OpenXR.
There’s a known issue with the configuration tool when using steamvr custom resolution:
Thank you. That’s it.
FidelityFX super resolution. AMDs answer to NIS and in my opinion a less obtrusive result. Softer sharpening.
Yeah thats not the issue. I have it simply set to 100% in steamVR. Something else is up.
Well you’ll be able to test FSR with the next version of the tool… Maybe this will work better for you but TBH 55% scaling is a pretty aggressive setting fir a high resolution device, so I think your expectations are a bit too high.
I would say, that I only get decent image quality with high NIS scaling settings. That means NIS scaler at above 90%. And NIS sharpness scaling below 30% otherwise it’s overdone. OXR and ingame TAA/Renderscale both 100. Unfortunately, of course with this settings there’s not much perf gain.
Can I ask you to elaborate further? I’m a bit confused on the details still.
I’m on a RTX3080–can I still use FSR if that’s an AMD thing? If so, how?
What do you mean by “native NIS appearance (with upscaling off)?” Can you explain what things are set to in order to enable this? Is it checking the “enable” box in the config tool, but having both the first slider set to 0%?
Are you suggesting to try enabling the NIS scaling by checking box in the config tool, setting the first slider to 0%, sharpen slider to 10-50%, and then reducing the in-sim Render Scaling to 50%?
One thing also still unclear on from my previous post is what the effects are of setting the 1st slider in the config tool to 100%. Does that negate the performance benefits of NIS? Or are there still expected performance benefits of setting in-sim render scaling to 100%, then the NIS config tool to enabled and 100% (maybe with some sharpening)?
I have a question, and I couldn’t find any related topic to it in this thread:
Can it be that the NIS sharpening is always the same on my system?
I had set the sharpening to 60 and compared very thoroughly the instruments in the Just Flight Warrior by switching back and forth with Ctrl+F1.
It is clearer and sharper then default.
I did the same with shapening set to 1 and even tried with 0.
But the effect is always the same, not more nor less, and with 0 it`s still the same.
The scaling was always the same, it is set to 65.
Is there something wrong with my setup or is it like that for everyone?
But in general I´m happy and quite surprised that it works at all, it`s the first noticable VR improvement that I can recognize after trying almost all available configuration guides here in the forum and from the youtubers since the release of VR in this sim
THANKS!!! I can read the numbers on the gauges now!! This is awesome. To sit on the runway and toggle with CTRL-F1 clearly shows the difference in sharpness on the asphalt… Amazing job!