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

[Supmua]

Just now, dburne said:

 

So far I have been extremely unimpressed with Varjo's Motion Smoothing. Don't think I have tried it running in DCS - MT yet, may have a look at it tomorrow.

You should check it out.  I was skeptical also, but not any more with the current beta and the latest MS implementation.

[Supmua]

Just now, motoadve said:

I only get this same experience as you when I do ground attack or sight seeing, super clear super smooth.

With WWII airplanes its harder because the fight its close to the enemy planes, so as soon as I am in a dogfight the other fighters look blurry when they are to the sides and almost in front, hope they can fix this, this is with a 4090 Locked at 45 with Motion Smoothing.

For up close dogfighting 90 fps with no reprojection is always going to be better, you don't have increased latency and image retention from reprojection.  But for everything else, including BVR combat, it's very good.

[motoadve]

17 minutes ago, Supmua said:

For up close dogfighting 90 fps with no reprojection is always going to be better, you don't have increased latency and image retention from reprojection.  But for everything else, including BVR combat, it's very good.

Exactly, this is why I would like to have a headset button programed it to turn it ON and OFF

[Supmua]

19 minutes ago, motoadve said:

Exactly, this is why I would like to have a headset button programed it to turn it ON and OFF

 Probably doable via Varjo's system button but the question is whether they'll put an effort into this.  Currently you can click the system button and then workspace icon to switch to desktop from within the headset, but have to manually switch Vsync off using VB (which is a quick mouse click btw).  They can easily add a button or half a dozen more to the headset pop up windows.  If they plan to no longer rely on Steam then this would be the way to go and I would prefer doing adjustment and setting via the headset popup layer, it seems more efficient this way.

Edited March 12, 2023 by Supmua

[Supmua]

Testing PD setting 0.9 with Aero's Higher setting.  The image quality is still very good at 0.9x and GPU FT drops by 1-1.5ms, when coupled with fixed foveation (wide/quality) which gives another 1ms GPU FT drop, the overall performance gain is quite good now that we no longer have significant CPU overhead.  I've been leaving Vsync on auto also, the overall performance is good enough that I no longer have to worry about locking fps.

[Gordy]

10 hours ago, etienne1968 said:

Hi gents,

Anyone please to outline his Varjo Aero settings to match latest DCS MT iteration. It's clearly confusing for newbies to understand how to set up adequately  V sync/motion smoothing combo  (fixed 45, 30 or automatic, enables if app supports it, etc..). Would appreciate as well if someone could post his DCS ingame system settings for a high end rig : I9 13900k + RTX 4090 + 64Gb RAM + SSD.  I'm pretty sure I miss something...

Many thanks in advance folks

@etienne1968 - I have the same hardware specs, except note that I downgraded from 64 gb to 32 gb so I could run my RAM at its full rated speed, 6600 MHz.   My cpu is overclocked to 5500 MHz.  Getting my RAM up to full speed earned me at least 10 fps, a significantly better improvement than having the extra ram. 

I have hyperthreading enabled, which seems to have made a significant difference in smoothness and stability vs. not having hyperthreading enabled. 

I'm using the native DCS OpenXR with mbucchia's hack to disable quad rendering.

My DCS shortcut to run DCS VR MT executes "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR --force_enable_VR

My varjo base settings:

Headset tab:

• Highest resolution quality
• Vertical sync disabled
• Motion smoothing disabled

Presentation tab:

• optimize performance on

System tab:

• Compatibility - openVR OFF
• Compatibility - openXR ON

My DCS settings:

 null 

If you want to buy some more frames, the first thing I'd do is step the varjo headset resolution down from "highest" to "very high".

In my Nvidia control panel settings Program Settings tab for dcs.exe, I have these non-default (bold) settings:

Antialiasing - FXAA: On
Antialiasing - Mode: Application-controlled
Low Latency Mode: On
Power Management mod: Prefer maximum performance
Texture Filtering - Anisotropic sample optimization: On
Texture Filtering - Quality: Performance
Texture Filtering - Trilinear optimization: On
Threaded optimization: Auto

The nvidia FXAA antialiasing makes a big difference without a performance hit, imho.

There's no reason to even consider motion smoothing if you have high enough frame rates.  I'm generally flying with 80-90 fps. 

[prancibald]

I was pretty unimpressed with this update at first, as it messed up the openVR method I've been using, but I bit the bullet and tried openXR.  Wasn't very impressed either.  But then I did a DCS slow repair, installed the wrapper that disables quad views, and now I can finally tell a difference.  Feels much smoother than it did before.

[Supmua]

DCS MT gives significant performance uplift in places that would normally trash your fps due to CPU bottlenecking.  You may not see much improvement in light missions depending on the settings and preexisting CPU/GPU frametimes, although this update also fixes shadows issues and should yield better performance in general even without MT.  The significant thing I notice is that my frametime graphs stay smooth with barely any spikes with the MT if I don’t go crazy on resolution setting, even with motion smoothing option.

