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

[Gordy]

 

[Gordy]

The native without-steamvr support isn't working with my aero, though... I can see on my monitor that I get into the main menu/lobby, but my aero is just black.   For both openxr and openvr. 

openvr with steamvr works, as before.

openxr with the replacement .dll works, as before. 

interested to hear if anyone else is having success with the native openxr support

[zildac]

In my testing, if you are using the native OXR now supported by DCS with a Varjo AERO you will have the double cursor/offset issue, and you can't use OXRTK. ED are enumerating the AERO incorrectly as having four screens, which breaks the cursor and OXRTK.

Edited January 26, 2023 by zildac

[zildac]

6 minutes ago, Gordy said:

The native without-steamvr support isn't working with my aero, though... I can see on my monitor that I get into the main menu/lobby, but my aero is just black.   For both openxr and openvr. 

openvr with steamvr works, as before.

openxr with the replacement .dll works, as before. 

interested to hear if anyone else is having success with the native openxr support

Do you have Open XR Toolkit enabled? If so, it will not work with native OXR in DCS..ED issue. I had the same thing 2D mirror is fine, HMD is blank. Disable OXRTK and it will work albeit with double cursor as in my previous post.

Edited January 26, 2023 by zildac

[Gordy]

ah, yes, thank you.   With OXRTK disabled, the native openxr works, but with the double cursor, as you say.  

openxr explorer shows both the stereo and quad view configurations advertised, so I guess that's what DCS is responding to... <shrug>.

Maybe it's picking the first view, in alphabetical order, and we're just unlucky that it's the wrong one:

XR_VIEW_CONFIGURATION_TYPE_PRIMARY_QUAD_VARJO
XR_VIEW_CONFIGURATION_TYPE_PRIMARY_STEREO

[Supmua]

All we need is a way to manually disable quad rendering mode, don't really need it.

[zildac]

1 hour ago, Gordy said:

ah, yes, thank you.   With OXRTK disabled, the native openxr works, but with the double cursor, as you say.  

openxr explorer shows both the stereo and quad view configurations advertised, so I guess that's what DCS is responding to... <shrug>.

Maybe it's picking the first view, in alphabetical order, and we're just unlucky that it's the wrong one:

XR_VIEW_CONFIGURATION_TYPE_PRIMARY_QUAD_VARJO
XR_VIEW_CONFIGURATION_TYPE_PRIMARY_STEREO

It appears to be exactly that

10 minutes ago, Supmua said:

All we need is a way to manually disable quad rendering mode, don't really need it.

Exactly as @mbucchiaasked. Cmd line switch or similar

[Supmua]

What’s bothering me is that no other VR games have this specific quad rendering issue with the Aero (OpenVR or OpenXR).

[mbucchia]

5 hours ago, Gordy said:

ah, yes, thank you.   With OXRTK disabled, the native openxr works, but with the double cursor, as you say.  

openxr explorer shows both the stereo and quad view configurations advertised, so I guess that's what DCS is responding to... <shrug>.

Maybe it's picking the first view, in alphabetical order, and we're just unlucky that it's the wrong one:

XR_VIEW_CONFIGURATION_TYPE_PRIMARY_QUAD_VARJO
XR_VIEW_CONFIGURATION_TYPE_PRIMARY_STEREO

No, they appear to intentionally force XR_VIEW_CONFIGURATION_TYPE_PRIMARY_QUAD_VARJO as long as they detect Varjo via instance capability (XR_VARJO_quad_views), and even if the runtime doesn't advertise it (I updated OpenXR Toolkit to force not advertising it).

See my comment here about proper enumeration logic, which they do not appear to follow:

 

Edited January 26, 2023 by mbucchia

[Supmua]

Okay I did some testing.  The best way for me to run OpenXR right now is via SteamVR.  So what you do is enable Steam OpenXR in SteamVR Settings/Developer/SteamVR as OpenXR Runtime.  This will disable Varjo's OpenXR.  Then run DCS normally (not via command line).  This way OXRTK works, fpsVR also works since everything runs via Steam's framework, and no Quad rendering with good performance as before.  The bottom line is, avoid using Varjo's OpenXR with DCS right now and use Steam's OpenXR instead.

Edited January 26, 2023 by Supmua

[zildac]

