Tigh

That'll be my TrackIR. Looks like you've solved that so thank you! My windows is up to date, I ran the slow repair as well. Tried various settings in the same scenario including turning down clouds, turning off shadows, turning off DLSS, etc. with no noticeable change. Limiting to 90fps helps frame rate stability compared with 180 which is just a stuttery mess. One thread suggested it was MT causing issues so I tried ST. With frame locked at 180 the rates sit around 120-130 with only a small variance. With frames locked at 90 it is back to 2.8MT silky smooth. I'm loosing c. 1/3rd-1/2 of my frame rate running ST vs. MT but I can live with that if it gives me smooth performance. For my specific setup something has changed with 2.9 which has pretty much broken MT. Additional: @BIGNEWY found your mt.lau thread (sorry I didn't see it earlier, so many threads!). MUCH better. 2.9MT fps hovers around 140 with only a 15-20 frame variance, the very odd stutter in heavy urban areas. With DLSS on I'd say the frame rate is a little less stable but is giving me an extra 40 fps. Locking at 90fps in this configuration and it just sits at 90fps. Lets face it, 90fps in a flight sim is pretty amazing. I'd be interested if the team feels there's more refinement needed with DLSS as it is a relatively early iteration for DCS.

I'm getting closer and closer to rolling back. 2.8MT was lovely; really good, stable frame rates. I can just about get away with 2.9 but it's noticeably stuttery and it's starting to get annoying. dcs.log DxDiag.txt

It's shadows in 2.9. Locking your frames can help to an extent.

Rather than start a new thread..... Just finished the campaign. Really, really enjoyed it, great storyline with challenging missions (12 perhaps a bit too challenging ). Up there with the best of them. Thank you for all your work @ChillNG. Looking forward to climbing back in the F-18 for OCN.

I got to 75 and lived to fight another day.

Glad it's not just me. It seems to be an autogen issue and more specifically looking at the cockpit panel in an area of heavy autogen. As soon as you look away from the cockpit panel or go to an external view or fly off into the desert the issue resolves itself. I'm not sure if they've changed anything about autogen between 2.8 and 2.9 or whether it's to do with the new rendering. I have linked a video trying to illustrate what I'm seeing. Apologies for the lack of subtlety with the editing. https://www.dropbox.com/scl/fi/xop4fpas421yb1f4r1skv/FPS-Test.mp4?rlkey=xgr4oswq1nneq662sx8zz5fvh&dl=0 13700K 4090 Additional: Not an issue at night. Running smoothly at c.150fps in the same scenario at night. And more: which led me to think about turning shadows off. No more issues at all. It's shadows causing the problems.

Hi Glyn, That does help. Not having dropped many JSOWs before I watched them into the target while turning cold, in doing this I've presumably wondered out of the engagement zone as you describe. I'll know better for next time. Really enjoying the campaign so far, thank you for creating it.

I've read and understood the helpful tips about hitting the three hangars in mission 5 which I did successfully. Just setting up my coordinates for the next bit and I was told the I had "failed to complete task 2" and was kicked out of the mission. Not sure what task 2 is. Any advice?

That's how it works though. Every piece of software you've ever used was once a beta version. I'm not sure what you're getting at. If you want these complex addons (and as you're happy to participate in an open beta it suggests you do) then expect that occasionally changing something will break something else. That is unfortunately what happens when you're dealing with complex software.

@aspen Great catch, I've been getting that error, hopefully now resolved.

@bignewy Thanks, I'll try to provide more details if I spot it again and will check the other conditions as advised by yourself and Swiftwin9s.

I've had this twice now where shortly after launch a HARM will despawn and disappear. I've attached two short TacView tracks to illustrate this. In the first example an incoming missile also despawns. However, I've not been able to reproduce conditions to get it happen reliably and mostly the HARMs work as intended. HARM1.zip HARM2.zip

iirc this is covered in Mag's Nav video -

@Baltic_Dragon Success! Your suggestion of getting my wingman down underneath the clouds with me worked. He did enough to make the difference and I think he survived the ejection! Now I just need to learn not to throw out chaff against an IR missile in mission 9.

Really appreciate you engaging on this. I'm sure there are plenty of guys getting through the mission so there must be a way, it's not all on your shoulders. That said, any incremental improvement would be welcomed!