Edited March 13, 2023 by Supmua

[F19_CoNa]

I just installed the open beta. Not that keen on running betas but I’ll bite the bullet this time.

 As I’m kind of new with the Aero, I saw that I had quad view when running it. Downloaded and installed the mbuccia wrapp, but I still get quad view.

Any advise on what I’m missing? 

[Supmua]

2 hours ago, F19_CoNa said:

I just installed the open beta. Not that keen on running betas but I’ll bite the bullet this time.

 As I’m kind of new with the Aero, I saw that I had quad view when running it. Downloaded and installed the mbuccia wrapp, but I still get quad view.

Any advise on what I’m missing? 

Make sure you run DCS.exe from bin-mt folder, not bin folder.  The non-mt build’s default output is still OpenVR and the wrapper doesn’t work with that unless you force OpenXR API via command line.

[dburne]

3 hours ago, F19_CoNa said:

I just installed the open beta. Not that keen on running betas but I’ll bite the bullet this time.

 As I’m kind of new with the Aero, I saw that I had quad view when running it. Downloaded and installed the mbuccia wrapp, but I still get quad view.

Any advise on what I’m missing? 

Insure you have the nomenclature correct in your shortcut properties. For instance mine is "D:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR  but I have mine installed on Drive D. Also note there is a space between the last quotation mark and first dash.

[F19_CoNa]

Thanks, you guys nailed it.

I was not using the bin-mt folder. Got it working now

[Pikas62]

On 3/11/2023 at 10:44 PM, Supmua said:

Ok it looks like DCS MT's default output is OpenXR instead of OpenVR.  Which means Varjo users no longer need to run command line to use OpenXR.  You can run the DCS app directly without any command lines or mods (except mbucchia's Quadview disable wrapper for Varjo OpenXR mode.  For Steam OpenXR no mod needed, just enable Steam as OpenXR runtime in SteamVR setting).  This is very nice, getting closer to plug and play.

 

It also seems OXRTK underestimated CPU frametime compared to fpsVR in my testing.  In F-16 Caucasus FF mission, my fps was in mid to high 80s from both OXRTK and fpsVR, and this was also confirmed by DCS's own fps tracker.  CPU FT reported by OXRTK was 7-8 ms while GPU FT was 9-10 ms, these numbers if true should give me >90 fps since both numbers are below 11 ms.  fpsVR on the other hand reported similar GPU FT but CPU FT was over 11 ms, which translates to final fps below 90 fps--hence appears better correlated.  Perhaps OXRTK CPU FT does not reflect the overall CPU FT but only within DCS app?

 

 

I have enabled Steam as OpenXR runtime in SteamVR settings. Can I undo this? I can't find a switch for this in the SteamVR GUI. Reset page to default doesn't seem to have any effect on this.

Edited March 13, 2023 by Pikas62

[dburne]

2 minutes ago, Pikas62 said:

 

I have enabled Steam as OpenXR runtime in SteamVR settings. Can I undo this? I can't find a switch for this in the SteamVR GUI. Reset page to default doesn't seem to have any effect on this.

 

 

Yes you undo Steam VR by selecting Open XR in Varjo Base...

[Pikas62]

26 minutes ago, dburne said:

 

Yes you undo Steam VR by selecting Open XR in Varjo Base...

 Ah, ok. Thank you!

[YouBet]

I'm having an issue that may be obvious to one of you (but not to me, so far).

Can't get Varjo to run properly when I use the executable in bin-mt. Whenever I select a mission (any mission, any type, any aircraft), my display (both on the headset and repeated in the monitor) is limited to a small portion in the upper left corner (picture below).

Error appears to be dependent on whether or not I enable OpenXR in Varjo Base. Oddly, whenever I deselect OpenXR in Varjo Base the game runs in 2D mode regardless of in-game settings or command line. DCS runs fine when I select the executable in the bin folder.

For full disclosure, I've submitted a report to the MT Error forum (no answers, yet), but you guys are the user-experts so I hoped to get your input. Thanks.

Intel 10990K at 5.3MHz, ASUS FTW3090, 64MB, Varjo HMD (ver 3.7.2.13 -- should I update to 3.9.0.10?)

[Supmua]

When you deselect Varjo OpenXR the game will not run in VR unless you also manually choose SteamVR as OpenXR runtime in SteamVR’s developer setting (because there’s no longer a specified runtime to execute OpenXR API). 
 

If you are using any mod/add ons I recommend removing them all except mbucchia extension wrapper that disables quad output.  Might be a good idea to do DCS repair also. 
 

You do not need any command line to run DCS mt as the default output is now OpenXR.  You just pick either Varjo or SteamVR runtime to run OpenXR. 

Edited March 13, 2023 by Supmua

[Harlikwin]

So,

