Well in 1.1.2 we moved the rendering of menu to a new technique, this was needed for 2 things:
Fix the menu position and rendering for certain headsets (like Pimax and HTC)
Fix some issues with OpenComposite (non Flight Sim 2020)
We need this feature going forward, we cannot start having multiple branches for these various use cases.
This new rendering broke something in WMR as reported, and we fixed in (WMR team for the next release). But if it also broke somethings for Varjo, there is nothing I can do about that.
Basically HAGS seems to be extremely sensitive to any misuse of Direct3D (called D3D Validation Errors). But unfortunately these can still be common among apps, because many times these validation errors do not have any visible effect and developers just miss them. But HAGS seems to be very affected by them.
Have you confirmed the following:
No HAGS does fix the issue for you?
Do you still have the issue when the OpenXR Toolkit overlay is disabled (this means use another FPS overlay)?
After some more testing, I have to correct a bit myself: there is nothing wrong with 1.1.3 and the Aero.
However 1.1.3 gives 2-3 fps less than 1.1.0: it is not much but as the aero does not have motion reprojection yet, it looks more stuttery. The performance in 1.1.3 is the same with HAGS on or off.
Anyway, Varjo is bound to implement reprojection at some point and with DLSS, I do not think the small fps difference will be noticable in the future. Thanks anyway for looking at my comment and keep up the good work !
Thanks. Any chance you can try these measurements with another FPS counter (ie turn off ALL OpenXR Toolkit overlays)? The only thing that could explain a difference from 1.1.0 to 1.1.2 is the new menu/overlay rendering. So I wonder if showing the FPS itself is what would cause the 2-3 FPS drop. This would be an interesting data point.
So … I have been playing around with the OpenXR settings with some success. However, I’m still rather confused as to the various resolution settings.
I’m using an hp reverb g2 on a sadly underpowered Nvidia RTX 2060 (which supposedly only runs the G2 at half resolution.
So … what is the relationship between the WMR video setting(best performance vs best resolution), the SteamVR res/per eye resolution, the OpenXR resolution (in the vr menu) and the game’s resolution (in Settings)
Which one is the determining factor or is it a mix? I had been setting the SteamVR res to 1/2 the recommended value (due to the 2060) - this was resulting in an fps around 15 … not ideal as the graphics are ■■■■■■. I have been experimenting with setting the SteamVR even higher that the recommended 100% without much degradation in FPS.
@mbucchia Hello, I have a G2, and I know that it is no a Toolkit related surely but WMR related and its SpeechRuntime process, and if these constant warnings each 10min or so in event viewer only when WMR is on, could it be a font of bugs WMR-PC freezes memory errors etc.?
I had similar issue with my G2 during many months. I had to disable USB hub and ports related to audio from the G2 to be able to use it. I tries many things like changing USB port, new USB PCI card with 2 amps capabilities, nothing better. Finally the G2 cable was the culprit. I got the new V2 cable and everything is fine since.
Sorry, I haven’t played around with VA yet. I’ve been flying the Fenix which has superb sun visors so actually haven’t needed the toolkit sunglasses for a while. I’ll take a look now though, should be fairly simple but I’ve been wrong before. Will let you know and share a VA profile if it works as planned.
I whipped this profile together quickly but try it out and see how you get on. The profile assumes a default install location for the openxr companion (C:\Program Files\OpenXR-Toolkit). If you have something else, you need to edit the ‘Run application’ steps for each command.
the profile expects you to say [switch;change;] sunglasses [to;] [light;dark;trunite;off]
so. eg. “change sunglasses to light”, “sunglasses light” etc.
Great interview and nice “meeting” you guys! Although I’m not a software programmer I really learned a lot about the processes, and the advantages and some of the disadvantages the new software technology coming about present. The higher levels of understanding of what DLSS and FSR2.0 actually do for “our😀” simulator was extremely understandable and enlightening. The same for your explanations of DX11 and DX12.
Thanks for this interview and again all you have done for our VR experience!
