Gordy

ah, I was about to say - I'm running fine on my aero, but I am using the mbucchia wrapper as well

@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.

agreed - I get double cursors with the native openxr support, and performance around 71+ fps. The same configuration with the drop-in .dll replacement that I've been using for the last year has me at 84-90 fps, no double cursor. So I'd stick with the drop-in .dll and openxr for now.

ah, yes, thank you. With OXRTK disabled, the native openxr works, but with the double cursor, as you say. openxr explorer shows both the stereo and quad view configurations advertised, so I guess that's what DCS is responding to... <shrug>. Maybe it's picking the first view, in alphabetical order, and we're just unlucky that it's the wrong one: XR_VIEW_CONFIGURATION_TYPE_PRIMARY_QUAD_VARJO XR_VIEW_CONFIGURATION_TYPE_PRIMARY_STEREO

The native without-steamvr support isn't working with my aero, though... I can see on my monitor that I get into the main menu/lobby, but my aero is just black. For both openxr and openvr. openvr with steamvr works, as before. openxr with the replacement .dll works, as before. interested to hear if anyone else is having success with the native openxr support

You should get even better performance in OpenXR

yeah seems okay to me now too, after backing out and re-applying the patch. not sure what happened the first time

Today's DCS hotfix seems to have reintroduced the lateral stutter that the last Varjo Base updated fixed.

where is the varjo discord, btw? I can't find it

yes, in DCS with OpenXR

confirmed significantly improved. I'm getting 80-90 fps in single player F18 caucasus free flight instant action, at "Very high" resolution... also getting that at "highest" (4148x3556), if I leave terrain object shadows off and view distance to "ultra". If I turn terrain object shadows to default and visibility range to "extreme", my frames range from 68-85 or so.

New version of Varjo Base released; waiting for download/install now Varjo Base, release version 3.7.2 November 8, 2022 This release includes improvements and bug fixes to existing features. Fixed an issue that caused image stuttering when using NVIDIA GeForce RTX 4090 graphics card. Fixed an issue that caused a horizontal line artifact in the video pass-through image when the application was using eye reprojection. (XR-3) Varjo Reality Cloud: Fixed an issue where fps (frames per second) was incorrectly displayed in the Remote application FPS graph in Analytics window under Performance tools. Improvements to the technical details given in the error messages in the event of a failed server connection.

I'm getting comparable performance after the update, on my 3090. But I have tons of stuff turned off to push my framerate up already. I *did* notice some wonky shadows on the bunker hangars ... like the shadow was on top of the bunker, instead of behind it

I use three of these, which are driven just by USB. - they're a little bit bigger than the MFD button box, but they still work great. https://www.amazon.com/gp/product/B003LS95SG Pair with these stands, which are nice and solid, if you're just putting them on your desk. https://www.amazon.com/gp/product/B07633JHLX I think you *can* add a second video card, just know that all of the work will be done by one of your two cards in DCS - make sure it's the better card. (I tried it).

I note this all the time when taxiing the F-16; the heat blur effect from other aircraft far away from me blurs my HUD. Not sure if it's a general problem or an F-16 problem Heat Blur graphics setting configured as "High". Observed on version 2.7.17.29140 Nvidia 3090 card

Someone pointed out to me that you can spot distant aircraft more easily in lower resolution... so I tried stepping down from the highest (39 ppd) to the default ("high", 35 PPD) setting, and am annoyed that, indeed, I can spot distant aircraft more easily. I think it's because you'll always see at least a pixel, and the pixels you'll see are now larger. Anyway... the terrain hasn't suffered much, in part because the textures are coarse enough when you get close to them that the high res doesn't make much difference anyway. The tradeoffs include that it is now harder to spot *ground* units, particularly infantry, some extra jaggies, and a little extra shimmer. But the upside is better spotting of aircraft, and my fps went from 30-50 to 40-70. If you're exclusively doing air-to-air or targeting the ground via a TGP, the lower resolution and higher fps are definitely 'better'.

Earlier today, everything seemed to be working okay on the buddyspike blue flag caucasus modern server; I fired ATGMs, then 30mm cannon, then ATGMs again, no problems. Linking related post, don't know if the linked post issue was already resolved.

