Mr_Blastman

You might want to try removing affinity from your last CPU core in Windows task manager under the details tab for the DCS process.

OKAY I removed CPU affinity from Core 7 on my CPU(as shown by Windows, which is actually the last core) and 90%+ of the hitching was resolved. Weird.

I can confirm this helps. I was having hitching on my Intel 7700k, and removed affinity from Core 7(the last core), and 90%+ of the hitching stopped.

Before the 2.9 update I could fly the Apache in the Instant Action Live Fire Range mission with butter smooth framerate. Everything was perfect. There were no stutters, there was no hitching. After the 2.9 update... Nighmares! Hitching. Stuttering. Popping. The moment I take off I begin seeing intermittent stutters and frame skips. This is driving me nuts! What is going on? System: Intel 7700k CPU 32 gigs RAM NVIDIA 1080 GTX GPU DCS loaded on SSD Operating system on NVME .M2 SSD Page file on a separate SSD Nvidia driver version 536.67 Steps taken to try to resolve: Deleted DCS shader caches Deleted NVIDIA shader caches Rebooted many times Nothing fixes. I had a similar issue almost a year ago, but that was eventually resolved. Alas, here I am again, and I'm going insane. I need butter smooth framerates to fly precisely. As things are right now, DCS is a paperweight again. Please help. Thank you.

There is a nasty bug with the F-15E on hotpit servers, where if you spawn in a hot jet then you cannot transmit at all to AWACS, despite correct settings. Your requests simply will not leave the jet and go to them. The weird thing is you can hear other players make AWACS calls. Switch to a cold jet and ramp start and the problem goes away.

OP you should always fly open beta if you are interested in multiplayer. You will not find many release servers. Most are open beta.

I think the BLU-107 is also available on the Mirage, as it is a French designed weapon, after all.

I set my 97s to 1200 ft. Burst altitude and then aim for the center point of say a dual ripple release and they hit smack dab where they should. This is wrong, because that means I have to lead a single 97 by quite a fair to ensure a hit, but works for now, nonetheless. I have accommodated for wind by setting up missions with zero wind, but still they are off slightly.

This begs the question... what is the manual engine restart procedure in flight? I had this happen yesterday but could not crank the engines like I would in the Viper...

Kill them well before they get close or be prepared to run...

The vast majority of multiplayer servers are open beta only. You cannot see them in stable.

Think of the Huey as training wheels. Then try the Hind. After you are ready to kill yourself, come back to the Apache, and she'll feel easier. Since the latest update I haven't rolled her once. Before the update she'd roll all the time. You're likely being far too aggressive with your controls, where in the lighter helicopters this isn't punishing because they weigh far less and their center of gravity is different. The Apache is a flying brick. Treat her with respect and be very delicate with the controls. Also, what helped me the most was learning to turn without using the tail rotor. She doesn't like you touching the tail rotor much over about 60 - 70 knots. Turn her like a plane, except raise the nose above the horizon before pulling harder.

The one that hits.

Flip your helmet visor down. LSHF + N. Boom. Amazing polarization filter. F-16C has the easiest control scheme because the jet was designed by geniuses, but the F-15E is not that far behind.

That would be up to server administrators to decide. If you are unable to play on an enforced server with VR, good thing there are other ones to choose from. With a Geforce 4090 you hardly have an issue with running VR with clouds on, as your specs advertise.