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

[Supmua]

1 hour ago, motoadve said:

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? 

No idea on the current performance of each VR mode. I won’t get to do some more testing until weekend. At least now OpenXR is officially supported so you no longer need the Opencomposite wrapper. The good news is that the old methods should still work.  The bad news is that we still have to figure out how to get around to make things work better, especially with the Aero. 

Edited January 27, 2023 by Supmua

[Supmua]

May be some of you guys who have free time can test the different OpenXR modes and see if there's any performance difference.

Route 1:  --force_steam_VR > Opencomposite OpenXR (dll installation) > Varjo OpenXR (toggle OpenXR switch ON in VB)

Route 2: --force_OpenXR > Steam OpenXR (Toggle OpenXR switch OFF in VB)

Route 3: --force_OpenXR > Varjo OpenXR (OpenXR switch ON in VB).  Quad rendering with this one so expect bad performance.

Edited January 27, 2023 by Supmua

[Jack Knife]

Hi,
I normally don’t write on these sort of forums as brighter and better informed individuals have experienced and fixed many of the issues that I have encountered. However, I don’t seen to see an answer to a problem that I have come across since a purchased my Areo a few months ago.

I have a bit of a dilemma, if I run DCS directly from Windows I get the two pointer issue, so, to resolve this I can run it through SteamVR and the problem goes away. But if I do this, I find that my HMD now points down at my feet so the only way to fix this is to crank my head up and look at the bottom of my screen.
Has anyone else experienced this issue, and more importantly, is there a fix?
 

[zildac]

Hi,
I normally don’t write on these sort of forums as brighter and better informed individuals have experienced and fixed many of the issues that I have encountered. However, I don’t seen to see an answer to a problem that I have come across since a purchased my Areo a few months ago.

I have a bit of a dilemma, if I run DCS directly from Windows I get the two pointer issue, so, to resolve this I can run it through SteamVR and the problem goes away. But if I do this, I find that my HMD now points down at my feet so the only way to fix this is to crank my head up and look at the bottom of my screen.
Has anyone else experienced this issue, and more importantly, is there a fix?
 

See here: https://r.tapatalk.com/shareLink/topic?url=https://forum.dcs.world/topic/318268-varjo-aero-dcs-native-oxr-oxrtk-and-offset-cockpit-cursor-issues-fixed/&share_tid=318268&share_fid=74365&share_type=t&link_source=app

[Toumal]

The VR changes broke the game for me completely.

I use a Varjo headset and I have to run in OpenXR, I cannot use OpenVR because motion compensation simply does not work correctly. In OpenXR everything worked fine.

Now the menu works fine in OpenXR but loading into a mission doesn't complete, ever. My logfile is getting filled with the following errors:

2023-01-28 16:29:21.082 ERROR   VISUALIZER (Main): xrEndFrame failed with error: XR_ERROR_SWAPCHAIN_RECT_INVALID
2023-01-28 16:29:21.093 ERROR   VISUALIZER (Main): xrEndFrame failed with error: XR_ERROR_HANDLE_INVALID
2023-01-28 16:29:21.715 WARNING LOG (8548): 55 duplicate message(s) skipped.

I tried running without any parameter, I tried to force OpenXR, and I tried the Varjo mode. 

EDIT: Oh and the replacement DLL doesn't work for me anymore either, the game won't even start up.

EDIT2: Wrapper DLL worked on second attempt. No idea why but there we go.

Any ideas?

Edited January 29, 2023 by Toumal

[zildac]

9 minutes ago, Toumal said:

The VR changes broke the game for me completely.
I use a Varjo headset and I have to run in OpenXR, I cannot use OpenVR because motion compensation simply does not work correctly. In OpenXR everything worked fine.
Now the menu works fine in OpenXR but loading into a mission doesn't complete, ever. My logfile is getting filled with the following errors:

