don’t think it can answer to you but here is a interresting article on Oculus link
1 Like
Yes, it’s recommended, otherwise you’re using more processing resources without benefit.
Getting no shimmering at 65 or 70% with 100% scaling .
Thanks for this great toolkit. I have to say when I initially tried it I didn’t like it at all, everything just seemed more shimmery but after following the advice to edit the config file and set sharpening to 0 I started to see an incredible difference. My G2 looks better than ever and I have both a sharper image, less shimmer, and slightly better performance than without using this tool.
Each change is only slighly better (enough to be noticeable) but they add up to a substantial improvement overall.
I have OpenXR set to 100 with motion reprojection disabled. I have in game render at 100.
I use FSR 90 and sharpening 25 and it looks and runs great on my G2.
I might experiment with higher sharpening but it already looks clear and sharp enough to the point that its showing some of the deficiencies of MSFS low textures in certain areas, so more of an improvement might not actually look better!
1 Like
KThanks for the suggestion about prediction dampening with the Buttkicker. I didn’t notice a problem, but will check it out. Is it placebo, or why does it seem like my plane (Icon A5) is moving faster relative to the ground. I like to fly low ( <1000 agl ). I’m wondering if it’s a function of a much higher FPS. I get best results at 100% scaling and 65% Sharpening using FSR
RTX3080
I9 10850
32gb Ram
Nvme2 ssd drive
Windows 10
Dx11
1 Like
This works quite well with the Varjo Aero, never thought I’d see 45 fps in MSFS with this headset. This is only in non congested areas though, but nice nonetheless.
Whattttt? Other people have reported no success with the Aero. Can you please confirm - the OpenXR toolkit is working with your Aero!? What version of the software? I have so many questions for you @supmua.
1 Like
I was getting similar type errors in the System Status tab of the OpenXR Developer Tools. I found mine were caused by the fact that my default location for istalling programs was drive D: rather than drive C:
I uinistalled, changed my registry so the default program installation was drive C: and reinstalled, the errors disappeared for me. Maybe you may have a similar issue in your system?
Gonna need to pick your brain here. Where did it use to install on d:?
I can definitely see the OpenXR Loader not being happy with this. Thanks to you I might have a way to reproduce the issue!
It was installed under Program Files, I had previously edited the registry so by default, programs would load on D: in preference to C: as my C: drive doesn’t have as much spare space as the D: drive.
I had the same problem with your first release, but was able to specify where I wanted to install it and that fixed it (took me a few days to figure it out that time!). The earlier version appeared to work ok in the sim, when I turned it on and off I could see differences in sharpness, it just showed errors in the ‘System Status’ tab
1 Like
OK so I did some testing and FSR is so much better than NIS. I have no shimmering (correction : I do), and definitely a picture improvement. (even to the cost of more aliasing)
My settings:
5800x
3090 RTX
Quest 2
Oculus Software:
Oculus SS x1.3
72Hz
ASW ON (Auto) (so my goal is 36FPS))
Sharpening OFF
OpenXR Toolkit:
FSR
Resolution 70% (1892x1916)
Sharpening 80%
MSFS:
Sharpening OFF
Resolution 100%
Clouds High
Buildings Medium (note to ALL: Don’t set this to Ultra, there is an issue (stated in a Q&A) where Ultra draws even the tiniest vent from super far away, eating ressources for nothing as you can’t even see them)
Everything else on Ultra and maxed out
Objects LOD 200
Terrain LOD 200
I have my 36FPS above New-York with broken clouds everywhere and the picture is more clear than without SS (+ I managed to crank up the LOD distance for terrain & objects as there were on 100 before).
Results: OpenXR Toolkit (upscaling, world scale, hand tracking...) - Release thread - #230 by Flobud
Now I have questions:
- How to open the .dds screenshots taken? Photoshop can’t, even online converters can’t. Are they corrupted?
- What is Prediction Dampening and what does it do? I tried some values but didn’t see anything.
- Do I have to manually disable the tool to play my other OpenXR games or is it only enabled with MSFS? If yes, can we expect it to be linked to an .exe (kind of a profile) so it only starts with MSFS?
Thanks!
- Use GIMP to open DDS
- Reduce this value if you experience oversensitivity with your tracking. If no issue then leave 0
- The ultimate goal is that this tool should work with ANY OpenXR app. But haven’t tested with anything but FS yet. So try first, if it doesn’t work please report what app does not work. Then you may indeed disable it for now.
Thanks for the fast answer, I’ll give all that a try.
That would be great. With an original quest running on a laptop (2060 GPU) I’m thinking I’d like to lock at 24 fps in dense areas like Washington DC.
Thanks for sharing your setup. I have an RTX 3070 so keen to try some of your settings in case they improve things for me.
One question, you mentioned 72Hz - are you using the default Oculus render resolution?
I think it might be something like 4128 x 2096. I can see you have SS at x1.3, so I assume you are, but just wanted to check.
Thanks,
@supmua , any chance you’re using NIS Scaler instead of OpenXR Toolkit? Perhaps this might explain the success, @mbucchia ?
People couldn’t get the NIS scaler to work on Aero. If @supmua is right then it’s a first, and it could be very useful in understanding the issue others are seeing.
2 Likes
I’m not, in the Oculus software, I set the resolution to x1. 3 (the maximum) so it’s not 4128x2096 anymore but 5408x2736.
1 Like
Not sure if you saw this already but I have a Vive Pro original and it works perfectly fine with OXRTK. I think its the Vive Pro 2 that has issues as HTC introduced an extra software layer (Vive Console) into the mix with that device (and perhaps Cosmos) that the original Vive Pro does not need/use (and is not compatible with). But Vive Pro original definately works perfectly with OXRTK.
Thank you so much for bringing us something that is literally a game changer 
You absolutely rock 
3 Likes