Supmua

Try playing with analytic window/performance analysis in VB, and play with different modes (vsync on, vsync off, 45 fps, etc.). See if that helps. OpenXR mode is usually pretty smooth for me. For OpenVR mode I typically need to lock framerate to 45 to get very smooth gameplay. Remember the Aero doesn’t have motion smoothing yet so take that into account if you are used to motion smoothing with other headsets.

The autoexec.cfg can be found here C:\Users\yourname\Saved Games\DCS.openbeta\Config add this (command) to your autoexec.cfg and save force_cross_eye_recovery_tool = true If you have a decent PC you definitely should not get 15-20 fps which is way too low. Reduce Steam per-app resolution for DCS to around 3100-3200 horizontal pixels. The Aero is a high res headset so supersampling in SteamVR is a no no and you want to downsample instead if anything. Also try the VR preset in DCS setting first. Once you get good fps you can increase the DCS graphics settings as needed. If you don’t want to do any of the above then go OpenXR route, just copy the contents from the zip that I posted in that thread into the folder that houses DCS.exe then run DCS from the SteamVR shortcut you made to use OpenXR mode which doesn’t need crosseye correction. You’ll also need to bind a button for VR recenter and use this in the game.

With later versions of OpenComposite OpenXR you no longer need to do crosseye correction. I can’t tell you anything about the stable DCS version because I always use the beta ones.

Your PC specs are high-end and should be able to get pretty smooth gameplay in DCS at that rendering resolution.

This means you are using Varjo's OpenVR instead of Steam's OpenVR which isn't working correctly. Currently, DCS needs to be forced to run SteamVR for normal operation so instead of running it directly from the DCS app you need to create a shortcut and add --force_steam_VR command to the exe file and always use that to run DCS. This is all the in guide thread which is recommended. Varjo Aero: General guide for new owners And you're not done there, there's also a step to correct crosseye also. Don't expect plug and play with DCS at current state. It's been months and I don't understand why this problem still hasn't been corrected by Varjo or ED devs. This is a huge turn off for new Aero owners.

Double cursor or warping issue? Check the Varjo's general guide thread, it's a bit of reading but will give you a better understanding of the current shortcomings of the headset and DCS and how to get around them.

If you're running SteamVR, either bring up the headset's GPU frametime visualization from Steam's developer menu, or use fpsVR to bring up CPU and GPU frametime window. This way you can see what happens to your system when you lose tracking. If there are no spikes from CPU and GPU graphs then SteamVR tracking may be the culprit. If there are spikes on the graph then it might be your PC itself, either background processes stealing power or throttling issue. With OpenXR it might be tougher to assess because I don't believe there's graphing option, but you can look at real-time changes in frametime numbers from OpenXR Toolkit/Performance/Advanced setting. What kind of CPU and GPU do you have, and what is your rendering resolution?

Yeah. Unless you can maintain the same fps as the screen refresh rate you’ll never get perfect images. For now don’t go crazy on the head movements when you fly and just look left right up down when you have to. I don’t really lock fps if I play in OpexXR mode, the frame pacing is better than SteamVR. I do get better images in SteamVR though but mostly because of Reshade not the api itself.

Yeah I’d be interested in getting a second link box as a backup.

Glad to hear that. I had to RMA my HMD way back then but nobody was really doing this so my replacement HMD came within a few days via overnight shipment from their US office. Now people are waiting weeks for their replacement headset.

Is it the real SteamVR tracking issue or PC switching back to an opened window on desktop from DCS app. If you also lose HOTAS control then it’s the latter, and DCS is known to do this. If it’s the latter this can be prevented by ALT-ENT in the main menu after you run DCS, or disable full screen mode in the setting. Closing all the windows on your desktop prior to running DCS may also help prevent this.

Use VR recenter command/button to recenter. Locking fps is done via Performance analysis window in VB, click on the bottom left icon to bring up the toolbar then click on the corresponding icon and choose 45 fps from drop down menu. Now doing this for general VR use may not be a good thing because you will get motion blur when moving your head around quickly due to 45 fps lock on a 90Hz screen. WMR dev tool is for WMR headsets only and not for the Aero which is a SteamVR headset.

I just don't get the splitting images with my setup and I play regularly although mostly Harrier and Apache these days. The cockpit can exhibit slight motion blur (because no motion smoothing) if you move your body side to side quickly on an x axis, but I don't really do that when I roll. Static capture of those parameters won't help much because that only shows one instant of who knows what, and how do other people know it correlates with whatever you're doing at that time. Try using OpenXR toolkit with Advanced overlay to display CPU and GPU frametime numbers from within DCS if you are using OpenXR. Or use fpsVR to do the same thing if you're using Steam's OpenVR mode. Then capture a video while doing the roll then we can see exactly what happens while checking out those numbers in real-time.