2023-01-28 16:29:21.082 ERROR   VISUALIZER (Main): xrEndFrame failed with error: XR_ERROR_SWAPCHAIN_RECT_INVALID2023-01-28 16:29:21.093 ERROR   VISUALIZER (Main): xrEndFrame failed with error: XR_ERROR_HANDLE_INVALID2023-01-28 16:29:21.715 WARNING LOG (8548): 55 duplicate message(s) skipped.

 

I tried running without any parameter, I tried to force OpenXR, and I tried the Varjo mode. 
EDIT: Oh and the replacement DLL doesn't work for me anymore either, the game won't even start up.
 
Any ideas?
 

It does work, so I'd suggest a ful /slow repair then try the method outlined in this post :

 

 

Edited January 28, 2023 by zildac

[Jack Knife]

2 hours ago, zildac said:

See here: https://r.tapatalk.com/shareLink/topic?url=https://forum.dcs.world/topic/318268-varjo-aero-dcs-native-oxr-oxrtk-and-offset-cockpit-cursor-issues-fixed/&share_tid=318268&share_fid=74365&share_type=t&link_source=app

NICE ONE! Worked for me a treat, much appreciated

 

[zildac]

NICE ONE! Worked for me a treat, much appreciated
 

Excellent

[Supmua]

I've been testing mbucchia's new wrapper that disables the quad screen output and it works really well for the most part.  This pretty much allows us to play DCS in both Varjo's OpenXR or Steam's OpenXR.

 

Varjo's OpenXR:

-Pros: bypassing Steam GUI which may increase performance (haven't really seen it myself).

-Cons: no Steam overlay due to above, fewer options in terms of resolution settings limited to VB setting (only 6 options) or DCS PD setting.  This also exposes some shortcoming with Varjo's current software, why only have 6 fixed resolution settings rather than providing options for customers to dial in any resolution they want like SteamVR or WMR.

 

Steam's OpenXR: (disable Varjo OpenXR in the base, and also enable Steam's OpenXR in settings/Developer menu on SteamVR GUI).

-Pros: fully functioning SteamVR GUI, meaning you can use steam overlay, placing desktop window/browser/pdf file inside VR games, etc.  fpsVR works.  It's also more flexible permitting granular resolution settings via SteamVR.  Varjo's framerate lock via VB also works in this mode.

