Supmua

Check the frametimes with OpenXR toolkit using detailed fps option. This will tell you whether it is CPU vs GPU bound (numbers are displayed in microsec rather than typical milliseconds), then you can branch out to check RAM vs VRAM usage etc. I’ve seen RAM use as high as 31.9 GB and VRAM up to 21 GB with my setup.

If you turn on detailed fps analysis option you can check frametimes as well as latency on both GPU and VPU. Foveated rendering I find strangely reports lower fps numbers than expected when compared with respective frametime numbers, which makes me think that it’s still not working correctly.

Pretty much stick with the settings that work for you. I opt for higher res (Very High on Varjo app, which is 3.6K horizontal pixels per eye vs 3.1K on default setting) because it looks much better even though there's some framerate issue in densely populated area. V-sync setting is no good at this res because fps suffers. In MP I can't maintain 45 fps but I'm ok with that.

The Aero only has eye tracking as it doesn’t have external cameras. I suppose you could buy the leap motion universal add-on to make it work like the XR or VR3 versions if that’s what you want. If you already have that add on then it shouldn’t matter what headset you use.

No it won’t change rendering resolution so it will default at 100%. Unlike WMR headsets which allows res change via WMR OpenXR tool, we can only change res via Varjo app (only 6 settings as far as I recall). You can use NIS or FSR option for res reduction plus upscaling back to 100% from the toolkit but that’s not quite the same as the conventional method and the results imo don’t look good on the Aero. These upscaling methods have performance advantage but sacrifice visual quality. The key advantage of OpenXR for me is that it allows me to use 100% res with decent fps, and this isn’t possible with OpenVR with my current setup. DCS or any VR apps with 100% res at higher setting on the Aero is a really nice visual treat. SkyrimVR, for example, is mind blowing.

You don’t actually need the Toolkit for OpenXR, it’s for further tinkering but offers very useful features such as frametime analysis, upscaling, image processing (contrast, saturation, etc.), FOV setting, foveated rendering which is essential for me to get good fps in MSFS BUT isn’t working right at present with DCS. it helps me figure out that by simply reducing texture to medium I can maintain stable 45 fps at the airport in Syria Apache hotstart instant action. I can even squeeze out better GPU frametime by manipulating forest settings.

No issue with the headset here, and I’ve played a lot daily since the Apache was released.

Don, try Higher setting on the Aero. It's pretty much 4KTV quality.

Do you have Oculus software installed by any chance? That error is unusual, I've seen OpenXR error with this but not OpenComposite one.

Yeah too bad it's not working out. Not really sure about that error. Oh....there's incompat with EVGA's Precision X1 software, it's on Discord.

When in doubt reboot first and try again. It can't be that bad. If it doesn't work just delete the files under red circle and do a repair to restore OpenVR_api.dll. Make sure Varjo's OpenXR is still on and not being overridden by SteamVR's OpenXR.

Yeah you need Jabbah's Opencomp ACC which is per app, as well as Mbucchia's OpenXR Toolkit which is universal install. I've never seen that error though, unusual. Make sure there's no customized stuff in that /bin folder.

Did you install OpenXR Toolkit as well? You need both, make sure to use the latest versions. NVM since you have the companion app which implies that you have the toolkit installed.

No need. It doesn't care whether SteamVR is on or not, but you will still need to force DCS to run via SteamVR since the Opencomposite wrapper relies on intercepting that. I typically have Steam on since it is my primary chat app with friends and I also use it for voice comm.

Try turning off OpenVR on the Varjo's app and just leave OpenXR on.

Don, just like previously you still have to force SteamVR mode with the exe command, but the wrapper will bypass that and switch to OpenXR instead.

Just realized you’re using 1.0.5 already. I’m still using version 1.0.4 didn’t realize there’s already a new one.

Sounds like a neat way to do it. Hopefully it works well in VR, I have R eye only IHADDS so the whole thing is shifted a bit off center to the right including the point of impact. Right now I just approach the target and use the rudder to line it up, horizontally it works well but vertical accuracy has been a toss up even with auto setting. Edit: tested it recently. Works pretty well with diving attack, but I have to focus on the right circular edge of the boresight alignment scope rather than the white line as vertical aiming point. This is with R eye IHADDS in VR and my custom cockpit view which is slighter higher and further back than default, YMMV. This is more accurate than trying to spam rudder input at low speed which can sometimes cause you to spin around if the maneuver is too aggressive.

I'd practice hovering, once you're comfortable with that you can pretty much land in any position. Practicing approach prior to hovering stop is also important. I find that it's easier for me to approach with nose-tail trim, but once you're comfortable with hovering stop it doesn't matter that much. As frostycab said when you land from hovering ground effect at 10ft and lower will push your aircraft upward and this needs extra nudge on the collective to counter that, if you land at higher speed ~30 you might not experience this. Don't let FPM drop too much or you'll lose control, try to decend slowly within a few hundred FPM. When you make corrections with the stick just nudge and let off and repeat, don’t keep continuous pressure on the stick. Same thing with rudder, this can help stabilize the aircraft quickly. Setting on your gear is also important, took me a while to find comfortable spring tensions/curves/deadzones on my rudder and joystick. I find that trimming too much will mess me up, so once I hover I don't trim. This guy has some nice tutorials on the Apache. I'm definitely not at his level in terms of smoothness but I'm getting there. DCS World | AH-64D | Hovering Practice Part 2 | Tire Box | Turns Around a Tire - YouTube

If you’re using Reshade 5, it’s got a separate runtime in VR mode. You have to enable it from VR overlay screen using VR controller (SteamVR in my case), find Reshade and click on it and it will display setting window (similar to fpsVR if you’ve ever used it)—mouse/keyboard input is only for nonVR (2D) mode.

Very nice!

Had this engine 2 issue in MP tonight also, I was playing CP/G so not sure if it was DCS or player's error but my friend was able to get it working eventually.

For the people who are interested, all it takes is dragging the files from the zip to the /bin folder. If you don’t like it delete those files and run DCS repair to restore the old OpenVR_api.dll. Installation takes a few seconds, and removal process is almost as easy. This basically allows me to swap back and forth between Steam and OpenXR quickly when I did the comparison tests. Then you’ll understand why people are raving about this in both MSFS and DCS communities. The ability to run your headset display at 100% resolution with decent framerate is a big deal especially if you have a high end setup and want to take full advantage of what your gear has to offer.

Whatever it is, I no longer need to have that visualizer on now that we have trim reset.