I'm seeing similar behavior on a server other than the Enigma server. For quite awhile (even before the latest patch update), petrovich will not fire ATGMs after the first couple. There's another thread that suggests this can break if you fire ATGMs, then switch to another weapon (rockets, 30 cal) and then back, but I don't know that's related. I can select targets, command to fire, see "Fire!" displayed in the messages, but the missiles never launch. In the past I assumed it was because I'd taken damage that prevented firing, but last night it happened when I was taking no return fire at all, but had switched from ATGM -> gun pods -> 30 cal -> ATGM. I experienced this on the Buddyspike Blue Flag Caucasus modern server. I can dig out the track file, but it's... not short.

From working with Varjo on some things - Varjo base will automatically fire up the SteamVR bits it needs for the base stations to perform head tracking; Steam VR does not need to be running when you launch an application, regardless of whether you're running OpenVR or OpenXR

I wanted to second the recommendation for using corrective lens inserts with the aero... I have been flying with my glasses on, and after switching to the inserts a couple days ago, everything is sharper and the sweet spot is much larger, I think because my eyes are closer to the headset lenses. Also, a lot of my chromatic aberration has gone away. If you're flying with your glasses on, this will probably make a noticeable difference.

@dartagnan - hit the "recenter VR headset" control in DCS. You'll find it under the "UI Layer", not a particular aircraft. I have it mapped to my HOTAS, and use it constantly.

@BIGNEWY, any chance of getting the ranges offered in the tool sliders expanded? My values default to around 0.7 and 1.57, but as soon as I touch the sliders to adjust, they jump to a range limited to between 1.0 and 1.5. So I can't actually make any fine adjustments to my baseline without manually editing the saved .lua file and restarting repeatedly. Using a Varjo Aero, fwiw.

Thanks ... I was already running at the highest setting on the aero, and had told OpenXR to not override the resolution... but it's good to verify that it's running at at least the native resolution. After playing with this for awhile, I think what's really happening is that with the PD cranked up, I'm getting the cross-eye issue - both eyes are required to look more toward the middle than straight ahead. The magic I'm seeing is that once my eyes find that point, they're getting properly synced on the image, and it's crystal clear, all the objects are rock solid. They way I've been flying, I always have that sort of ghost and shimmer, as if one eye is polarized differently than the other, or you have the HMD displayed in one and not the other - the image in each eye isn't exactly the same, so a lot of the world looks kind of ethereal, and I had just chalked it up to an artifact of VR in general. now... I can't dial this in with the cross-eye correction tool, because the sliders only let me move between values of 1.0 and 1.5, and the correct values are always well outside of that (the "reset" starts at 0.7 and 1.57 for most values). As soon as I touch the manual slider, it jumps to a very-wrong value. I can manually edit the .lua file, but that's...crazy to edit, reboot, test, edit reboot, test... I've already tried swapping top/bottom values and deleting my existing .lua file, those are as good as they're going to get. The aspect ratio is also clearly wrong; if I turn my head sideways, I can see the image compress vertically. I don't have that problem with PD set to 1.0. I can't start the VR session at all with PD set to 0.5. I tried switching to OpenVR, and I don't have these problems there, but I also don't see a dramatically improved image, and it steals about 5-10 fps from me. So I think I need to work out how to get my cross-eyedness dialed in... anyone know how to get those sliders to work on a wider range?

Varjo support was quite good/responsive when I was working with them on an issue. My issue was the usb connect was unreliable; at this point I've accepted that I need to disconnect/reconnnect my headset several times before I get a solid signal. A common failure mode (for me) is what you describe - fans spin up, lenses adjust, green LED, varjo base looks happy - but gray image in the headset. I thought my headset had failed, because several attempts to restart it all failed and got me a pulsing red LED. After working on it for awhile, disconnecting and reconnecting the headset up to a dozen or so times gets me back to operating fully, and then it's stable until I shut the system down, generally for several weeks. They sent me a replacement, but it behaved the same, and they couldn't reproduce the problem when I shipped the headset back to them, so I suspect it's an idiosyncracy of my hardware/motherboard/whatever. Point is, try disconnecting/reconnecting a dozen times - unplug the USB-C cable between the headset and the link box - it might surprise you. And if you end up giving them some additional data that helps address this behavior, that'd be great. 8-10 misses before it succeeds is not unusual for me, but it always hits within about ten minutes. Also, if yours is now behaving like mine, and your replacement link box fixes it, I'm gonna want to know that too