Varjo Aero: Общее руководство для новых владельцев

[Baldrick33]

Thanks for all the replies re DFR.

I don’t want to derail this excellent thread but what makes the Aero work with DFR & DCS whilst the Meta Quest Pro doesn’t?

[dburne]

12 minutes ago, Baldrick33 said:

Thanks for all the replies re DFR.

I don’t want to derail this excellent thread but what makes the Aero work with DFR & DCS whilst the Meta Quest Pro doesn’t?

 

@mbucchia magic dust...

He would be best to answer this as he implemented it , if I had to guess I would say the Varjo Aero having quad view capability has something to do with it.

[mrno]

nullHi - I setup the system as recommended for my Aero.

 

Running MT with only --force_varjo_VR and Dynamic FOV rendering.  I get this image within an image issue.  Any guidance and help would be appreciated.

[mbucchia]

2 hours ago, Baldrick33 said:

I don’t want to derail this excellent thread but what makes the Aero work with DFR & DCS whilst the Meta Quest Pro doesn’t?

Like Don said this is (partially) about the "quad views" support (being able to render in 2 passes with 2 different resolutions and a moving viewport) being a Varjo feature (the "official" name of it is "XR_VARJO_quad_views"). This is a completely different technique than the one used in OpenXR Toolkit or VR perfkit, and it cannot just be "forced in" like OpenXR Toolkit FFR/DFR, it requires some fundations in the game engine which ED built.

However they seem to not have finished it:

a) there is a major bug in their frame management with MT (reported to them)

b) they never actually enabled the DFR capability aka "XR_VARJO_foveated_rendering".

This is why you need a separate tool, my "OpenXR-Varjo-Foveated" to fix a) and add the missing bits for b).

Regarding other headsets support, this is in theory achievable: the OpenXR extensions mentioned above, while published by Varjo, are free of any intellectual property and can be implemented on any OpenXR platform.

For example, I've added support for them into my Pimax OpenXR runtime, and they work today on older Pimax products with the add-on eye tracking module, and they _should_ work on Pimax Crystal once they release firmware with the eye tracker support.

For other headsets like Quest Pro, they are some significant barriers that Meta is putting in the way (of _any developer really_):

- Their eye tracking support is targeted for Avatars only (that thing that none of us gamers care about). Remember, it's the Quest "Pro" as in "Enterprise". It requires additional support efforts to be usable for something like foveated rendering.

- Their eye tracker functionality is currently gated by "developer mode", a mode of the device that is unfriendly to end-users, and activating such mode has many bugs (this is why even today with OpenXR Toolkit support for DFR in some games, many users still cannot use it due to these developer mode issues).

- Their compositor doesn't support a feature called "FOV mutable", which is critical in writing quad views emulation code, specifically to implement a smaller moving view port for the foveated region. Writing code to simulate that feature is complex.

- The Quest Pro isn't that high-end and high resolution. In the end, because the resolution is only a fraction of what it is on Varjo, then it means the gains will also only be a fraction of the gains on Varjo.

In the end the decision is a no brainer: unfriendly usage, need of significant code to fill the gaps left by Meta, and estimated too small gains make it not worth my time, for a device that is clearly not intended for gaming usage in the first place.

For comparison: I considered adding support for G2 Omnicept, because at least the eye tracker works out of the box and WMR supports FOV mutable. However the lower pixel count and low adoption of this device also make it not worth my time.

A comparison worth it: the initial implementation of quad views support in PimaxXR took only 2 days, and it's already showing gains comparable to what we see on Aero (and I dont even have a Pimax device with eye tracker)... my support had built-in equivalent of what my OpenXR-Varjo-Foveated mod does (the thing we asked Varjo on their Discord to offer - aka a checkbox to force use of the eye tracker with quad views even if the app isn't asking for it), so the separate program isn't even needed with Pimax.

