Sorry if this is a numpty question. Do I need to run my headset with the WMR portal and the OpenXR dev tool open, or does OpenXR “kick in” when you start up VR in the game once you’ve downloaded and set up the dev tool?
Thanks
Only WMR needs to be “open”, but the OpenXR Dev Tool must be installed to be able to use the latest preview!
Thanks @RPthreenine - I’ve managed to stumble my way through it. It seems to be offering me a very smooth experience.
Definitely worth doing.
Thanks again
1 Like
My Open XR for WMR in Developer Tools shows it was updated in the apps section but version number did not change - will see if it does once I start flying some today.
Thank you for the information. Can I ask you a question related to OpenXR? From what I can figure out UltraLeap / LeapMotion hand tracking hardware is working with SteamVR OpenXR runtime, but it isn’t available for WMR OpenXR runtime. Is there a reason for that? Are you planning any kind of support for LeapMotion hardware? Is there anything that prevents developers from writing a driver/middleware for VR controller emulation on WMR OpenXR? Thanks.
1 Like
You have to wait a few seconds after switching latest preview on as described to see the version change.
Hello OpenXR Developer! Thanks for sharing your infos.
As i do not know where else i could make wishes for OpenXR, i do it here. But if there is some other way to post wishes, please let me know.
I would like to propose something for OpenXR which perhaps would be very easy to implement with a high potential of speedup.
It would be 4 percentage values for FOV:
Top FOV
Bottom FOV
Inner FOV
Outer FOV
I have a G2 (lets assume it has 3000x3000 resolution to render) and when i enable MSFS Developer Mode with FPS display, i nearly cannot see the FPS display as it is out of sight but still displayed. So i could lower my inner FOV to say 90% which would be 300 Pixels less. If i lower top and bottom FOV to both 95% this would also be 300 Pixels less. In sum the new resolution to render would be 2700x2700, which is only 81% of 3000x3000! This would speed things up a lot!
Also it would be really cool to have FSR built into OpenXR.
So please forgive me to bother you and have a nice day!
Thomas
2 Likes
Hey @HyperJet2018,
Thanks for the feedback.
It is not possible for our team to address every feature request, especially as we are working on other products and with other developers to enable their applications.
I am not 100% convinced that what you propose here will make a difference, however you seem very motivated so I will do what I can to empower you to try this technique out. If the results are as great as you predict, I can try to bring this up to the rest of my team for further investigation.
Please note that the work below is not affiliated with Microsoft, and it is my personal contribution as a VR enthusiast, entirely built without any resources from Microsoft.
I’ve spent a few hours building a basic OpenXR API layer (ie: something that is NOT part of of the OpenXR runtime, but allows to modify the behavior of OpenXR) to enable modifying the FOV via a config file. Note that since it’s an OpenXR layer, it will work with other OpenXR runtimes (ie: not just the WMR one). However, I have only tested with WMR.
The GitHub page has instructions on how to install the API layer and configure it. The example I used is specifically for MSFS2020, and I actually used the values that you mentioned in your post.
I don’t really play MSFS so I can’t really appreciate whether this makes a real difference, but please give ii a try if you can, and report back to me.
For developers out there: this open source bit of code can be used as a stub to create OpenXR API layers to modify the behavior of OpenXR not just for WMR but any other headset.
Thanks and have a great week-end!
4 Likes
Wow, this was much faster than i even dreamt about!!! I will try it thanks a lot!! 
Have a great weekend too!
Ok, i tried it! And i could set these values without any black edges for my G2 with standard padding:
left.up=0.9
left.down=0.9
left.right=0.8
right.up=0.9
right.down=0.9
right.left=0.8
This is then 20% less pixels on both axes which is only 64% of the Pixels!! This could be a real Game Changer 
in terms of fps! But: currently in FS2020 the render Resolution did not change, i thought that it gets decreased. I could use 75% render Resolution in FS2020 and had the clarity of 100% - so this would be really great.
Sadly, the motion reprojection did not work anymore, i always use it on automatic and it did not work here. So i personally can not use this 
but others who do not use the Repro could benefit greatly.
Wow, perhaps this can be extended for Motion Repro. But if not i am happy i could test it! Thanks!!
Ok, second try without Motion Repro: works really GREAT!! I could use 100% OpenXR Resolution and 80% inGame, but this is like 100% inGame!! Its insanely sharp, you see the G1000 Text nearly like a normal monitor! And above Lukla i could even go higher, nearly 100% which would be 120% or so. Very impressed. This with 30FPS capping is GREAT for all users without Repro.
Then i turned on the Repro, ok it “wants” to work, but i get too much watery, wobbly effects. Even with 30fps. This is unusable with Repro in the current state.
PC: 5800x, 32GB, 3070Ti, M2
I can report absolutely no more issues on my end switching out of VR whilst still in the cockpit. Kudos on this fix!! Also unrelated to this but wanted to mention I have still gone many hours in SU7 (DX11) without a single CTD. That was certainly not the case with SU6 for me.
And back on topic - you guys have done a good job with Motion Compensation. Yeah it is not perfect but IMHO is certainly better than Steam VR Motion Smoothing.
Keep up the great work!!
Hi can you please help me set it up.Where is XR_APILAYER_NOVENDOR_fov_modifier.dll inside the package?And also when i’m trying to run it as administrator i can find only run with power shell.Any help will be appreciated.
First of all: Massive thanks for your efforts. It is really highly appreciated that you’re trying to help us simmers!
I’m currently struggling with the application (MSFS) “passing no name to OpenXR” (App configuration - Step 1).
The Log file reads:
dllHome is “C:\Program Files\OpenXR-API-Layers”
XR_APILAYER_NOVENDOR_fov_modifier layer is active
Could not load config for “OpenXR Entwicklertools für Windows Mixed Reality”
Could not load config for “OpenXRDeveloperTools”
Using FOV for left 1.000 1.000 1.000 1.000 and right 1.000 1.000 1.000 1.000
When I create a *.cfg named “OpenXRDeveloperTools.cfg” with the proposed values, the log file changes the settings, however, I see no difference within MSFS.
Any ideas?
can you please help me with the first steps?Where is XR_APILAYER_NOVENDOR_fov_modifier.dll inside the package?And also when i’m trying to run it as administrator i can find only run with power shell
You must’ve missed the 1st step that says to download the ZIP file from the releases page, here’s the link to the file: https://github.com/mbucchia/XR_APILAYER_NOVENDOR_fov_modifier/releases/download/preview-2/XR_APILAYER_NOVENDOR_fov_modifier-preview-2.zip.
I’ll update the instructions later to be more clear.
UWP apps have a tendency to have different %LocalAppData%. My guess is that you are looking at the wrong log file, and you’re getting logs from the OpenXR Developer Tools and not MSFS2020. Maybe do a search in your %LocalAppData% for all files named XR_APILAYER_NOVENDOR_fov_modifier.log to locate the correct one. For MSFS2020 it should be at the root of your local app data, ie something like C:\Users\<username>\AppData\Local, and not under Packages\<something package ID>.
Nonetheless, for MSFS2020 downloaded from the Microsoft Store, the app name should be FS2020 hence the file name should be FS2020.cfg as the example shows in the readme.
I had the same problem. This is how I solved it:
-
Open the PowerShell as Administrator and activate script execution with the command
Set-ExecutionPolicy Bypass. -
Install the
Install-Layerscript. -
Make sure to deactivate this bypass after having the script installed via
Set-ExecutionPolicy Restricted.
Hope this helps.
1 Like
I’ve uploaded a new release that includes scripts that can just be run with “Run with PowerShell” and will do the Administrator elevation automatically.
PS: I am having some GitHub issues here, so the release might not show up immediately. Look for a “Preview release #2” that has a new ZIP file.
1 Like
You guessed right! I found the correct logfile which had the app listed as FS2020.
I have a quite powerful rig (11900K, 3090, 32GB CL16 3600, PCIe 4.0 NVMe) and was able to reach stable 30FPS with 100% OXR and 80% render scale within MSFS before. All settings on ultra/max. However, 100% render scale is my personal goal.
This is what I figured out so far:
The settings suggested by @HyperJet2018 had no influence on my visually perceived FOV but unfortunately also no influence on FPS. To find out if the idea works at all, I lowered the percentage down to .5 which gave a plus of around 6-8 FPS. Further down to 0.3 did not show further increase in FPS. Of course .5 is not really an option.
Maybe this helps for further developing the idea. I’ll keep the “new” settings as they may give my GPU some rest from time to time and I could not find any degradation of the quality.
Thanks for all your efforts and ideas!
You are right, i also did not gain any FPS. But look at the visuals!!! They get much sharper!! So if you want to gain FPS, just lower your in-Game Render Scale from 80% down to 60% and there is your gain.
Or in other words: you reached your goal of 100% OXR and 100% inGame with your current setting of 100% OXR and 80% inGame. Please try and compare the visuals - and let us know.