Search the Community

VR performance in the OH-85D is unacceptable. I have pretty much every module in DCS and play all in VR with almost always 72 FPS in both SP and MP. As soon as the rotor starts spinning FPS goes from a stable 72 to 62-60 with very high frametimes (Please see attached CapeframeX with both frametime and FPS) Explanation of capeframeX: I am looking straight forward during the full 3 min Empty mission on Syria.(no other assets) Using autostart first stage in framtime is cold and dark. Second stage is when I press autostart. Third stage is when the rotor starts spinning. Worth noting: If I center my view in VR with my head outside of the aircraft I have a stable 72 fps. MMS is not on. I have also attached my track file + my options. Hardware: Quest 3 AMD 6800XT AMD 5800X3D 32GB RAM M.2 SSD LastMissionTrack.trk options.lua

Since version 2.9 the valve index controllers have been broken in game and no longer have the hands to allow for the interaction of, menus and aircraft. I have created a video attached that demonstrates this issue and compares 2.8 controllers vs 2.9. Attached also is the log of both versions of the game. This issue has been going on for months I'm hoping this gets fixed soon. broken vr controls.mp4 dcs version 2.8.log dcs version 2.9.log

Ever since 2.9.8.1107 my DCS install has been CTDing after flying for ~ 15 minutes. This is on an AMD 5900x and RTX 3090Ti. and 32gig RAM using an Aero. Never had that happen before. This occurs consistently on simple dogfight missions. My Nvidia drivers are up to date.

After the last update on Open Beta and Stable version in the main menu hangar, when using VR (Oculus Rift S), the MIG29 is missing of Radome, Canopy and Nose Wheel. Help

Dopo aver aggiornato DCS, sia Open Beta che Stable, nell'hangar in cui ci si trova come main menu quando si usa la VR, al MIG29 mancano Radome, Canopy e Ruotino. Capita anche ad altri di voi?

Hi, On the latest open beta I am having an issue where my cursor disappears in VR and locks onto clickable items. The cursor appears occasionally before vanishing again. This happened last updcs.logdate in the Hind only, now appears to be in all aircraft. Cannot attach log as it is too large. Using WMR/Steamvr

Hey, I've recently got a new machine and using my existing headset (reverb G2) I've been hitting a really frustrating issue with VR display stutters uncontrollably. The game will often run perfectly fine with a good solid FPS, everything working normally and then *something* will happen and the VR view will stutter uncontrollably around the head position. I can still play (in a way) as the stutter seems to be around my current head position. Its as if the game gets stuck in a loop trying to find my head position and causes it to act erratically. I've also noticed that the Steam VR button on my controller no longer works once my game gets in this state. The ingame FPS shows no change and my mirrored monitor showing the game normally. Once the session has ended the stutter goes away and everything is back to normal. The *something* I've not been able to isolate. Sometimes it happens after a certain amount of time (10 mins or more) sometimes its when something happens in game (ie, in the AH64, when I get a rotor warning) or when I use the F10 map. It happened in both single player & multiplayer but is never consistent, sometimes I can play entire sessions (1hr +) without any issue and other times it can occur right away and derail my entire session. I've tried the usual suspects, HAGs, changing OpenXR runtime (from WMR to steam & back again), got updates, overclocked, not over clocked, lower graphics settings, higher graphics settings but nothing seems to have resolved it 100% as I can never be sure if or when it occurs. Any ideas? Specs: Intel Core i9 12900KF GeForce RTX 3080 OC 32GB RAM DDR4 3200MHz M2 SSD Windows 11 HP Reverb G2

