dburne

It would be nice if MT Open Beta supported the Varjo Aero natively - at least in the sense of it producing two images by default. Granted there are some now discovering the ability to use eye tracking with dynamic foveated rendering when quad is enabled, but I think that should be an option rather than going to quad by default. Having to keep up with and use the wrapper from Mbucchia just to run standard Open XR with the Aero is a bit too much friction imho. I love that we have that wrapper as I use it with every launch but would be nice not to have to.

The Toolkit gives you more access to some post processing features that can improve one's experience. I would say as far as performance the main gain there is by switching to using the Open XR runtime, even if it is Steam's version. Everyone though can have difference experiences. Suggest you have a good read about Open XR Toolkit here.

Everyone is a little different. FOV to me means much less than say image clarity and stability. I will take the latter any day over FOV. And I would want a finished product, not one that is continuously being developed on the fly to reach what they stated it would do based on the last say 100 units shipped out. Pimax Modus Operandi. Pimax left a very bad taste in my mouth from the get go and I guess I just can't overcome that. But I am happy they are there and offering high end PC-VR to the consumers, certainly helps the VR cause in the long run. And that is a good thing.

This type of stuff is why VR in it's current form will never reach mass adoption.

Thanks. I guess I just wanted a way to display the actual resolution in the headset when it was set to default. Apparently no way to do this.

Personal thing for me but - I won't touch Pimax with a 10ft pole. I despise the way they market and do business. Been having a blast with my Aero every day now for well over a year. In fact Aero and Crystal were announced the same week. Varjo delivered - Pimax - well they are still working on it lol.

Ok thanks, yeah I am currently only doing DCS.

Thanks but again that does me no good, apparently I am not stating this in a way that is clear enough to grasp. I would like the Open XR Resolution setting to reflect what my default would be for the setting in Varjo Base. Once I have entered a value in Open XR Toolkit for resolution it keeps that resolution. So no matter what I select in Varjo Base when I select to override resolution it is automatically going to input the last value I entered for it. I see no way to get it back to default resolution say as a starting point.

Thanks for the info. I guess for what I am asking though there is not an easy way to tell what my default resolution if set to very high would be as it has been changed in OXRTK already and it stays where it was last set. I do use the resolution override to change my resolution setting. But say I have done this with the high setting and I then change Varjo Base to very high setting. But I go back in resolution setting in OXRTK and it still shows the same I had to set to when it was on High setting.

I am afraid I was not clear enough in my request. This has nothing to do with DFR or that new stuff being worked on currently. Just the base resolution. The resolution I set in Open XR Developer Tools stays where I have it set to and I don't see a default setting. So say I want to know the resolution of Very High setting in Varjo Base with Varjo's Open XR, any way to tell what that is?

Does the Open XR Toolkit have a default VR resolution for the Aero? Like for each Aero base setting, say hi or very high, is there a default resolution for each Varjo setting in Open XR? I do not seem to be able to find one if there is, it will always display the last resolution I have set. Just wondering what Open XR considers Varjo default resolution to be in high or very high base setting.

Ok so I know I am not fully awake yet - but why you say it does not happen in cockpit when your screen shot shows it inside the cockpit?

I will probably wait a while and let that part of the cake bake a little longer. Don't want to disrupt my newfound performance using the MT version and great display using Open XR along with the Toolkit.

I was never that big on the Open XR combined with Open XR Toolkit that so many seemed to be happy with. After DCS introduced the new MT with this last update, I set it up and gave it another whirl and am very pleased with it. I have an Aero and am not that fond of their Motion Reprojection implementation so I am running without that now anyway. But yeah I get where you are coming from.

Well did some comparisons today on my end on running either with Varjo's Open XR or with Steam's Open XR. They are pretty close to each other, I think Steam VR's Open XR has little less in performance but is maybe little more consistent in frametimes. I see more of the occasional frametime spikes in Varjo's Open XR than in Steam's. Not enough to really sway me one over the other, but since performance seems little better in Varjo Open XR think I will leave it be for now with that. Both though with the new MT from DCS are quite good.

I am tempted and probably only thing giving me pause is it is not carrier based at least that I can tell. I do love me some good Super Carrier action. I am sure I will grab it though, long missions do not bother me so much and I love flying Hornet campaigns. Lol I swear sometimes I think the information flow changes on a daily basis on some of this stuff. Previously (very recently) it was the Aero does not, the VR-3 does. It is no wonder VR will never come close to mass adoption.

Ok thanks much, I may have a peek at it here soon.

Question for ya in regards to running Open XR using Steam VR along with the Open XR Toolkit, which is used to set resolution or are both effective at that? Just wondering.

But of course, ED says it is Varjo, Varjo says it is Ed. I just want the dang thing to work like it is supposed to so I reckon it probably never will at this point. I like running in Varjo's Open XR though now with the Open XR Toolkit so I will stick with using the wrapper as long as it works. AFAIK Aero does not support 4 views, only 2. Someone needs to fix this. Varjo VR3 supports 4 views, not Aero.

Currently very happy with using Open XR along with Open XR Toolkit with my Aero. And my performance practically skyrocketed after the MT update. Now if only ED could address and fix the native Open XR with the Aero. Currently requires the wrapper kindly provided by Mbucchia to get it to run properly. So it requires a Mod to get it to work with DCS properly.

So I guess no fix then for Varjo headsets being able to run natively with Open XR. Not surprised. Will just have to keep using Mbucchia's wrapper in order to get it to run correctly.

Shouldn't have to, no. Only if you update VB for example. Ok great, that is kind of what I was thinking also. Ideally the next DCS update would have a fix for this but I am not very hopefull on that one.

Ok so probably a stupid question. After each DCS update will I still need to go in and do anything for the Open XR Wrapper to still work properly with DCS? I ask as I know the wrapper is put into the Varjo Base files rather than the DCS files?

Oh pleeaase let there be a fix for native Varjo Aero in Open XR with DCS.