-Cons: may reduce performance slightly due to additional SteamVR GUI layer (again I haven't seen any significant differences during my testing).

 

OpenXR Tool Kit:

is currently quite finicky with these new OpenXR output options (both Varjo and Steam's).  For one it does not like resolution override, this will cause the pop-up menu to bug out and disappear.  So if you like running your Aero at Max resolution the performance will suffer unless you reduce PD setting in DCS.  I've tried PD 0.7 with VB max resolution (4.1K horizontal pixels) and still got pretty sharp images with fps mostly 90 (F-16C Syria Freeflight map).  I'm also not sure if this wrapper will cause issues with OXRTK in other games.  More testings to do.

 

I also cannot thank mbucchia enough for providing this tool for the community.  This has been an option that I'd wanted to see for months.  There's no reason for us to use quad screen output for regular gamings because the performance hit is too much and the headset's native resolution is already more than good enough.

 

Having said that, all these get around things that we have to do is far from ideal.  We should be able to put on any VR headset, double click DCS icon and be ready to fly.  There's no reason for anybody to have to mess around with creating shortcuts with command line, installing custom dll file, etc.  Imagine if you have to do this with more mainstream games such as MSFS or Call of Duty, well I can't because it would've been hell for customer support--this community is very forgiving unlike the rest of the world.

Edited January 29, 2023 by Supmua

[Supmua]

My new simple OpenXR current settings (using mbucchia's wrapper).  I was getting a lot of crashes/freezes with OXRTK when trying to change various parameters so it's not being used for now.  OpenXR provides superior frame pacing, so even when the fps dips into the 80s the stuttering remains minimal vs 90 fps.  And this API seems to be the future of VR so you guys might as well start using it.  Other older VR titles that got updated (theBlu, etc.) are also switching to OpenXR now.

 

Varjo Aero:

-Resolution Quality: Higher (3608x3092).  At this setting DCS shimmering/aliasing artifacts are really minimal.  Default Varjo resolution gives better fps but moderate shimmering in distant objects, and Highest resolution taxes the performance too much.

-V Sync: disable

 

DCS:

-PD 1.0.

-Preset: VR Preset.  I always use this to standardize things during testings, so use whatever you want based on your need.

-DCS Gamma: 2.0

 

I've been using mostly Steam's OpenXR, just so I can have screen overlay for Windows desktop access without taking off my headset.

Edited January 28, 2023 by Supmua

[dburne]

I have been using Steam VR and running my Aero on default of Hi with vysnc on and locked at 45 fps. I have been getting a good smooth experience with these settings along with some pretty high gfx settings in DCS. Just finished the Spitfire The Big Show campaign with these settings and it was great. 

I may have a look at Open XR in next day or so. It would be nice if ED got the fix out for the Aero sooner rather than later but am sure they will likely wait for the next update so I may give the wrapper a try.

[Supmua]

21 minutes ago, dburne said:

I have been using Steam VR and running my Aero on default of Hi with vysnc on and locked at 45 fps. I have been getting a good smooth experience with these settings along with some pretty high gfx settings in DCS. Just finished the Spitfire The Big Show campaign with these settings and it was great. 

I may have a look at Open XR in next day or so. It would be nice if ED got the fix out for the Aero sooner rather than later but am sure they will likely wait for the next update so I may give the wrapper a try.

Not sure the wrapper is needed for Steam's OpenXR route as it wasn't needed before the hotfix update when OpenXR was the default output.

fpsVR is also compatible with Steam's OpenXR mode, so maybe try that if you don't want to use the wrapper.  It's my goto route anyway because the convenience of accessing desktop overlay and running concurrent SteamVR apps.

[dburne]

2 minutes ago, Supmua said:

Not sure the wrapper is needed for Steam's OpenXR route as it wasn't needed before the hotfix update when OpenXR was the default output.

fpsVR is also compatible with Steam's OpenXR mode, so maybe try that if you don't want to use the wrapper.  It's my goto route anyway because the convenience of accessing desktop overlay and running concurrent SteamVR apps.

 

Ok so then no wrapper and just select Stean VR as OpenXR runtime? Man this stuff can get confusing lol.

[Supmua]

10 minutes ago, dburne said:

 

Ok so then no wrapper and just select Stean VR as OpenXR runtime? Man this stuff can get confusing lol.

Yes, you're already using Steam's OpenVR.  The only diff is that you'll be using Steam's OpenXR instead.  So make the change on Steam so it is the default route for OpenXR intead of Varjo, but also change the DCS.exe command line from --force_steam_VR to --force_OpenXR.  I think Steam disables OpenXR Quad view automatically, it does this with OpenVR and this is why we've been using OpenVR via Steam (instead of default Varjo's OpenVR) with force command line.

Remember Steam can do both OpenVR and OpenXR, you just have to specify it in the setting.

Edited January 29, 2023 by Supmua

[dburne]

11 minutes ago, Supmua said:

Yes, you're already using Steam's OpenVR.  The only diff is that you'll be using Steam's OpenXR instead.  So make the change on Steam so it is the default route for OpenXR intead of Varjo, but also change the DCS.exe command line from --force_steam_VR to --force_OpenXR.  I think Steam disables OpenXR Quad view automatically, it does this with OpenVR and this is why we've been using OpenVR via Steam (instead of default Varjo's OpenVR) with force command line.

 

 

 --force_enable_VR --force_OpenXR

Like this? Or leave the --force_enable_VR out and just have --force_OpenXR?

Edited January 29, 2023 by dburne

[Supmua]

1 minute ago, dburne said:

 

 --force_enable_VR --force_OpenXR

Like this? Or leave the --force_enable_VR out and just have --force_OpenXR?

 

 --force_enable_VR is not needed if you already have VR option on in DCS setting.  Mine is always on but it's really up to you.

Edited January 29, 2023 by Supmua

[dburne]

Just now, Supmua said:

 --force_enable_VR is not needed if you have already VR option on in DCS setting.  Mine is always on but it's really up to you.

Ok good to know then, thanks.

You may have already answered this earlier, by using Steam's Open XR does it still recognize my resolution settings I have in Steam VR?

[Supmua]

26 minutes ago, dburne said:

Ok good to know then, thanks.

You may have already answered this earlier, by using Steam's Open XR does it still recognize my resolution settings I have in Steam VR?

Diff APIs so you might have to double check the rendering res to make sure it’s what you want. I just leave everything at 100%

[Toumal]

16 hours ago, zildac said:

It does work, so I'd suggest a ful /slow repair then try the method outlined in this post :

 

 

 

I actually just tried again and the wrapper worked this time... Not really sure why I got CTD before but anyway, I'll take it

[zildac]

I actually just tried again and the wrapper worked this time... Not really sure why I got CTD before but anyway, I'll take it

Good newsy

[dburne]

14 hours ago, Supmua said:

 --force_enable_VR is not needed if you already have VR option on in DCS setting.  Mine is always on but it's really up to you.

 

 

Ok made a seperate shortcut with the  --force_OpenXR nomenclature added to the shortcut and launched DCS, everything started properly in VR using Steam's Open XR I presume. I did select Open XR in Steam's Developer settings. Will test it out some later on in the day in a Spit campaign. Also appears I can still change resolution per app in Steam VR should I so desire.

Edited January 29, 2023 by dburne

[Supmua]

1 hour ago, dburne said:

 

Ok made a seperate shortcut with the  --force_OpenXR nomenclature added to the shortcut and launched DCS, everything started properly in VR using Steam's Open XR I presume. I did select Open XR in Steam's Developer settings. Will test it out some later on in the day in a Spit campaign. Also appears I can still change resolution per app in Steam VR should I so desire.

 

Try fpsVR to track performance too if you have it. 

[dburne]

1 minute ago, Supmua said:

Try fpsVR to track performance too if you have it. 

 

I do and sure will thanks.

[dburne]

Ok so flew some Spit campaign flying today using Steam VR's Open XR runtime. Performance was at least as good as Steam VR if not a little better. Kind of hard to tell for me as I run with vysnc on and locked to 45 fps - seems to give me a quite smooth experience that I am happy with and can run some higher graphics settings. I did get the impression the image quality in the cockpit was even a little sharper, some smaller text even easier to see it seemed.

I will probably stick with this for now using Steam VR's Open XR until ED gets the proper implementation for the Aero taken care of.  However if it takes too long for them to roll that out I may get curious and go ahead and try it with the wrapper.

Edited January 30, 2023 by dburne

[Supmua]

17 minutes ago, dburne said:

Ok so flew some Spit campaign flying today using Steam VR's Open XR runtime. Performance was at least as good as Steam VR if not a little better. Kind of hard to tell for me as I run with vysnc on and locked to 45 fps - seems to give me a quite smooth experience that I am happy with and can run some higher graphics settings. I did get the impression the image quality in the cockpit was even a little sharper, some smaller text even easier to see it seemed.

I will probably stick with this for now using Steam VR's Open XR until ED gets the proper implementation for the Aero taken care of.  However if it takes too long for them to roll that out I may get curious and go ahead and try it with the wrapper.

 

Glad to hear it’s working well for you.  There’re currently several ways to run DCS VR and it doesn’t hurt to explore them all.  I’m sticking with Steam’s OpenXR for now though because Steam Overlay is huge for me for quick access to Web or Chat box while gaming without taking off my headset.