Hey all, I tried browsing the forums for a few minutes and could find similar issues but not identical to mine though I may have just missed it. I upgraded from the Odyssey+ to the Reverb G2 about 2 months ago. Game runs great in VR, both in the O+ and Reverb G2, only issues is when I go back to spectator online. The game will stutter near to the point that it's unplayable, but it seems to only happen when I return to spectators or respawn aircraft, otherwise it runs near flawlessly for me. If I look in one direction it runs fine but as soon as I adjust my head position to view instruments post respawn, or look around, the stuttering resumes. I never had that issue with the O+, so it seems to be G2 specific for me, I have tried adjusting and changing various graphical settings, VR settings, etc. with the same results. I am unable to pin down exactly what is causing this issue for me. If I return to the main menu the stuttering stops, as soon as I go back into multiplayer, it resumes. If I restart DCS it runs great until I respawn then it starts all over again. I'm kind of at a loss as to what is causing the stuttering to occur as it only occurs under those conditions, trying to find out if anyone else has had the same issue and if so, if they have found a work around.

Every time today when I switch from DCS VR to desktop via SteamVR the controls stop working when I return to the game. Only the mouse, throttle axis and joystick axis work but most buttons and keyboard buttons do not work. I am forced to restart DCS each time. This sucks because I have Chuck's Guides open on a desktop screen for problems/references.