Okay I did some testing.  The best way for me to run OpenXR right now is via SteamVR.  So what you do is enable Steam OpenXR in SteamVR Settings/Developer/SteamVR as OpenXR Runtime.  This will disable Varjo's OpenXR.  Then run DCS normally (not via command line).  This way OXRTK works, fpsVR also works since everything runs via Steam's framework, and no Quad rendering with good performance as before.  The bottom line is, avoid using Varjo's OpenXR with DCS right now and use Steam's OpenXR instead.

Isn't it juat easier and more efficient to use OpenComposite?

[Supmua]

34 minutes ago, zildac said:

37 minutes ago, Supmua said:

Okay I did some testing.  The best way for me to run OpenXR right now is via SteamVR.  So what you do is enable Steam OpenXR in SteamVR Settings/Developer/SteamVR as OpenXR Runtime.  This will disable Varjo's OpenXR.  Then run DCS normally (not via command line).  This way OXRTK works, fpsVR also works since everything runs via Steam's framework, and no Quad rendering with good performance as before.  The bottom line is, avoid using Varjo's OpenXR with DCS right now and use Steam's OpenXR instead.

Isn't it juat easier and more efficient to use OpenComposite?

This isn't a hack like OpenComposite so I think it will be at least as efficient if not more as this is pretty much OpenXR output from DCS directly to SteamVR (skipping the OpenComposite to OpenXR translation stage) and it's working as intended and I'm still getting 90 fps in free flights with current DCS settings.  OXTRK works, I'm using it right now with all kinds of image postprocessing such as contrast/exposure/color balance changes (Overriding resolution doesn't work but you can change resolution via SteamVR, CPU frametime is wrong but it's been like that for OXRTK).  I also have fpsVR working in this mode also.

 

This actually makes it simple for new Varjo Aero owners to run DCS.  All they have to do is set SteamVR as default for OpenXR then run DCS normally, as this will disable Varjo's OpenXR.  No command lines, no extra steps.

Edited January 26, 2023 by Supmua

[dburne]

39 minutes ago, Supmua said:

Okay I did some testing.  The best way for me to run OpenXR right now is via SteamVR.  So what you do is enable Steam OpenXR in SteamVR Settings/Developer/SteamVR as OpenXR Runtime.  This will disable Varjo's OpenXR.  Then run DCS normally (not via command line).  This way OXRTK works, fpsVR also works since everything runs via Steam's framework, and no Quad rendering with good performance as before.  The bottom line is, avoid using Varjo's OpenXR with DCS right now and use Steam's OpenXR instead.

 

 

Interesting may have a look at this - can you expand on that part I highlighted a little?  I think I am using a shortcut wtih the --force_steam_vr nomenclature set for it. Granted I have been happy with my performance in Steam VR but now that DCS has native Open XR I would like to check it out, without all the other toolkit stuff. I do not need or want access to all those addtional settings tweaks. I prefer to just fly.

Edited January 26, 2023 by dburne

[Supmua]

16 minutes ago, dburne said:

 

Interesting may have a look at this - can you expand on that part I highlighted a little?  I think I am using a shortcut wtih the --force_steam_vr nomenclature set for it. Granted I have been happy with my performance in Steam VR but now that DCS has native Open XR I would like to check it out, without all the other toolkit stuff.

No need for that now Don.