Yeah lock it at 45 fps, and it's fairly smooth. Not silky 90 fps smooth but it is unrealistic to expect that kind of fps with a high-res headset. Some DCS maps or missions are also CPU limited so even if I have a GPU that is twice as fast as the current one it still won't achieve 90 fps. Motion smoothing isn't a perfect answer either because you will still see double artifacts with very fast moving objects as image interpolation is never perfect. So, blurry fast moving objects or double images...take your pick. I'd say blurry is more realistic to me, because that's what you see in real life when looking to the side in a fast moving vehicle. I've completed a few campaign DLCs with the Aero and frankly would play everything on the Aero over other headsets with motion smoothing, everytime. The clarity and image quality alone is quite worth it. Not everything is rosy with the Aero, though. It's got quite a few shortcomings.

Didn’t make any diff to me. My IPD is 69 and I pretty much tried everything from 65-71 and chromatic aberration was still too prominent. On the other hand, I have near zero CA with 3.5.1. Now this could just be specific to my vision but there are quite a few owners from discord who also share the same opinion. The downgrade in image quality is quite stark when doing back to back comparison using the headset as a regular monitor for web browsing.

I've been switching between VB 3.5.1 and 3.6.1 and it's crazy how much sharper DCS appears with the 3.5.1. After flying with 3.6.1 for the past few days, going back to 3.5.1 again with the old distortion profile completely blew me away. At 3268x2800 pixels the image on DCS is crazy sharp with the older software, especially after manually setting crosseye correction tool (I increased R_out and L_out to 1.451 each and this basically upped the clarity further by quite a bit). The shimmering is also much better than the new version, probably due to next to nothing chromatic aberration. The clarity is so good that those tiny numbers on the small stopwatch dial to the left of the Harrier's cockpit is crystal clear, even just by glancing left and down. YMMV, but with the 3.6.1 software I feel like my astigmatism and myopia which should've been corrected with lens inserts had come back and hit me twice as hard; and this is all resolved by going back to the 3.5.1 software. This is with Steam's OpenVR mode testing, but the experience should be similar with OpenXR at least in my case.

Resolution increase alone is just a parameter for image quality. I don’t see the point of going beyond 4100 pixels or high PD when performance already suffers (personally use ~3200 to keep fps >45). There’re other things you can do to improve image quality. For example, exposure reduction to minimize shimmering, color correction to fix yellow tint, gamma change to reduce ground washout, sharpening to increase ground and distant detail, etc. No idea on the crosseye correction setting beyond the GUI range besides lua editing manually. I now seem to have issue with blurry texts and chromatic aberration with VB 3.6.1. This isn’t noticeable in DCS but pretty significant with web browsing especially with white texts on dark background, suffices to say that web browsing is no longer enjoyable on the Aero. Switching back to 3.5.1 with the old distortion profile seems to fix this.

I’m surprised you got PD other than 1.0 to work with OpenXR, the last time I tried other PD setting wouldn’t run but that was a few months ago. Anyway, another way to get shaper image without using DCS PD is to set the Aero at Highest setting (4100+ horizontal pixels at 100%) and leave PD at 1.0.

Sorry to hear that, Don, kind of unexpected. I hope it’s the linkbox or cable iissue rather than the screen as the latter would be a pain to replace considering a lot of people are having issues with dead pixels and blurriness. My Aero from the same batch is still ok *finger crossed*..

I lowered mine to 80%. Too dim is no good either, you loose smooth color transition and gradient in the dark area especially when watching movies. At this setting the overall picture is still a bit dim compared to my OLED TV setup when doing direct comparison.

I flew F16 Marianas Freeflight in SteamVR mode and it was fairly smooth, even though the framerate was mostly below 45 fps. There is motion blur on the ground with flyby which is better than juddering imo, it seems frame pacing has improved and is comparable to OpenXR mode now. This is quite different from my past experiences with the Aero and SteamVR.

Check out the Varjo guide in the other thread, only a short read and might save hours of uninstalling and reinstalling.

Great. OpenCompsite is known to be quite finicky with other preexisting DCS mods so that must’ve been the issue.

On my PC it’s pretty much drag and drop the dll file to switch to OpenXR. I even have Reshade 5 installed which doesn’t cause any issue with OpenXR. It’s strange that you are getting error but of course we do not have the same setup. I’ve also been switching back and forth between OpenVR and OpenXR without any error.

Does Steam OpenVR mode work for you? In order to start this you have to do DCS repair to restore the old openvr_api.dll first (remember the modified dll file is for OpenComposite OpenXR only and will cause error with OpenVR mode). There shouldn’t be any error related to OpenXR as you won’t be using it.