There have been many reports of unexplained prolonged FPS drops in VR. I have provided what I hope is a consistent repro along with a GPU/perf capture later on below, but common symptoms of this issue seem to include: Happens randomly, but common triggers seem to be actions that cause temporary performance blips (that then turn into sustained FPS drops) FPS goes from something stable and normal (e.g. 30/45fps) to significantly lower and unplayable (e.g. 15-25fps) FPS drop lasts for many minutes, sometimes requiring exiting the game to recover VR-specific Alt-tabbing away from and back to DCS sometimes resolves the issue Returning to the main menu still exhibits abnormally low FPS I think those last three points are important, as they point to a software bug, not a hardware bottleneck. FPS would return to normal at the main menu, and alt-tabbing wouldn't fix the issue, if this were simply a problem with users' machines being incapable of sustaining adequate framerates. Furthermore, the issue seems to be VR-specific, pointing to a VR-specific bug as opposed to a hardware capacity issue. Here's a collection of forum posts that I believe exhibit this issue (there are more): The most consistent repro that I can find is to: Load into main menu Observe 90fps Load into Cold Start instant action on Marianas map in F/A-18C sim (this is a good starting point, since you're on a carrier, and can see the island in the distance) Observe stable 45fps Slowly turn your head to the left, until you're looking behind your left shoulder Slowly turn your head to face back forward, then right, until you're looking behind your right shoulder this time Turn your head back to face forward Observe ~14 fps Quit to main menu Observe ~25 fps This is on current stable Steam DCS (also on beta), Windows 10, a stock RTX 3080 (driver 512.95, doesn't seem to matter), stock Ryzen 5950x, HP Reverb G2, WMR 2000.21051.1282.0 (version doesn't seem to matter), OpenXR 110.2204.7007 (also reproduces on SteamVR), 100% render scale (3168x3096 pixels per eye), motion reprojection always on, and the following in-game settings: 2022-06-02 08:30:19.529 INFO APP: options.graphics = { ['messagesFontScale'] = 1; ['forestDetailsFactor'] = 0.75; ['rainDroplets'] = true; ['LensEffects'] = 0; ['box_mouse_cursor'] = true; ['anisotropy'] = 4; ['water'] = 1; ['motionBlur'] = 0; ['outputGamma'] = 2; ['aspect'] = 1.6666666666667; ['lights'] = 2; ['shadows'] = 4; ['MSAA'] = 1; ['SSAA'] = 0; ['civTraffic'] = ''; ['clutterMaxDistance'] = 0; ['cockpitGI'] = 0; ['terrainTextures'] = 'max'; ['multiMonitorSetup'] = '1camera'; ['shadowTree'] = false; ['chimneySmokeDensity'] = 0; ['fullScreen'] = false; ['forestDistanceFactor'] = 0.75; ['useDeferredShading'] = 1; ['DOF'] = 0; ['clouds'] = 1; ['sceneryDetailsFactor'] = 1; ['width'] = 1280; ['flatTerrainShadows'] = 0; ['visibRange'] = 'Ultra'; ['textures'] = 2; ['SSLR'] = 0; ['effects'] = 3; ['SSAO'] = 0; ['secondaryShadows'] = 0; ['sync'] = false; ['scaleGui'] = 1; ['preloadRadius'] = 150000; ['height'] = 768; ['heatBlr'] = 0; ['terrainMapMFD'] = { ['distance'] = { ['mapLodDistance3'] = 200000; ['mapLodDistance2'] = 100000; ['mapLodDistance0'] = 25000; ['mapLodDistance1'] = 50000; }; }; }; This behavior doesn't really make sense. I'm sure that the act of looking right on the Marianas map is exceeding the VRAM on my 3080, causing a temporary blip as stuff has to be paged out of VRAM for it, but when I look back forward, everything should get paged back in automatically (at least on DX11) and return to normal. And indeed, in the captures below, there isn't any persistent VRAM paging going on that would explain the severe drop in FPS. Similarly, when returning to the main menu, instead of getting 90fps like I was before, I'm at 25fps, and nothing strenuous is going on (I haven't grabbed a capture of this yet as it's much more difficult to get a capture of due to needing to alt-tab to start the capture, and alt-tab typically clears the issue in the main menu); I took a GPUView capture of the issue on the Marianas map (happy to provide to private support), and it clearly shows some kind of problem with how DCS is scheduling it's main thread. In summary, it appears to be sleeping too long and doing nothing. This isn't a problem that requires advanced multithreading, DX12, better VRAM management, etc... It simply appears to be an issue with DCS waiting too long to start rendering the next time. Here is a capture of a normal, stable 30 fps for me after loading into Marianas (higher settings than I mentioned previously, but still a decent 30fps): What I've gathered from this is that: In VR, DCS has a thread started from WinXrRuntime.dll that runs at 90Hz (or whatever the refresh rate of your headset is) You can see the row for this in the bottom left (labeled WinXrRuntime.dll) The blue boxes are when this thread is running on a CPU core. You can see a total of 14 of them, because this capture window covers about 160 milliseconds, so at 90hz we'd expect about 14 occurrences in a 160 millisecond time period I believe this is due to xrWaitFrame (https://www.khronos.org/registry/OpenXR/specs/1.0/man/html/xrWaitFrame.html), which must be called by the application to synchronize frame submissions with my headset. So this thread is probably calling xrWaitFrame on a loop to do that, which is why it's running at 90Hz The DCS.exe thread is running at 30Hz, every 3rd time that the WinXrRuntime.dll thread is running The WinXrRuntime.dll thread is seemed to be used to (among other things) schedule the main DCS.exe thread to run (i.e. this is how DCS ensures it synchronizes its frame submissions with your VR headset) You can see the row for this a bit above WinXrRuntime.dll, labeled as DCS.exe Similarly, the blue boxes are when this thread is running on a CPU core, which aligns with every 3rd time that WinXrRuntime.dll runs In this capture, when the DCS.exe thread is signaled to run, it executes for about 16ms This isn't fast enough to run at 90Hz As noted above, it's running at every 3rd time that the WinXrRuntime.dll thread is running I.e. this is running at 30Hz, or 30fps. Which with motion reprojection, is perfectly stable and playable This could run at 45Hz, however my GPU wouldn't be able to keep up, so it would be a bottleneck and my FPS wouldn't improve. You can tell this from the Device Context and RTX 3080/Hardware Queue 3D rows, which show that the GPU is being kept busy ~85% of the time. The GPU work scheduled to the Device Context queue also takes about 28ms to drain, so it's limited to about 30fps, and there's no point to the DCS.exe thread running more often (at least, not for scheduling GPU work) In summary, the main DCS.exe thread is running at the ideal 30Hz for how my hardware is performing, and I'm getting a reasonably smooth 30fps with motion reprojection Now, let's compare this with a capture of an abnormal, unstable ~22fps for me, on the same Marianas map, after briefly turning to the right and then looking forward in the same exact direction (i.e. should be rendering the same stuff as earlier in the 30fps capture): There are a few notable differences from the earlier capture that was stable at 30fps: The WinXrRuntime.dll thread is still running at the expected 90Hz The DCS.exe thread is running at 22.5Hz, every 4th time that the WinXrRuntime.dll thread is running (instead of every 3rd) In this capture, when the DCS.exe thread is signaled to run, it executes for about 23ms This is higher than in the good capture (23ms vs. 16ms) As noted above, it's running at every 4th time that the WinXrRuntime.dll thread is running I.e. this is running at 22.5Hz, or 22.5fps. Even with motion reprojection, this isn't very playable (it also varies a lot and isn't stable) This could run at 30Hz, but for some reason it isn't. My GPU isn't a bottleneck. The GPU work queued to the Device Context is still taking 28ms to drain, which is the same as the good capture. The GPU is also only being kept busy about 60% of the time, and there's no reason that the DCS.exe thread couldn't run more often (at least, probably not) In summary, the main DCS.exe thread could be running at 30Hz, and my GPU would be able to keep up, but for some reason it isn't, resulting in a very poor framerate My CPU also certainly isn't a bottleneck. I don't have an explanation as to why each frame of the DCS.exe thread went from 16ms to 23ms, but that's still fast enough to run at 30fps. I also have plenty of spare cores to which the DCS.exe thread could be scheduled to and run during this, so that isn't a problem either: In summary, it should be evident from these captures that DCS is more than capable of running this at a stable 30fps here, but isn't due to what appears to be a bug with the main DCS.exe thread literally deciding to do nothing and wait (lazy thread!). There is no CPU/GPU bottleneck. DCS must have some way of throttling how frequently the main DCS.exe thread runs. If it ran as frequently as it could, then my GPU wouldn't be able to keep up. This is why it only runs at 30Hz instead of 45Hz in the first capture, because even though it could run at 45Hz, the GPU would fall behind. So it must be doing something intelligent to throttle how often it runs. It's my theory that these framerate drops in VR (consistent with the symptoms mentioned here) are due to a bug with how the DCS main thread is scheduled to run, that causes it to run less frequently than it should in certain scenarios, and thus may be a relatively simple fix and a huge stability boost to anyone experiencing this issue (including myself). I'm happy to provide more info. I also have logs available, but I'll note that they look the same whether or not the issue is occurring, so I don't believe they'll do much good. I also have some experience in this field and would be happy to sign an NDA and look into the issue myself, but I'm sure ED has people better suited to fixing this than me. If only they're able to reproduce and look into the issue, I'm sure a lot of VR customers would be very grateful, as this issue is extremely disruptive, to the point of making the game unplayable in VR without excessive hardware purchases (like a 3090) or turning settings down to very low levels and avoiding maps like Marianas or even MP entirely.

I am still using the MT "":\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR" do I need to be doing these things at this time? Is there a more current recommendation to start the game? Prior to the last update, I thought that I had the jittering under control via some some of the recommended settings, I haven't tweaked anything in quite awhile, and gameplay is really bad imo. If I look anywhere except thru the canopy it's just jittery and bad, I don't mean to sound negative but at what point does gameplay get better? I mean, heaven forbid.. looking down and using the mouse to lower/raise gear and your view is jittery and becomes off center etc. I can seem to find the 5 key with VR set on lol, to re-center. What gives with this latest update and what is the future of this game? I was excited to get involved but as time goes on, I'm wondering.. I have a decent rig, 5800x, 4080, 32gb ram.. HP G2 in VR, I play other stuff very very smooth but DCS is fun but quite a challenge anymore in VR.