Jump to content

Varjo Aero: General guide for new owners


Supmua

Recommended Posts

Last Update: 05/21/2023.

**The current state of muti-threaded DCS beta & Dynamic Foveation with the Aero**

-Default output is Varjo OpenXR, hence no need to be run via shortcuts/command lines (at least as of now).  Single threaded DCS still uses OpenVR API as default.

-With multi-threaded DCS which is now highly recommended when used with dynamic foveated rendering, forcing Steam OpenVR mode (--force_steam_VR) can cause freezing while forcing Varjo OpenVR mode (--force_varjo_VR) can cause graphic glitches.

-OpenXR-InstanceExtension wrapper is required for Varjo OpenXR runtime to disable quad view output (no need for Steam OpenXR runtime).  When you update VB, this will also need to be reinstalled.

-XRnecksafer b5 can cause DCS crash in Steam OpenXR mode even when it's not running (possible redundant/residual OXR layers), uninstall it to resolve this if you have the issue.

-OpenXR Toolkit v1.3.0 now supports chromatic aberration correction.  This helps minimize chromostereopsis effect and is highly recommended, but it is currently not compatible with DFR mode.

-OpenXR Toolkit's Turbo Mode causes both CPU and GPU frametime spikes in Steam OpenXR mode on my setup, YMMV.

-Moderate increase in minimum and avg fps is seen with DCS MT for most people, especially in CPU intensive scenarios (MP, complex missions, etc.).

-Motion smoothing works really well in Fixed 45 fps, providing that you can maintain fps above that number.  On my setup the cost is 2.5-3.0 ms increase in CPU frametime and 1.0 ms in GPU frametime, YMMV.

-Flat shadows no longer impose excessive performance penalty, but there might still be issues with other shadow settings.

-Buildings are way too reflective at night with strange white flashes with night lightings.

-DCT multi-thread exe is a new app and is located in a separate folder (bin-mt), if you used to run DCS via the old shortcut it will not work because it will still activate the old single threaded DCS which is still present in the regular bin folder.  This may change in the future once DCS mt becomes mainstream.

-Dynamic Foveated Rendering now works via Quad View mode.  This is done via mbucchia's Varjo Foveated mod Home · mbucchia/Varjo-Foveated Wiki · GitHub, note that OXTRK is not compatible with quad view and should be disabled.  In the past, we've tried to avoid using this mode because of poor performance and double cursor issue.  However, with Varjo Foveated mod things have taken 360 degree turn and you can now achieve both performance and visual quality with quad view + dynamic foveation.  Single-threaded DCS.exe still works the exact same as before, meaning quadview mirror screen as well as double cursor problem, and still uses OpenVR API by default.

-With DFR mode my PC crashed with peripheral_multiplier <1.0 in settings.cfg at 35 and 37 PPD, no issue with 39 PPD or multiplier >1.0.

-In DFR mode there seems to be a faint square-shaped box in the central FOV that's lighter in color.  This is more visible to some people, and we think that this is where Varjo renders its focus screen since that has fixed 1:1 pixels rendering depending on your PPD setting in VB.  I wonder if this is superimposed directly on the top of the peripheral screen creating slight color or brightness mismatch.

 

Introduction

When Varjo Aero was initially released in the beginning of 2022 DCS support was very bare boned and several owners in this forum had difficulty with the setup, so I've created this basic guide so that new Aero owners will hopefully be able to quickly set up their HMDs to play DCS with minimal headache.  Knowing how your headset operates is a big factor when it comes to maximizing performance and VR experiences.  Please feel free to also share tips and tricks that you may have.

