wheelie

wheelie

The Varjo Base software has the option to enable OpenVR and disable OpenXR. I enable OpenVR Disable the OpenXR toolkit Start SteamVR and set Steam VR to be the runtime This allows me to run in SteamVR with 50% motion compensation and is excellent if you intend to record or stream DCS. I also lock it to 60fps. In the Varjo OpenXR config json file i change it from quad view InstanceExtensionsWrapper.dll to VarjoOpenXR.dll I then start DCS with the following shortcut: "S:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenVR

Mine appears to be back to normal now. I checked the NVidia settings and made the following changes. I also tested it using SteamVR/OpenVR as opposed to Varjo openxr with the InstanceExtensionsWrapper.dll. After seeing an improvement using SteamVR i set it back to using Varjo's OpenXR with OpenXR toolkit enabled. Seems to have rectified my stutters. I'm still seeing random drops in FPS but not to the point where it slows down the terrain. My frametime is around 10/11ms consistently. My DCS setttings are below. Not sure if this is an actual fix for everyone but it certainly is for me. Hope this helps someone.

I'm seeing a similar performance degradation since the latest update. The FPS seems OK but there is a weird jitter as if something is being loaded or some loop in the code is happening. Its very, very noticeable in helicopters, Apache, HUEY, blackhawk and HIND. I don't know what it is and don't see the antifreeze message some are reporting in the dcs.log file. It feels like there is something looping in the background? I hope the track files added in this discussion help ED to identify and rectify as its not a good experience at the moment. i9 9900k all cores at 5GHZ 64gb Ram 4090 GPU OS on m.2 DCS on its own m.2 Page file on separate m.2 All drivers still the same my end and no OS updates added.

yep same here

I updated to NVidia driver 551.46, cleared the DX runtime cache and usual FXO and Metashaders folders and its definately smoother for me. This is with the Varjo Aero and RTX4090 so even i can notice a difference.

A year ago i ran a 3090 with 24gb VRAM. Syria missions (multiplayer) and liberation missions would take up 21/23gb of the VRAM, i was a tad shocked to say the least and always wondered how other users would handle this with the plethora of cards out there. I've since switched to a 4090 and again i see high utilisation of VRAM which is kind of what i would expect. So a year later i still see the same VRAM behaviour i had seen before MT was a thing. Maybe we're seeing more caching in VRAM for the new eye candy, night lights, shadows, pre-rendered content, 4k textures? I don't know but the VRAM usage for me is the same as it's always been however for cards with 8, 12 and 16gb ram i suspect this may have caused some unexpected issues that could result in shared memory being used which would obviously be far, far slower than the GDDR6 on a lot of GPU's. Perhaps the additional shadow options have added to this? I don't know but i see the VRAM as high as it's always been on my system. A good troubleshooting exercise would be to have the same mission replay and enable each shadow/texture option to see what, if any increase this causes and and what point it goes above the threshold of a GPU's available VRAM.

Thanks for the update mate much appreciated, so with the VB software rolled back you can use the OpenXRTK within DCS? i.e. NO DFR enabled?

Are you playing with OpenXR enabled and no DFR? This seems to be the main issue, since the latest release we cannot use OpenXR toolkit with the wrapper as we could in 41066.1. Matt has released the updated version of DFR which allows us to once again use OpenXRTK within DCS but turbo mode crashes DCS and the anti-aliasing is broken somehow, e.g when i look back at the sidewinders on the wingtips they are pixelated.

@BIGNEWY Scott can we get some information or clarification as to what changed in the last DCS patch that is not detailed in the change log please? It appears something changed around VR that was not documented or detailed that specifically affects Varjo Aero headsets. Openbeta v41066.1 doesnt have the issue. Any clarification/details would be most appreciated.

Aha apologies chap didnt realise that would actually work, many thanks.

Ok so quick question for those that are saying its ok. Currently we cannot use OpenXR tooklit and Varjo Aero like we could previoiusly. So within DCS we now don't have the ability to open the XR toolkit menus and amend the VR config with the current MT openbeta. If your using DFR you already have OpenXR tooklit disabled and you won't see what we're referring to. Does anyone currently use the OpenXR Toolkit enabled with the Aero and are able to open the XR Toolkit menus within DCS MT openbeta?

Where are you getting the previous version of the beta 14066 install? Did you already have it locally? i'm at the point where i want to rollback.

Hyperthreading is on mate and works fine for me with an i9 9900k @5ghz all cores. The Vsync to FAST is a weird one but i think its more driver/nvidia related than specific to VR. Great when it stops tearing though, i had to disable vsync in DCS and set vsync to fast and have left it that way for about 18 months now. Glad you had a positive result with it.