Kahless_uk

Changing to HEVC from AV1 fixed it, now I just have to remember how the fly the thing!! Thanks folks

That's a point I didn't consider, I'll try that then BIGNEWY's suggestions

Has happened in SP too

Whenever I load up the AH-64 in VR, my VR headset (quest 3) will freeze after a few seconds while the game continues to run on the desktop (including still tracking my head movements) This doesn't seem to be a problem for other modules, just this one. I'm using Virtual desktop 1.33 which along with the pc and the headset have to be restarted to get out of this problem Oculus link (by cable) doesn't crash but looks terrible (and eventually degenerates even further with different areas of the display moving at different rates that requires a restart to fix) I'm including a trk file but I doubt it'll tell you anything as I'm just sat there in the apache for a few seconds. I've tried; Lowering texture settings, Increasing DLSS scaling, Deleting shaders within DCS, Deleting Nvidia shaders, Deleting Windows DX shaders, Reinstalling Virtual desktop (windows and quest), Running repair on DCS, Running SFC and DISM on windows. CAW-TRG-CAUC-20250122-165851.trk dcs.log DxDiag.txt

While I appreciate a genuine attempt to help, if turning rendering settings down fixed the problem I wouldn't be here complaining. To be fair 2.9.7 did have rendering issues however it was due to the main thread cutting into the render thread's cpu time, this isn't happening anymore it's just the main thread limiting everything by being slow and even with 2.9.7 turning down settings netted me 2 to 3 fps. 2.9.5 however had none of these problems 2.9.8 is an improvement over 2.9.7 without question (good job ED) in that the wild fluctuations in framerate are mostly gone it's just that the total output isn't great, I only want 60fps, not 120 or whatever and with 2.9.5 I got that with room to spare, now I get around 48 which is just within the bounds of VRR so it IS reasonably smooth just not great for headtracking

dcs.logDxDiag.txt After 2.9.6 I've had pretty bad performance from the CPU side, 2.9.8 has improved things in terms of the FPS being more stable, but it's still below par from 2.9.5

Side note, but possibly related, just sitting in the main menu without clicking anything and one CPU core is already at 100% and the next most loaded not far behind with the others doing nothing and a second screenie of CPU activity sitting still on the deck of the supercarrier in an F/A-18c on the syria map with the fps tanking

Single digit frames running that miz, looking at cpu usage shows 2 cores 100% the rest doing nothing dcs.log

One log as requested dcs.log

Getting similar problems since the last major patch and hotfix, essentially the multithreading isn't multithreading anymore. It seems to pick the core reported as the fastest (core 2 for me) and the core reported as next fastest (core 6 for me) and then just runs everything on the fastest core pinning it to 100% with the occasional drib and drab on the next fastest core while ignoring all the others. If I use affinity masking to disable the fastest core it just 100% s the second fastest core instead and so on down the line, performance is effectively ruined and the game reports itself cpu bound on the main thread and then the render thread intermittently dropping frames and stuttering like crazy with each swap between the two states. It's not just me either and AMD cpus without 3dvcache seem to be the common denominator among people I've spoken to