Random question for folks. I've had this thing for less than a month, and its been babied. I have recently started to have some issues where I see a "flash" of static in parts of the screen for split second. Usually the upper part of the screen. Anyone else see this? I'd assume its a cable issue as I've seen stuff like this on a very used and abused G2 cable. But AFAIK I've never done anything "mean" to the Aero cable.

 

[dburne]

23 hours ago, dburne said:

 

So far I have been extremely unimpressed with Varjo's Motion Smoothing. Don't think I have tried it running in DCS - MT yet, may have a look at it tomorrow. I am still quite amazed at the performance I am getting in DCS with my Aero now with the MT version.

 

Gave Varjo's Motion Smoothing a shot earlier today with the MT version of the game. It was better , but still lacking for me. I am averaging between 70-90 fps , usually around 80-90  and to me the experience is better still with Motion Smoothing off.  Maybe I will check it again around 1st of next year when I get a new motherboard and CPU.

[Supmua]

58 minutes ago, Harlikwin said:

So,

Random question for folks. I've had this thing for less than a month, and its been babied. I have recently started to have some issues where I see a "flash" of static in parts of the screen for split second. Usually the upper part of the screen. Anyone else see this? I'd assume its a cable issue as I've seen stuff like this on a very used and abused G2 cable. But AFAIK I've never done anything "mean" to the Aero cable.

 

Could be cable issue.  Mine is also a bit loose at the HMD connection.  Try unplugging the cable to the headset’s top left compartment and twist it 180 degree before plugging back in, that may solve the problem but if it persists then you should contact tech support.

8 minutes ago, dburne said:

Gave Varjo's Motion Smoothing a shot earlier today with the MT version of the game. It was better , but still lacking for me. I am averaging between 70-90 fps , usually around 80-90  and to me the experience is better still with Motion Smoothing off.  Maybe I will check it again around 1st of next year when I get a new motherboard and CPU.

Maybe I have higher tolerance for VR artifacts, for me it’s quite acceptable and playability-wise it’s a toss up between this and 45 fps lock without MS.  Or perhaps I’m so used to playing games with PSVR2, on that setup motion reprojection is pretty much the norm as the PS5 can’t really generate 90 fps in most games.

[dburne]

1 hour ago, Supmua said:

Could be cable issue.  Mine is also a bit loose at the HMD connection.  Try unplugging the cable to the headset’s top left compartment and twist it 180 degree before plugging back in, that may solve the problem but if it persists then you should contact tech support.

Maybe I have higher tolerance for VR artifacts, for me it’s quite acceptable and playability-wise it’s a toss up between this and 45 fps lock without MS.  Or perhaps I’m so used to playing games with PSVR2, on that setup motion reprojection is pretty much the norm as the PS5 can’t really generate 90 fps in most games.

Running mine no fps lock and no vsysc and am pretty happy. At least so far.

[Supmua]

I’ve been testing auto Vsync with MS, no big issues so far for what I typically do (no massive MP stuff).  In non congested areas it’s pretty much 90 fps without reprojection and if I can’t maintain 90 then it would transition to 45.  The key is to leave some headroom in the settings for situations that would cause brief performance drop to maintain smoothness (for me this is done via using PD 0.9 or Steam’s sub sampling if you run via Steam OpenXR, fixed foveated rendering, flat terrain shadows—these would drop GPU FT by at least 3ms without significant reduction in image quality).  MS used to have a huge performance hit, but the mt build + new shadows patch + conservative settings make this viable now at least on my setup.  I get zero ground object blur this way.  Dogfight upclose is still a miss with close object separation at high speed but this happens with any iteration of motion smoothing, so Varjo’s MS is imo now roughly as good as HTC or Steam’s implementation.

Edited March 14, 2023 by Supmua

[Supmua]

MT vs non-MT CPU Utilization

(Apache Syria Hot ramp mission)

As you can see, MT build is really the only way forward.  Much better utilization of CPU power, no jumping between cores.

Edited March 14, 2023 by Supmua

[Slick Twitchy]

Couple of weird things after Varjo Base update: 1) Using the shortcut from Bin-MT folder- WITH NO  "--force_OpenXR  --force_enable_VR"- and it runs fine-no quad view etc. I had previously installed the necessary wrapper.

2) Open XR doesn't work-even if safe mode. Have to fully uninstall, and/pr uncheck DSC.exe box in OPENXRTK.

Anyone else have similar experiences?

[Pikas62]

@Supmua & dburne: Thank you very much for your great support! I have enabled Steam as OpenXR runtime in SteamVR settings and with the same settings (45 fps lock, vertical sync on, MS off, SteamVR 122%) I have an even smoother experience with MT. Almost no FT peaks at all! When I disable fps lock I can see that I have over 30% increase in fps with MT. I am now, also thanks to you, super satisfied with MT and am already looking forward to the coming iterations :-).