1. Run SteamVR GUI and go to settings/Developer section and make Steam the default platform for OpenXR.  (You might also be able to do this by just toggling Varjo OpenXR to OFF in VB but I haven't confirmed this).

2. Run DCS without command line, straight from Windows Menu or Start menu, etc. like you'd normally do with other games.

3. Change rendering resolution in SteamVR, as needed.

4. Use OXRTK if you want for postprocessing, frame manipulation, etc.  Some options don't work correctly (resolution change) and CPU frametime report is wrong, at present.

Edit: right now if you use resolution override in OXTRK it will cause the OXRTK pop-up window to disappear after restarting DCS.  To bring it back enable Safemode in OXRTK via companion app then reset the settings with CTRL+F1+F2+F3, and restart DCS again.

Edited January 26, 2023 by Supmua

[dburne]

11 minutes ago, Supmua said:

No need for that now Don.

1. Run SteamVR GUI and go to settings/Developer section and make Steam the default platform for OpenXR.  (You might also be able to do this by just toggling Varjo OpenXR to OFF in VB but I haven't confirmed this).

2. Run DCS without command line, straight from Windows Menu or Start menu, etc. like you'd normally do with other games.

3. Change rendering resolution in SteamVR, as needed.

4. Use OXRTK if you want for postprocessing, frame manipulation, etc.  Some options don't work correctly (resolution change) and CPU frametime report is wrong, at present.

Edit: right now if you use resolution override in OXTRK it will cause the menu to disappear after restarting DCS.  To bring it back enable Safemode in OXRTK via companion app then reset the settings with CTRL+F1+F2+F3, and restart DCS again.

 

 

Ok thanks I will give it a try tomorrow sans Toolkit though, I just want to compare how it does using Open XR runtime. Nice to know I can still use my resolution settings I have in Steam VR.

[Supmua]

29 minutes ago, dburne said:

 

Ok thanks I will give it a try tomorrow sans Toolkit though, I just want to compare how it does using Open XR runtime. Nice to know I can still use my resolution settings I have in Steam VR.

Yeah, no hacks involved, no messing around with DSC installation or editing DCS.exe shortcut.  All you have to do is use Steam's OpenXR with DCS instead of Varjo's and that's it.  I don't see any performance loss at all (I also don't see performance loss running MSFS via Steam's OpenXR).

This is basically the same issue that we've had with Varjo's OpenVR and DCS, just redirect the output to SteamVR and it works better without Quad rendering issue.

EDIT: so far I'm seeing slightly better CPU frametime with the old Steam's OpenVR (via command line) vs this OpenXR via Steam by around 1.0ms.  GPU frametimes are pretty much the same.  So the old method with Steam's OpenVR might yield slightly better performance in CPU limited situations such as on MP servers (most of the time I'm GPU limited in SP missions).

Edited January 27, 2023 by Supmua

[zildac]

10 hours ago, Supmua said:

This isn't a hack like OpenComposite so I think it will be at least as efficient if not more as this is pretty much OpenXR output from DCS directly to SteamVR (skipping the OpenComposite to OpenXR translation stage) and it's working as intended and I'm still getting 90 fps in free flights with current DCS settings.  OXTRK works, I'm using it right now with all kinds of image postprocessing such as contrast/exposure/color balance changes (Overriding resolution doesn't work but you can change resolution via SteamVR, CPU frametime is wrong but it's been like that for OXRTK).  I also have fpsVR working in this mode also.

 

This actually makes it simple for new Varjo Aero owners to run DCS.  All they have to do is set SteamVR as default for OpenXR then run DCS normally, as this will disable Varjo's OpenXR.  No command lines, no extra steps.

 

No, I understand it's not a "hack", but I'm assuming you lose the ability to use VB to cap at 45FPS for example via Vsync and set PPD?. And Steam VR just always felt clunky to me. I guess I can give it a quick try and see.

Edited January 27, 2023 by zildac

[dburne]

5 hours ago, zildac said:

No, I understand it's not a "hack", but I'm assuming you lose the ability to use VB to cap at 45FPS for example via Vsync and set PPD?. And Steam VR just always felt clunky to me. I guess I can give it a quick try and see.

 

 

I hope not as I much prefer flying with vsync on in VB and locked at 45 fps.

[zildac]

I've just tried setting SteamVR as the default OpenXR "handler" and I get nothing display wise in my Aero HMD. I'll stick with OC for the time being I think.

[Supmua]

The newest update changes everything back to square one.  Which means you get quad screen no matter what with default launch, so we will need to run DCS via command line again to bypass this.

[dburne]

Not sure if today's hotfix changed any of the above to run in Open XR or not?

[Supmua]

Just now, dburne said:

Not sure if today's hotfix changed any of the above to run in Open XR or not?

yep it does, back to what it was before meaning default quad views for the Aero.

[dburne]

Just now, Supmua said:

yep it does, back to what it was before meaning default quad views for the Aero.

 

Lol figures, well I will just stick with my tried and true Steam VR for now.

Thanks,

[Supmua]

Just now, dburne said:

 

Lol figures, well I will just stick with my tried and true Steam VR for now.

Thanks,

Yeah, the OpenXR Steam incurs 1ms CPU frametime increase (vs OpenVR Steam) anyway.

[motoadve]

Recent Hotfix lowered my performance.

Varjo Aero, 4090.

No mods, no tool kits.

Should I run Steam VR  for better performance?
When I start DCS it never starts on its own, but I can start it by double clicking the Steam VR icon.
Also what is best to set Steam VR to?  OpenXR runtime to use SteamVR.? or SteamVR as OpenXR runtime?

What is more compatible with DCS?

 

Also what to set on the Varjo?