I think the Varjo implementation in their runtime will still be more polished than mine in Pimax, simply because it look like they have done some work to optimize it for their optics (something I don't really have the time/skills to do myself).

30 minutes ago, mrno said:

Running MT with only --force_varjo_VR and Dynamic FOV rendering

Don't use force_varjo_VR and just let the game use OpenXR instead.

Edited May 21, 2023 by mbucchia

[Rodeo]

11 hours ago, Slick Twitchy said:

I have the box where the focus is located-as you said noticeable in specific situations (NVG,  staring into the sun etc)- seems like it may be 'some setting' in that others don't have/notice it. 

Which video are you referring to (re: Str][ker video)?

I noticed it a time or two flying in broken clouds with the sun just a certain way as I was banking after launching Mavericks.. not sure if this trick is a resolution but I closed my eyes for a brief nanosecond and resolved the issue. I did it three or four times and each time the box disappeared. Not sure if the issue has to do with the headsets internal calibration but I’ll try it out again next time it happened.

Also here is the video you asked about. It is the install for DFR 

 

[mrno]

1 hour ago, mbucchia said:

 

Don't use force_varjo_VR and just let the game use OpenXR instead.

 

Thanks for the suggestion.  Still getting weird square that follows my gaze and its 2x magnified.  I removed and reinstalled everything still no dice with --force_OpenXR

 

 

[mbucchia]

49 minutes ago, mrno said:

Thanks for the suggestion.  Still getting weird square that follows my gaze and its 2x magnified.  I removed and reinstalled everything still no dice with --force_OpenXR

 

 

Can you try "plain quad views" (aka FFR) by uninstalling OpenXR-Varjo-Foveated? Alternatively you can also try modifying the OpenXR-Varjo-Foveated config file (see instructions on the website/wiki) to set no_eye_tracking=1.

[Baldrick33]

@mbucchia

Thanks for the comprehensive reply, that makes it much clearer.

[mrno]

30 minutes ago, mbucchia said:

Can you try "plain quad views" (aka FFR) by uninstalling OpenXR-Varjo-Foveated? Alternatively you can also try modifying the OpenXR-Varjo-Foveated config file (see instructions on the website/wiki) to set no_eye_tracking=1.

Thanks - Using your mbucchia/OpenXR-InstanceExtensionsWrapper fixes it in openxr. 

Issues occur in the following:

Varjo Base - Eye tracking off - in Openxr - nothing installed.  Time to time a large box in the middle of the screen appears and its 2X zoom.

Same thing with Eye Tracking on, but you get the lovely effect that it follows your gaze now.

Either case its not your utility for DFR, it happens with or without it.  Its basically the quad view thing and perhaps it has some quirks.  SteamVR(OepnVR) I dont see the issue, thus its isolated to the QuadView or whatever that its.

Perhaps its my setup so reflashed the firmware with no avail, re-install etc... nothing works.  I have a Varjo Aero and an XR3, it only happens with the XR3.

[Supmua]

3 hours ago, mrno said:

nullHi - I setup the system as recommended for my Aero.

 

Running MT with only --force_varjo_VR and Dynamic FOV rendering.  I get this image within an image issue.  Any guidance and help would be appreciated.

For MT DFR there is no need to use any command line, just make sure the VR option is selected in DCS setting. You’ll want to use Varjo OpenXR which is the default MT output, the very first post has precise instructions for this and more. Using force_varjo_VR will enforce Varjo OpenVR which is not desirable in this case. 
 

OpenVR API doesn’t scale well with multi-threading so it should be avoided at all cost and always use OpenXR (either Varjo or Steam) with DCS MT.  Also note that Steam OpenXR doesn’t support DFR/quad view, and to make things worse for new comers DCS single threaded still outputs OpenVR rather than OpenXR as default. 

Edited May 21, 2023 by Supmua

[Rodeo]

Quick question y’all… love my Aero and everything has been running so smooth and clear; absolute amazing compared to the 8kx IMHO… anyways I fly the A10CII predominately and my only complaint in a “default” state (I haven’t messed with any in-game VR settings) is that my left and right instrument panels seems  disproportionately smaller scale. I’m amazed how clearly I can read the labels on the CDU buttons and all but CDU, Radios, and panels seem to small compared to front instruments and HUD. Am I missing something like messing with PD setting or such? Basically seems like the the cockpit is very long and narrow if that makes sense. 

Sorry about the rambling

[Willdass]

@Rodeo Hard to say without seeing your settings. But it seems like a DCS setting issue and not a Aero issue. 
Maybe your FOV setting in DCS? Does resetting your DCS settings not work?

[Rodeo]

@Willdass Here are my settings.. thanks for the help.

 

Edited May 24, 2023 by Rodeo

[dburne]

52 minutes ago, Rodeo said:

@Willdass Here are my settings.. thanks for the help.

 

 

 

Are you running DFR with eye tracking for the Aero with DCS? If so you should disable the MSAA mask size in DCS.

If not - you should give it a try.

Edited May 24, 2023 by dburne

[Rodeo]

34 minutes ago, dburne said:

 

Are you running DFR with eye tracking for the Aero with DCS? If so you should disable the MSAA mask size in DCS.

If not - you should give it a try.

 

I am running DFR.. thanks for the tip.

 

[Willdass]

@Rodeo Thx for screenshots, does not look like you have anything crazy in your settings that should cause this... Maaaaybe the external FOV setting bugs out with DFR and applies in the cockpit? IDK. You can also try the default VR preset.

[Supmua]

FYI, make sure to update mbucchia's Foveated mod to the latest version for full compatibility with some non-DCS games.  Took me awhile to figure out it was the older version that was causing crashes with the new Star Trek: Resurgence game.  The new version is trouble-free so far.

[Rodeo]

37 minutes ago, Supmua said:

FYI, make sure to update mbucchia's Foveated mod to the latest version for full compatibility with some non-DCS games.  Took me awhile to figure out it was the older version that was causing crashes with the new Star Trek: Resurgence game.  The new version is trouble-free so far.

Thanks for taking the time and interest in my issue; I think I have the latest version.  I just upgraded from the Pimax 8kx to Aero two weeks ago.  I think that was the latest DFR version.

Thanks again

[Rodeo]

57 minutes ago, Willdass said:

@Rodeo Thx for screenshots, does not look like you have anything crazy in your settings that should cause this... Maaaaybe the external FOV setting bugs out with DFR and applies in the cockpit? IDK. You can also try the default VR preset.

Thanks @Willdass  This is such a minor problem given the huge gains I have gotten from switching.  I'll disable the MSAA as suggested by @dburne and see what happens.

[dburne]

1 hour ago, Rodeo said:

Thanks @Willdass  This is such a minor problem given the huge gains I have gotten from switching.  I'll disable the MSAA as suggested by @dburne and see what happens.

 

Not disable MSAA itself, just the mask size feature of it - un-enable that in the VR settings. Your DFR will take care of the rest.  I actually increased my MSAA ;from 2x to 4x after implementing the DFR feature.

[Rodeo]

34 minutes ago, dburne said:

 

Not disable MSAA itself, just the mask size feature of it - un-enable that in the VR settings. Your DFR will take care of the rest.  I actually increased my MSAA ;from 2x to 4x after implementing the DFR feature.

Gotcha thanks… takes a village to raise me 

[Rodeo]

So I feel a little silly and maybe there is a setting or two I'm missing but I think I found part of my problem.. and to not admit my own failures I will blame bad habits caused by Pimax .

I think part of my problem is that with the 8kx the FOV is that little bit wider but the resolution is way behind the Aero. Flying the 8kx the past year (on my old Dell with 3090) the resolution was so bad/poor that I would have to adjust the cockpit camera way forward to help with MFD resolutions. So much so I have the camera view adjustments bound to my HOTAS. A year of doing that certain bad habits were formed constantly adjusting so I could at least utilize the MFDs. Now with the Aero’s amazing resolution and DFR I only make micro adjustments to fit my personal preference with the cockpit camera.
 

What I DID NOT realize or think of was the vertical seat adjustment in the A10. The combination of the 8kx FOV and probably my calibration with the headset I never messed with the verticals seat adjustment because I was making the cockpit cam adjustments. Now with the Aero I am realizing that the default seat position is way to high for my headset. Once I lower my seat then adjust the cockpit camera the left and right side panels are much easier to look at and slightly larger. Again I am sure there might be a little tweak somewhere in system settings but this solution was a big help with actually seeing the radio and CDU (not resolution but actually being able to look down naturally and they are close to were they suppose to be). 
 

Thanks again everyone

Edited May 26, 2023 by Rodeo

[chev255]

On 5/24/2023 at 10:29 PM, Rodeo said:

 

 

@Willdass Here are my settings.. thanks for the help.

 

 

Change resolution of cockpit displays to 1024 and you will see a big difference

[Rodeo]

2 hours ago, chev255 said:

Change resolution of cockpit displays to 1024 and you will see a big difference

Already did once I looked at my own screenshot.. yeah moment. Although the Aero rocked it at that low setting especially coming from the 8kx (I restored all my setting to default when I switched to Aero BTW)

[Tomcat31]

Hi, I have a similar problem with DFR, I think.  I have 2 squares which appear in flight (who follow my gaze) and which disappear after a few seconds. I don't really know what i can do to resolve this :-/.

thanks.