MoleUK

Any suggestions for fixes? Started happening here since I did a cleanup and repair of DCS. Didn't touch anything else, other than DCS graphics settings. Tried a windows and nvidia update since then, but no luck. It's a hard crash too, locks up the PC completely.

There's no way to get this to pass IC in 2.8 is there? Shame if so.

Yeah mine have been mute for a while.

Could definitely give it a shot. Reducing antisotropic filtering to 0x and clouds to high has let me hit 60 FPS again in some instances at least, but busy servers like ECW and Blue Flash seem to be harder to run in 2.8 than 2.7 atm regardless. Hopefully they find out what the conflict is, if it's more than just the shadows issue.

Hit ctrl + pause a couple times. On some keyboards it will be scroll lock instead of pause. Oof, hope that's not the case. I'm stuck with 8 gigs of vram on my 3070 for the forseeable future.

Other alterations/minutiae: Nvidia control panel: Pre-rendered frames 1, Vsync fast, texture filtering trilinear optimisation on, texture filtering quality high performance, negative LOD bias clamp, anisotropic sample optimisation on, power management prefer max performance, low latency ultra. Windows gaming mode off, HAGS off, re-sizeable BAR on, full screen optimisations on DCS.exe disabled. I lock all the oculus software from using the same CPU cores as DCS. All relevant processes set to high priority.

Per request, putting this in a separate thread. With 2.8 I've seen a significant performance degradation in VR. Even turning down various settings doesn't seem to offset this loss, and at a guess it appears to be CPU related. Specs: 5800X, 3070, 32 gigs 3200mhz. All on an NVME SSD. Quest 2, running at 120 hz. Running via oculus air link on the oculus runtime with ASW disabled. Settings: Textures medium, terrain textures low. Shadows medium, view distance far, secondary shadows off, MSAA 2x, global cockpit illumination off. Water was on high. Clouds were on ultra, terrain shadows were off, Antisotropic filtering was on 16x. Dropped all those to medium/high/off and put terrain shadows on flat to try and regain FPS unsuccessfully. I can point to one indicator of the new low FPS. The update ms time in the DCS FPS breakdown indicator has spiked. Included two screenshots. Same module, same server, same settings, minutes apart. Once that update time drops my FPS come back. Apologies if it's hard to make out, hard to screenshot VR in my current setup. If you can't quite make it out, in the first SS my simulation time is at 4.4ms, update at 5.2. Hitting around 60 FPS. 2nd SS, simulation time 6.2, update either 13.4 or 15.4. Gets down to 30 FPS. (edited) For reference, my FPS in 2.7 was mostly dictated by my simulation ms. Once it got up to around 10, I'd drop from 60 to 40 FPS. When it hovered around 5-7 I'd maintain 60. The update ms was always consistently around 6-7, so this is a big change in behavior. (edited)

I can at least point to one indicator of the new low FPS. The update ms time in the DCS FPS breakdown indicator has spiked. Included two screenshots. Same module, same server, same settings, minutes apart. Once that update time drops my FPS come back. Apologies if it's hard to make out, hard to screenshot VR in my current setup. If you can't quite make it out, in the first SS my simulation time is at 4.4ms, update at 5.2. Hitting around 60 FPS. 2nd SS, simulation time 6.2, update either 13.4 or 15.4. Gets down to 30 FPS. (edited) For reference, my FPS in 2.7 was mostly dictated by my simulation ms. Once it got up to around 10, I'd drop from 60 to 40 FPS. When it hovered around 5-7 I'd maintain 60. The update ms was always consistently around 6-7, so this is a big change in behavior. (edited)

Using the oculus runtime here. If I switch shadows from medium to off I can get back some of the FPS loss. But it's not consistent, something is spiking CPU. Simulation time goes to around 10ms+ and the FPS drops.

Didn't get much time in yet, but immediately noticed a decrease in FPS unfortunately. I noticed the simulation ms was much higher than it used to be at low/medium altitude. My FPS was much more fluid though, rather than cratering from 60 to 40 it was staying fluid inbetween instead of locking at 40 which felt a lot better. This was all in MP on a fairly busy server for context.

Afterburner is installed on my system, but I typically close it when running DCS and no OC is being applied to my GPU currently.

Are you running in VR by any chance?

HAGS is off. Re-sizeable BAR is on tho. Yep, I have to check every time I quit DCS atm. Not a huge issue as i'm in the habit of bringing up task manager before launch every time as well to set DCS to high CPU priority. Interesting you had a good experience with HAGS in VR tho, might have to try switching it on. You running in VR on the Q2 as well?

When this happens, set them to hold and HOLD down the fire button. It resets it to toggling fire on/off on both sides. Not ideal but it's a workaround.

Sure, as luck would had I just had one. dcs.log

Anyone find a workaround for this?

Yeah when I first started in the huey I went by the ball indicator, after a few weeks of that in VR I started getting serious back-ache problems lol. Now I know just to ignore it, which is unfortunate as it'd be nice to have an accurate indicator.

It has been a couple months since I've updated nvidia drivers, so could give it a shot. It's still happening. Not a huge issue as I've gotten in the habit of bringing up task-master after exiting to check if it's still running. I did remove the mods for a while but that didn't change anything. I mostly fly MP on Enigmas, so I'd guess that mission is on the larger size.

This isn't the problem. Sometimes tapping fire or cycling ROE will fix it, sometimes not.

And another dcs.log

Another one if it helps: dcs.log

Been happening since before I installed either of the mods.

This has been happening for a few weeks if not a few months now intermittently. It wouldn't bother me except the process is still eating the CPU time (seems to peg itself at 12 ish%, which i'm guessing is 100% of 1 core as when the game is running it will stay pegged at 25% using two cores fully. Managed to get a log after the last incident and get a few SS's. Launching in VR, using quit to desktop from in-game typically. dcs.log

That's actually interesting. One time I was flying the hip in VR with mirrors disabled, something glitched and I suddenly had the mirror displays hovering on both sides, without being attached to the airframe. Couldn't toggle them off again as they were supposed to be completely disabled. Makes me wonder if that's a wider problem, where switching them off sometimes leaves them rendering but invisible.

Did it not make the cut? Or just not listed in patch notes?