nubbins_

I can also confirm something about the last 1 or 2 updates broke mission triggers. But it's not universal, just some of them. Helo Hunter for F-15C is half-broken - the first wave of Mi-8s will give a mission fail ("helos reached their target") the moment their flaming carcasses hit the ground. Which is also at the very same moment that the success message for destroying the first wave appears. The PG Fighter Sweep mission (for F-16C I think) is broken to a more severe extent, a number of triggers are broken. The late activation strike units do not spawn in under any circumstance. Even if the F15E strike package is set to immediate activation, it seems that the success messages for killing the 2 x Mig29 waves do not appear even after they die, and thus the Strike Eagles will mission fail when reaching their target ("target area not swept of fighters"). Syria King of the Hill for F-16C has also been a bit wonky as of late (AI flight seems very slow to detect that player has joined formation, and thus keeps flying a loop for a while before the trigger happens), but I'm not 100% sure about this one. I just had a complete clean out of Openbeta folder and user folder recently due to troubleshooting another bug, so at least the first two mission examples are about as vanilla as can be.

I think that did the trick, both amraams finally back to normal now. Which then begs the question........what do I have to be paranoid about reinstalling now into savedgames? It's a tossup between tacview and ECHO19 Thanks everyone for the help

Back on 2.9.2.49940 still happening on a COMPLETELY DELETED AND CLEAN install folder fully repaired multiple times what is my monke brain missing here?? @Art-J totally forgot about savedgames, unfortunately this is gonna take a lil while to backup my binds

Like I said, I don't run with the 120D mod after any DCS update. The only file that it changes, gets replaced clean every time - if I want to use the mod again I have to put the modded file back in, which isn't the case for all of the testing tries so far. I don't use the rest of the files (installing by .bat), I just copy some lines of code into aim120_family.lua. I have just finished redownloading entire core install folder from scratch. Gonna clean again and try again.

New Openbeta update today - 2.9.2.49940 (vs 2.9.2.49629 the original 2.9.2 release). Unfortunately, issue is unchanged.

That's what I thought as well, but the only mod I really still keep around is the 120D one. It only involves changes to one file in main folder (aim120_family.lua), and each time I update between game versions, it gets replaced with a fresh copy of the vanilla file. And the changes to the .lua is strictly to the AIM-120B code section - AIM-120C as I'm using in all my tests is usually not at all affected. Aside from that, the only other one I can think of is probably Tacview plugin and ECHO19 sounds. Earlier this year I did a complete clean and reinstall of my folders to purge it of any old mods. I just went back to 2.9.2, is still doing the same thing on Stations 1 and 9. The strange choppy behaviour is visible from the #9 pylon launch. new amraam bug.trk

Not too sure how widespread this is (at first glance 9M/9X don't seem to behave any different compared to 2.9.1). If already reported please merge, but I didn't see any thread on this in General or Weapon Bugs. In 2.9.1: F-15E belly stations: drop missile first for separation, then motor ignites shortly after F-15E wing stations: motor ignites immediately F-16C all stations: motor ignites immediately In 2.9.2: F-15E all stations: now behave like they are belly stations, wing pylons will drop the missile through where drop tank would be, motor ignites delayed. Not yet sure what happens if equipping bags. F-16C: Station 1 (left wingtip) floats missile upwards like gravity doesn't exist, Station 9 (right wingtip) drops the missile like it's an Eagle belly station, AMRAAM flight behaviour SUPER erratic when launched from Station 9 I don't have the Hornet so I'm not sure if the dual AMRAAM rack is affected. Gonna test SD-10 later today after I go back to 2.9.2 again. Is my install just super borked? I find it hard to believe that no one else has noticed this super obvious behaviour in the past 6 days. Gonna get some trackfiles later as well - my clips are not taken from trackfiles though, but realtime F2 view. I've been updating back and forth between 2.9.1 and 2.9.2 to see if I'm just doing something wrong, but behaviour is consistent.

Isn't the 2000s+ single seat cockpit completely different? So even if you could mod a CFT-less -E to get there, it'd require some serious suspension of disbelief to pose as a -C A modern full fidelity -C is always #1 on my wishlist, because despite FC3 visual quality the consistent APG-63v1 is comfortable to use as opposed to ED constantly torturing the APG-68's performance. But Strike Eagle is a weird place to look for one's -C fix.........I mean if you really want to fly a long mission with 4 AAMs and internal fuel LOL Just caving to random community demands doesn't make for a good dev either...

Hi all, just checking in. I am new to DCS and have been slowly gathering gear and getting used to the Viper over the past 3 months - but I often still get pulled back into the comfort and safety of the F-15. Not gonna lie though, it's the current AMRAAM behaviour and AI wingman bug that pushed me to finally register here lol The F-16 is the sole reason why I decided to get into this sim. That said, I have been eyeing the Hornet lately and impatiently waiting on the Mudhen, as well as looking at different pedals and thinking about a TrackIR to replace my current Opentrack neuralnet setup. See y'all around!