Varjo Aero is a SteamVR device, thus relies on Vive/Valve base stations and SteamVR framework for tracking.  Other than Steam OpenVR and OpenXR, the headset also offers Varjo OpenVR and OpenXR modes (bypassing SteamVR's user interface).  These settings are adjusted on Varjo Base app.  Note that turning OpenVR or OpenXR on in the Varjo Base app will give priority to Varjo's runtime over SteamVR's.  The Varjo software lacks Bluetooth sleep functionality and owners have to rely on external app (phone or PC) to put the base stations in sleep mode.  The headset itself also lacks on/off switch and it might be a good idea to use a smart plug for turning it off to help prevent overheat or screen burn-in when not in use, unless you want to plug/unplug the power cord manually.  Varjo sports Quad rendering (besides Stereo) rendering for extra image clarity but at the cost of performance which is not good for general gaming.  If you see double cursors in DCS VR, this means you're in Quad rendering which is not desirable as it decreases the performance.

The latest DCS openbeta now supports native OpenXR output, but the default API when you doubleclick DCS.exe icon remains OpenVR.

Some Primers

HMD Sweetspot: can be small or large, refers to placement positions of your HMD on your head that will allow maximum clarity but not necessarily max FOV.  Aspheric lens allows the Aero to have larger sweet spot than headsets with fresnel lens, however the Aero’s sweetspot us still not that large if you want to get maximum clarity.  Optimal placement varies among individuals because we don’t have the same facial type and size.  In my case, the headset needs to be slightly away from my face rather than closer—at the max clarity sweetspot I can almost spot individual pixels on the Aero’s screen.

API (application programming interface): is an interface between application and runtime.  Examples: OpenVR, OpenXR, Oculus OVR.

Runtime: software platform that executes API (SteamVR, Varjo, WMR, Oculus, HTC Vive).  Only one can be active at a time.


OpenVR: this is Steam's native VR API, being transitioned to OpenXR which is newest kid on the block.  Hence SteamVR platform supports both OpenVR and OpenXR APIs (and also OVR, see below).

OpenOVR or libOVR: this is the Oculus VR API.  No longer developed for PC as Meta seems to have abandoned PCVR platform.

OpenXR: the newest VR API which will become the gold standard in the near future.

OpenComposite: this was initially developed as a way for Oculus headsets to use SteamVR games natively without going through SteamVR layer.  Later on it branched off into OpenComposite OpenXR which allows OpenXR headsets to access SteamVR games natively bypassing SteamVR layer.

ReVive: developed as a way for SteamVR headsets to use Oculus games natively.  Seems to have been abandoned which is too bad.

Four different ways to run DCS with the Aero

A. Varjo OpenVR:  ["*\bin\DCS.exe"] -> Varjo OpenVR.  This is the current default path (and I think it's the same as --force_varjo_VR command line) if you choose to run DCS normally by doubleclicking DCS.exe icon, but at present not recommended (until Varjo fixes it) due to double cursor and poor performance issues (it seems to be using Varjo’s Quad rendering mode without foveation).  You can recognize this mode by checking the VR mirror window (with DCS running) on PC monitor which will show 4 mirror screens instead of 1 or 2.

B. Steam OpenVR:  ["*\bin\DCS.exe" --force_steam_VR] -> SteamVR -> Steam OpenVR.  This requires running DCS via a custom shortcut with --force_steam_VR command.  This mode uses Stereo rendering rather than Quad which is much better for performance, allows SteamVR overlay screen as well as running other Steam's OpenVR apps with DCS (fpsVR, Reshade 5, etc.). This mode requires you to run DCS WMR cross eye correction and flip top/bottom for each eye to correct menu distortion, will create hedy.lua file in the Saved game folder—delete this file and restart DCS to modify crosseye correction settings).  This method currently has crashing issues with multi-threaded DCS, so use with single-threaded version for best results.

C. Varjo OpenXR:  ["*\bin\DCS.exe" --force_OpenXR] -> Varjo OpenXR. This is also Quad screen rendering at present and there are now two ways of running DCS with this.  The newer method is quad view eyetracking (dynamic foveated rendering/DFR) mode using the new multi-threaded DCS via Varjo Foveated mod (Home · mbucchia/Varjo-Foveated Wiki · GitHub ), and the older method is stereo view mode via InstanceExtensions wrapper mod (https://github.com/mbucchia/OpenXR-InstanceExtensionsWrapper/releases).

D. Steam OpenXR:  ["*\bin\DCS.exe" --force_OpenXR] ->SteamVR ->Steam OpenXR. This method requires turning off Varjo OpenXR in Varjo Base app, as well as toggle Steam as default OpenXR platform (in SteamVR Setting/Developer window).  This shunts the OpenXR output to SteamVR and the output becomes Stereo rendering which is desirable (Steam OpenXR currently does not support Varjo specific extensions such as Gaze tracking or Quad view).  Steam OpenXR characteristically will autocenter DCS main menu, which is different from Varjo OpenXR which requires recentering upon starting DCS.

There's also a 5th way which uses OpenComposite OpenXR wrapper to translate OpenVR to OpenXR (can be used with either Varjo or Steam OpenXR route), but this is no longer needed as of the latest beta so I have removed the entire section on this.

Suggested Startup Sequence:

1. Boot PC, turn on the Vive/Valve Basestations and controllers, plug in Varjo Aero headset.

2. Run Varjo Base app.  This process needs to be running at all time.  Put on the headset per instructions in the manual.

3. Make sure that real-time mirror screen is working, as this indicates normal operation.  If "no headset is connected" message is present, unplug the USB-C cable from the upper left compartment of the headset and reseat this (pull diagonally and push back in).  Frequent headset disconnection messages could be a due to loose contact at that spot, unplug the cable and twist it 180 degrees and plug back in can help secure the connection at the USB socket.

The Basic Process:  not exactly a simple plug and play

1. Varjo Base: choose High/Higher/Highest setting (I personally use Higher or Highest).  setting: OpenVR ON, OpenXR ON.  Vertical sync OFF (ON if your PC can maintain stable >45 fps).  At present, turning OpenVR OFF will break SteamVR functionality so this is not recommended.

2. Create a DCS shortcut on Windows desktop and add the --force_steam_VR command to the target box (or --force_OpenXR if you want OpenXR output) with a space between the preexisting texts and the --force_**.  This is at present mandatory to get DCS to run correctly (with Stereo rather than Quad display) in either OpenVR or OpenXR mode with the Aero.  Texts are case sensitive, so double check your typing before proceeding to the next step.

3. For Steam OpenXR turn Varjo OpenXR switch to OFF in Varjo Base, and in SteamVR Setting/Developer choose Steam as the default OpenXR platorm.  For Varjo OpenXR mode, install mbucchia's wrapper (link above) to disable Quad view, and leave the Varjo OpenXR switch to ON in Varjo Base.  Varjo OpenVR should be left to ON at all time.

4. Setup Cross eye correction tool as needed.  Typically no need if you use OpenXR.

DCS Settings

-Main Tab: VR preset.  Use this preset as the initial setting, then start adjusting various parameters as needed after flying around and getting a feel for default image quality.  I strongly recommend MSSAx2 as it helps minimize shimmering.  Increase Textures/Water/Visibility/Shadows to higher settings as needed.

-VR Tab: Enable VR Headset in check box, Pixel Density 1.0

How to: Steam OpenVR Mode (single-treaded DCS only)

1. This mode supports all SteamVR extensions.  Which means you use Steam overlay, desktop window display within DCS, fpsVR, Reshade, etc.

2. Locate DCS.exe, create a shortcut on desktop.

3. Right click the shortcut, properties.  In target window add a command clause so that it shows "*:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_steam_VR

4. Run DCS via this shortcut.

5. Do top/bottom swap for both eyes via Crosseye tool window, SAVE.

6. If you see double cursors in cockpit view, then you are not in Steam's OpenVR mode and likely in Varjo's OpenVR mode.

7. For SteamVR mode.  Make sure that rendering resolution is setup properly to avoid getting suboptimal image quality.  I recommend leaving Global resolution at 100% of whatever your Varjo setting is, and change Video/Per-app resolution to your liking (I typically use 3268x2800 pixels for DCS).  You'll likely need to downsample from the global rendering resolution in order to maintain good fps and frametimes.  Keeping global resolution at 100% is also very important for other uses such as Web browsing or Movie watching, as chromatic aberration can get quite ugly unless the rendering resolution is properly matching or higher than the physical screen pixels.

NEW--How to: DCS multi-threaded via Varjo OpenXR

1. DCS MT outputs OpenXR only at present (on Varjo headsets it uses Varjo OpenXR bypassing Steam), hence it does not require shortcut or command lines to run but you need to make sure to execute the app from the correct folder which is \bin-mt\ (the old DCS app still resides in \bin\ folder which is single-threaded).  This will likely become the preferred mode for most users because it gives the best performance and visuals compared to other modes when coupled with Dynamic Foveation, even in early stage of release.

2. This version supports dynamic foveation, but needs mbucchia's Varjo Foveated mod to work.  (Home · mbucchia/Varjo-Foveated Wiki · GitHub).  The files are installed in %ProgramFiles%\OpenXR-Varjo-Foveated\ folder, in case you need to remove them later.  You can still force stereo view mode via mbucchia's Instance Extensions wrapper (GitHub - mbucchia/OpenXR-InstanceExtensionsWrapper: An OpenXR runtime wrapper to mask selected instance extensions.).  Use only either one of these mods because they're not compatible with each other, the latter one disables quad view while the former one promotes quad view with eyetracking.

3. If Varjo Foveated mod is used, OpenXR toolkit must be either disabled (via companion app) or uninstalled.  Alternatively, you can also selectively disable DCS from the supported game list in OXRTK companion app.

4. In Varjo Base app, ensure Varjo OpenXR switch in ON.  (Steam OpenXR runtime will also work but does not support DFR, hence poor perfomance).  Varjo OpenVR should also be ON for general compatibility with SteamVR apps which typically uses OpenVR API.

5. Run DCS.exe directly from \bin-mt\, or create a new shortcut for it.

6. You will also notice Varjo Gaze background process in the Task Manager, which indicates that DFR is active.

How to: Steam OpenXR Mode

1. This mode also supports SteamVR layer, meaning Steam has partial control of the headset and you get desktop access via VR overlay screen as well as ability to run compatible apps such as fpsVR, etc.  You can set specific rendering resolution via Steam's setting.  DCS VR main menu positioning is correct without recenter. 

2. Locate DCS.exe, create a shortcut on desktop.

3. Right click the shortcut, properties.  In target window add a command clause so that it shows "*:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_OpenXR.

4. In Varjo Base app, toggle off Varjo OpenXR, leave OpenVR switch on.

5. In SteamVR setting window, go to Developer section and choose Steam as OpenXR default platform.

6. Run DCS via this shortcut.

How to: Varjo OpenXR Mode

1. This mode bypasses SteamVR so you will not have access to Steam layer.  You also lose the ability to change resolution via Steam but can still do it in Varjo Base app via Resolution Quality Presets (only 6 options available at present).  Quad view output is used and you have options via mbucchia's mods to use quad view with dynamic foveated rendering (Home · mbucchia/Varjo-Foveated Wiki · GitHub), or stereo view without eyetracking (GitHub - mbucchia/OpenXR-InstanceExtensionsWrapper: An OpenXR runtime wrapper to mask selected instance extensions.).

2. Locate DCS.exe (either in \bin\ or \bin-mt\ folder depending on single-threaded vs multi-threaded version), create a shortcut on desktop.

3. Right click the shortcut, properties.  In target window add a command clause so that it shows "*:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_OpenXR.  If you are using multi-threaded DCS then use \bin-mt\DCS.exe for the shortcut intead.

4. In Varjo Base app, leave both OpenVR and OpenXR switches on.

5. Run DCS via this shortcut.

How to: Correct Cross-eye Issue

1. This is no longer needed with OpenXR, but you still have to do this with Steam OpenVR mode.

2. Follow this thread.  


Motion Smoothing option

Useful for smoothing out fast moving objects so everything remains sharp and clear, at present works best when coupled with 45 fps lock mode.  It will tax GPU frametime by 4.5-5ms which is a lot so best used when your frametime without motion smoothing is >16.6 ms (or 60 fps) in order to minimize artifacts.

 

How to: Reshade 5 with DCS

1. Reshade 5 is a powerful and popular image postprocessing utility with dozens if not hundreds of different filters to choose from.  It is currently compatible with SteamVR's OpenVR mode only.  Setting in VR mode is currently done via SteamVR's overlay using SteamVR compatible controllers only as well (keyboard input is for non-VR mode only).

2. Download Reshade 5 from https://reshade.me

3. Install Reshade 5, choose the folder that contains DCS.exe, choose DirectX 10/11/12 option (not DirectX 9, not OpenGL), choose desired filter groups (default ones are pretty adequate).

4. Run DCS via SteamVR's OpenVR mode.  Bring up SteamVR overlay (press the recessed system button on your controller), click on Reshade 5 icon to activate it.  Check Performance mode with VR controller and select the filters you want to use (I recommend Lumasharpen and Tonemap).  Uncheck Performance mode to go into setting mode.  Adjust the setting parameters as needed, when done check Performance mode again and hide SteamVR overlay (press system button).

5. To remove Reshade, uninstall with installer app.

How to: XRNeckSafer

(This is to mimic TrackIR's accelerated turning.  For OpenXR mode only.  For OpenVR use VRNeckSafer by the same author)

1. Download from here Norbert Siepenkötter / XrNeckSafer · GitLab

2. Install as per instructions on web page.

3. Run XRNeckSafer.exe app, Autorotation Smooth, adjust parameters to suit your taste (ex: Start at 80 deg, Amplify by 200% both eyes).

Varjo Audio Jack:

-supports mic with TRRS CTIA standard (mic ring is the furthest away from the tip).

-For ease of use I prefer high quality IEMs with built-in mic as they have very low profile with really good audio (sounds several times better than Varjo’s default IEMs) and the in-line mic typically produces adequate voice quality for gaming.

-modern Chinese IEMs are relatively cheap yet produce very high quality sounds, but many use OMTP standard with swapped mic and ground rings so mic will not be functional right off the bat.  This can be made to work by using OMTP-CTIA adapter.

Misc:

1. Each NVIDIA driver update seems to affect the profile setting which could result in suboptimal visuals in VR (at least on my setup).

2. To ensure you get optimal stereoscopy and visual clarity, download NVInspector NVIDIA Inspector Download version 1.9.8.1 (guru3d.com) and choose default profile (should already be loaded by default on startup), and just click apply changes (may have to first pick a setting, make a change and change it back before applying changes).  Then close the app.

3. Chromostereopsis test.  See if you can experience different layers of depth from color patterns. This illustrates that we don't have the same 3D perception as some people will not see the varying depths from this flat 2D image, while others will see up to 4 different layers of depths.

Image that may show effects of chromostereopsis - Chromostereopsis - Wikipedia

4. Useful video to test your VR HMD to spot various issues (mura, color retention, blooming, motion artifacts, etc.).

5. How to delete unwanted OpenXR_API layers that persisted despite complete uninstallation (such as XRnecksafer).  Regedit and go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1\ApiLayers\Implicit, then delete the unwanted API layer individually (at your own risk).

 

Bonus: Play flatscreen games in 3D Stereoscopy on your VR headset

1. Requires: Reshade 5, App that can display 3D side by side mode (I use Virtual Desktop), Reshade compatible games (most games out there, for example, Cyberpunk 2077.  I particularly enjoy slower paced adventure games in 3D stereo, especially the new VTM Swansong).

2. Install Reshade 5 to the game, select appropriate graphics API (DX, OGL, Vulkan, etc.) for that particular game, make sure to include Depth3D filter collection by BlueSkyDefender during installation.

3. Run Virtual Desktop (or similar app), load the game.

4. Press Home key to open Reshade Menu (2D API not via VR layer).

5. Activate SuperDepth3D_VR filter.  You may need to uncheck performance box to make adjustment.

6. In Depth Map setting, switch DM0 to DM1 reversed.  Increase ZPD balance to 0.500 (version 5.2.2+ only)

7. Change Depth Map Adjustment (max 250) and Divergence (max 50) sliders as needed for 3D effects.

8. Press Home to hide Reshade menu.

9. Activate 3D side by side display mode (F7 in Virtual Desktop).

10. For best performance, minimize postprocessing effects as well as antialiasing for that particular game.

11. The farther away the virtual screen is from the eyes, the better the 3D effects.  Zoom out or increase the screen distance (Virtual Desktop) if you have to.

 

My current High-End settings via OpenXR mode (perfect for demonstrating jaw-dropping image quality on the Aero)

Varjo: Higher Quality, Brightness 75%, Vsync 45 fps fixed or auto, motion smoothing Always enabled.

DCS: High Preset but turn off SSAA, SSLR, SSAO.  DCS Gamma 2.0.

*Post processing with OXTRK to make it pop:  leave DCS gamma at 2.2, OXRTK post processing on (contrast 60, brightness 45, saturation 53).

 

My current single player 90 fps setting via DFR OpenXR mode with DCS MT

Varjo: Higher Quality, Brightness 75%, Vsync off.

DCS: VR Preset but high Water and Shadows, MSSAx2.  DCS Gamma 2.0.


Edited by Supmua
  • Like 8
  • Thanks 8

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

Thanks for creating this guide!  Just received my Varjo Aero a few days ago, spent the weekend working through issues.  Can strongly recommend the --force SteamVR and Cross Eye fix to eliminate most of the new user issues I was encountering.

One question: improving color saturation.  I've been using a 2018 HTC Vive Pro, and the Aero offers a leap forwards in clarity that is jaw-dropping.  Small cockpit instruments are finally readable, and I'm spotting individual ground vehicles from 10,000 ft.  However, DCS in the Aero looks far more "washed out" than my old Vive Pro.  Part of this is the move from OLED to LCD, and I'm accepting that nighttime missions now look more dark grey than true black, but I'm hoping for options to increase color saturation.  I recently finished the Hormuz Freedom campaign for the AV-8B, and some of the best moments were the rich colors of the sunsets over the Persian Gulf.  

I haven't tried Reshade 5 yet, but I was also hoping to move to OpenXR to improve smoothness.  Seems that Reshade 5 only works for SteamVR?  

Any suggestions from other Aero users?


Edited by Istari6
Link to comment
Share on other sites

6 hours ago, Istari6 said:

Thanks for creating this guide!  Just received my Varjo Aero a few days ago, spent the weekend working through issues.  Can strongly recommend the --force SteamVR and Cross Eye fix to eliminate most of the new user issues I was encountering.

One question: improving color saturation.  I've been using a 2018 HTC Vive Pro, and the Aero offers a leap forwards in clarity that is jaw-dropping.  Small cockpit instruments are finally readable, and I'm spotting individual ground vehicles from 10,000 ft.  However, DCS in the Aero looks far more "washed out" than my old Vive Pro.  Part of this is the move from OLED to LCD, and I'm accepting that nighttime missions now look more dark grey than true black, but I'm hoping for options to increase color saturation.  I recently finished the Hormuz Freedom campaign for the AV-8B, and some of the best moments were the rich colors of the sunsets over the Persian Gulf.  

I haven't tried Reshade 5 yet, but I was also hoping to move to OpenXR to improve smoothness.  Seems that Reshade 5 only works for SteamVR?  

Any suggestions from other Aero users?

 

OpenXR Toolkit has Saturation and other image settings if you want to go that route. See the Varjo OpencompositeACC thread.  OLED panel while known for true black, it’s also weaker in the brightness and white area so you can’t compared image quality at default 100% brightness without some adjustments in gamma and so on because the miniLED will come out brighter and more faded.  Night flying won’t be as immersive but that’s the way it is for non-OLED screen.

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

1 minute ago, Supmua said:

OpenXR Toolkit has Saturation and other image settings if you want to go that route. See the Varjo OpencompositeACC thread.  OLED panel while known for true black, it’s also weaker in the brightness and white area so you can’t compared image quality at default 100% brightness without some adjustments in gamma and so on because the miniLED will come out brighter and more faded.  Night flying won’t be as immersive but that’s the way it is for non-OLED screen.

At first I thought the toolkit was not necessarily working with the Aero and Open XR , so he has the toolkit settings now working with the Aero?

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

6 hours ago, dureiken said:

Hi

I just have a question for Aero : is there still shimmering ? 🙂 shadows, buildings, lines ...

 

thanks !

Yes but it’s pretty much next to nothing in OpenXR mode or OpenVR with reduced exposure setting.  Lines, shadows and bridges, mostly no.  Some on buildings only in high contrast lighting.

5 minutes ago, dburne said:

At first I thought the toolkit was not necessarily working with the Aero and Open XR , so he has the toolkit settings now working with the Aero?

Toolkit has working resolution override, fixed foveated rendering, image postprocessing, FOV and world adjustment.


Edited by Supmua

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

22 minutes ago, Supmua said:

Yes but it’s pretty much next to nothing in OpenXR mode or OpenVR with reduced exposure setting.  Lines, shadows and bridges, mostly no.  Some on buildings only in high contrast lighting.

Toolkit has working resolution override, fixed foveated rendering, image postprocessing, FOV and world adjustment.

 

oh nice ok thanks, and on steam VR ? 🙂 because I can't use OpenXR for the moment

 

Link to comment
Share on other sites

35 minutes ago, dureiken said:

oh nice ok thanks, and on steam VR ? 🙂 because I can't use OpenXR for the moment

 

Yes. 

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

Thanks for sharing. I got my Aero today and out of the box it's useless in DCS (horrible stutters and I get double cross-hairs cursors so I can't click anything in the v-cockpit).

i then found this post and realized the combo DCS/Aero/OpenVR is a known no-no. I did use OpenComposite with my G2 before so I tested the same but that made DCS crash (see attached screenie). I then tried your version but got the same result.

One thing though: In you guide you mention OpenVR cannot be the default in Varjo Base. In "System" there are two switched, for OpenVR and OpenXR and both are selected. But how do I make OpenXR the default?

 

Screenshot 2022-05-03 224322.png


Edited by moggel

i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS

Link to comment
Share on other sites

v01.png

v02.png

**With the latest software update, OpenVR switch should be on to ensure normal operations with SteamVR.


Edited by Supmua

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

3 hours ago, moggel said:

Thanks for sharing. I got my Aero today and out of the box it's useless in DCS (horrible stutters and I get double cross-hairs cursors so I can't click anything in the v-cockpit).

i then found this post and realized the combo DCS/Aero/OpenVR is a known no-no. I did use OpenComposite with my G2 before so I tested the same but that made DCS crash (see attached screenie). I then tried your version but got the same result.

One thing though: In you guide you mention OpenVR cannot be the default in Varjo Base. In "System" there are two switched, for OpenVR and OpenXR and both are selected. But how do I make OpenXR the default?

 

 

Strange I have no issue at all running DCS/Aero/ Steam VR.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

3 hours ago, dburne said:

Strange I have no issue at all running DCS/Aero/ Steam VR.

SteamVR is currently my preferred mode also, very flexible especially if you want to use Reshade.

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

Ok, disabling OpenVR in Varjo Base and adding "--force_steam_VR" seems to allow me to run in OpenXR (although a bit non-intuitive considering the "--force_steam_VR" flag). This fixes the double cursor problem and the stutters but the overall experience is so laggy I can't play the game at all.

Specs:

i9-11900K @ 3.50GHz, 32Gb RAM, RTX3080


Edited by moggel

i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS

Link to comment
Share on other sites

Well moggel I have the opposite to you. Am  getting the double mouse cursor problem (one bright , one dim with the active selection somewhere in between...) but good performance. I too have disabled OpenVR in Varjo Base. To further complicate, the "--force_steam_VR"  broke  VR completely in DCS so I reverted to manually run SteamVR  which I've been doing for the couple of days that I've been setting up my new Aero.

Have done quite a bit of searching on the double mouse cursors to no avail so far.

 

I have i9-10900K @ 3.7GHz, 32Gb RAM ,  RTX3090

Link to comment
Share on other sites

Re-read your guide and realized the --force_steam_VR should've been added in the first place. So, re-enabled OpenVR in Varjo Base and reset the DCS binaries to disable OpenComposite's OpenXR support and tried again.

The stutters are much better and the double cursors phenomenon is fixed. But I get a very pronounced distortion effect, making the whole experience feel like I'm looking through some fish eye lense. Also, it's still pretty laggy, compared to my G2 experience. Moving my head quickly from side to side produces significant lag.

i9-11900K @ 3.50GHz, 32Gb RAM, RTX3080


Edited by moggel

i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS

Link to comment
Share on other sites

On 5/4/2022 at 2:36 AM, moggel said:

Re-read your guide and realized the --force_steam_VR should've been added in the first place. So, re-enabled OpenVR in Varjo Base and reset the DCS binaries to disable OpenComposite's OpenXR support and tried again.

The stutters are much better and the double cursors phenomenon is fixed. But I get a very pronounced distortion effect, making the whole experience feel like I'm looking through some fish eye lense. Also, it's still pretty laggy, compared to my G2 experience. Moving my head quickly from side to side produces significant lag.

i9-11900K @ 3.50GHz, 32Gb RAM, RTX3080

 

Varjo’s OpenVR should be OFF at all times, because that mode causes significant stuttering.  If that mode is on it might bypass SteamVR’s OpenVR. 
Did you do the cross eye correction step to correct the distortion?

 

EDIT: With the latest update, leave Varjo OpenVR to ON to avoid issue with SteamVR.  It will still be bypassed if you run DCS via force_steam_VR command.


Edited by Supmua

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

1 hour ago, Supmua said:

:
Did you do the cross eye correction step to correct the distortion?

No, the cross-eye issue was resolved by --force_steam_VR it seems. Without that flag I had that problem but the debug tool also didn't have any effect. I'll turn off OpenVR in Varjo now and try again. Thanks for helping out! Much appreciated!


Edited by moggel

i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS

Link to comment
Share on other sites

Ok, I must be misunderstanding something. I turned off Varjo's OpenVR support and started DCS with the --force_steam_VR flag.
When I started DCS I got this from SteamVR:

Screenshot 2022-05-04 144151.png

i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS

Link to comment
Share on other sites

42 minutes ago, moggel said:

Ok, I must be misunderstanding something. I turned off Varjo's OpenVR support and started DCS with the --force_steam_VR flag.
When I started DCS I got this from SteamVR:

Screenshot 2022-05-04 144151.png

Yeah I got the same back when I tried it some time ago, I just leave Open VR selected in Varjo Base.  Does not seem to affect my performance negatively.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

1 hour ago, moggel said:

Ok, I must be misunderstanding something. I turned off Varjo's OpenVR support and started DCS with the --force_steam_VR flag.
When I started DCS I got this from SteamVR:

Screenshot 2022-05-04 144151.png

If you see SteamVR GUI window then you’re on the right track for SteamVR mode. However, the display connection trouble warning indicates something is wrong with the connectivity between GPU and headset. 
 

I would unplug both ends of the USB-C cable from the headset and the hub, and reseat them. Do a headset reset. If the problem persists then you should contact Varjo tech support. 


Edited by Supmua

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

That is weird I just had another look and my Varjo Base shows Open VR disabled and Open XR enabled. I don't think I need Open XR enabled unless I am using MSFS 2020. Going to disable and see what happens.

I could have swore the last time I tried disabling Open VR I was getting that same error message. Computers, gotta love em!


Edited by dburne

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

40 minutes ago, Supmua said:

If you see SteamVR GUI window then you’re on the right track for SteamVR mode. However, the display connection trouble warning indicates something is wrong with the connectivity between GPU and headset. 
 

I would unplug both ends of the USB-C cable from the headset and the hub, and reseat them. Do a headset reset. If the problem persists then you should contact Varjo tech support. 

 

If I indeed have a connectivity issue, shouldn't that also affect it when I turn ON Varjo's OpenVR option?

i7-3930K CPU @ 3.20GHz; 16Gb DDR3; GeForce GTX 1070; Windows 10; TM Warthog HOTAS

Link to comment
Share on other sites

45 minutes ago, dburne said:

That is weird I just had another look and my Varjo Base shows Open VR disabled and Open XR enabled. I don't think I need Open XR enabled unless I am using MSFS 2020. Going to disable and see what happens.

I could have swore the last time I tried disabling Open VR I was getting that same error message. Computers, gotta love em!

 

Don you can also run MSFS with OpenXR via SteamVR but Varjo’s OpenXR is supposed to offer slightly better performance without Steam GUI overhead. 

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

51 minutes ago, moggel said:

If I indeed have a connectivity issue, shouldn't that also affect it when I turn ON Varjo's OpenVR option?

I’m not sure how to answer that as I’ve never had that warning. Best check with Varjo support themselves. 

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Link to comment
Share on other sites

33 minutes ago, Supmua said:

Don you can also run MSFS with OpenXR via SteamVR but Varjo’s OpenXR is supposed to offer slightly better performance without Steam GUI overhead. 

Yes it does whilst I do not fly it very much I have already tried the Open XR option for MSFS2020 and it does well.

Question for ya - have you tried Varjo Base vsync on and locked to 30 fps? I know you tried 45 fps but curious if you had tried 30 fps.
I have been doing the Apache weapons range instant action in Persian Gulf and it seems to do fairly well with fps locked to 30. Can't say if I am imagining it but seems like I may be losing a little image clarity off in the distance but gaining good smoothness when flying low. 

Going to try the Hornet off the Supercarrier in the Persian Gulf and see how it does and looks with fps locked to 30 in Varjo Base.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...