Ballinger French

Overhead approach to runway 3L at Nellis, left break over the approach end. For whatever reason, I decided to actually flare this time.

Pretty sure there's a bump on the approach end of the runway at Tonopah. It might've helped if I flared the correct way too, but I'm sticking with the bump theory for now.

Left Closed Traffic runway 32, Tonopah, Nevada.

Aha, the culprit is already being hunted, thank you. Doesn't appear to be too high on the fix list at this time, so I guess the only viable workaround would be to carry an extra AMRAAM on a pylon and use it as a captive hostage to force the correct HUD symbology for the other missile(s) when they are fired. I mean, the hostage missile could still always be used for attacking a bandit at some point, just with the caveat that telemetry isn't possible after it's fired. I guess you'd be firing in FC mode (fingers crossed) in this situation.

Hi, When firing AMRAAMs, after the last AIM-120 missile on the aircraft is fired, the HUD symbology reverts to either Sidewinder missiles (if loaded) or simply goes back to basic air to air mode with no inflight radar guided missile telemetry displayed. The problem here is that the AIM-120 is initially data-linked to the firing aircraft for guidance to target before the missile's own radar activates and the AMRAAM becomes autonomous. Without any indication of when the AIM-120's own radar activates and the missile goes 'Pitbull', the pilot in the DCS F-16 has no reference as to when to break off tracking the target and must simply guess when the missile has either gone active or splashed the target. Again, this condition only exists after the very last AIM-120 is fired. When there are additional AMRAAM stores available on the aircraft after a AIM-120 missile is fired, the HUD provides time to missile activation and estimated time to impact. This information will however disappear after the very last missile is fired, leaving the pilot in the dark as to missile status. Is this actual F-16 logic or is the DCS F-16 perhaps a little bugged here? Thanks!

Thought this was one of my cooler shots.

Okay, I was hesitant to upgrade from DCS 2.8 after reading about all the people here having issues with massive stuttering on Intel Core I7 & I9, 12th and 13th generation CPUs. My system is based on a I7 12700K, overclocked to 5.0ghz on 8 P-cores and 3.9ghz on 4 E-cores, with 32mb of DDR5 running at XMP profile specs. I have a Nvidia RTX 3070 with 8 gigs of ram for video. I upgraded to DCS 2.9 today. I am experiencing absolutely NO stuttering or pausing running the DCS 2.9 MT executable, and in fact the sim is as smooth as it's ever been. I'm running under Windows 11 64 bit Pro with a M2 PCIe Nvme SSD, and both Windows and DCS installed together on the same card. For me personally, this has been about the smoothest major DCS update yet. DLSS, DLAA, both working flawlessly with excellent performance all around. I never experienced any delay with the game startup or freezes in the main menu, and this leads me to believe whatever issues other Intel CPU owners are experiencing must somehow be software/BIOS setting related rather than hardware incompatibility. One thing I have noticed with Intel-based systems is that both motherboard BIOS and Windows tend to be overly 'green' with dynamic CPU scaling and core parking. Core parking is set by default on Windows Intel based systems, and essentially shuts down several physical CPU cores when the system in not under significant thread loading, much like Nvidia video cards automatically throttling GPU and memory clocks when not under load to save electricity and reduce heat. I really suspect Core Parking might be a culprit here in regard to DCS stuttering in that the DCS platform may not be properly thread loading parked cores when the sim is booting up. Again, Core Parking should disable itself as the CPU core demand goes up, but I'm wondering in something is getting flubbed up in the process and the DCS engine is somehow avoiding thread loading the parked cores, even though they should be 'unparking' as the sim boots up. Just a theory. It certainly wouldn't hurt to disable CPU core parking on your Intel CPU/Windows setup and giving it a go. Whatever IS going on with those of you experiencing the horrible stuttering, it really does not seem to be hardware dependent as my system is the same as several others on this thread that are seeing the stuttering with the MT beta. Here is simple tutorial on how to disable Core Parking on Windows 11: https://www.youtube.com/watch?v=sFz8HRk4WfI

Has anyone with this issue tried running Process Lasso to manage CPU affinity for DCS 2.9?

Weird. In the past, running Prepar3D Flight Simulator, I had problems with certain add-on aircraft causing stuttering which I traced down to an overloaded CPU as others here are mentioning having issues with DCS 2.9 Using windows Task Manager, I masked half the cores on my CPU with Prepar3D still running, then immediately reactivated them again. This had a net effect of 'rebalancing' all the threads running on different cores so that no single core was maxed. In other words I didn't have to keep any core masked but instead I could essentially rebalance the distributed load as I described.

You should be able to uninstall DCS 2.9 (the entire game), and then reinstall the DCS 2.8 stable version (non open beta version).

Has anyone affected by this issue tried updating their motherboard chipset drivers and/or verifying they have all the latest Windows updates? Although I haven't installed 2.9 as of yet, I have been running the 2.8 MT version for about six months using a I7 12700K CPU (hyperthreading enabled) and Windows 11 Pro without issue. SSAA never worked with the 2.8 MT version, so I was never able to use it, FYI.

I noticed that my credit card stop letting itself be charged for DCS modules that can't seem to get canopy reflections fixed once and for all.

Nah. I can put $$$ towards a RTX 3080 video card like yours, currently listing anywhere from $900 to $1000. Who needs a F-18 and/or food, right? Seriously though, the DCS rep in the above post just admitted the F18 is broken and it may take quite a while before it's fixed. Fair enough. That person is being honest and straightforward, which I appreciate. I don't want to invest a broken sim at this time, so the free trial worked out wonderfully for me personally in this instance. Additonally, I don't have to invest copious amounts of time learning the system and avionics of a sim that will end up disappointing me in the long run. The A-10II module I currently own is wonderful and when I sense one of the other DCS mods that are on par with the A-10, I will invest in that. Case closed. Have a nice day.