DSplayer

Ok just checking back it seems like my super old modified F-18 CMDS lua got activated which I hadn't noticed since it didn't break any IC checks (and I forgot what the original CM programs on the 18 looked like). It had a repeat of 0 for Program 1 (which isn't possible normally since 1 for RPT is the lowest it can go) and if you tried to decrease past 0, it would cause that overflow to happen.

Got reported when the Mirage F1 first came out, still hasn't changed.

I am sure that I didn’t have any mods, edits, or tools that can be installed to edit countermeasures. EDIT: Here is a log and a video for an instance where the RPT overflow happens just in case: dcs.log

Btw the USN did state a Mach 5 speed figure for the 54C to Congress prior to the proposed NASA tests. However, I do think the motor values we have know are the most accurate values we can get with the information that is available.

I think he means no Agile Eagle slats. EJs do, of course, have leading edge flaps.

Bug: Decreasing Repeat (RPT) when editing countermeasure program past 0 causes large integer to appear when its expected to roll over back to 24. Can I reproduce it 100%: Yes How to reproduce/description: Step 1: Open the EW page on the F-18 Step 2: Attempt to edit the repeat for a countermeasure program (doesn't matter what mode the ALE-47 is in) Result: The countermeasure repeat interval will overflow into an extremely large integer. DCS Version: Open Beta 2.8.2.35759 Mods: None. Screenshot: Broken Repeat CMDS F-18.trk

Just updated the mod to V1.5.5. Name of the mod has changed since capability for the Mirage F1EE has been added.

Bug: Currently the AERO-3B is used when mounting the Rb24, Rb24J, and Rb74 when the AERO-3B should only be used with the Rb24 and Rb24J. The Lavett 74/LAU-7 should be used with the Rb74 but can also be used with the Rb24J. In-Game Screenshot: Current in-game loadout that shows the Rb74 using the AERO-3B DCS Version: Open Beta 2.8.2.35759 Mods: None. Images:

I don't think this is anything new. I remember the F-14's jammer working a lot more uniquely compared to other jammers since it isn't a constant noise jammer which constantly jams but rather tries to break the lock and then turning off when the lock is sufficiently broken but also jams radars that are in a fire control mode. I think this thread kind of has the all you need to know for why the F-14's DECM does what it does:

I'm not too well versed on this so I'm sure someone else who is more knowledgeable on the topic can probably shed more light but I think the different colors are just colors to differentiate each collision cell.

It can be pilot sniped. It's just that the damage model is a lot more accurate than those of the F-18 and F-16. For the F-18 and F-16, if you hit anywhere in the entire canopy, the pilot is killed while for the F-14, you have to actually hit the pilot to kill them. F-14 damage/collision model: F-16 damage/collision model: As of now, the ED damage models for the F-16s and F-18s aren't as accurate/precise compared to the WW2 damage models. There was a reddit post on Hoggit about this recently and NineLine did respond regarding it:

Yeah I'll attempt to update it over the weekend.

VSL Low and PAL you should be able to see the diamond going across the HUD when you’ve selected an applicable HUD mode and weapon (for example A/A HUD mode and not guns selected). VSL Hi scans super high so it’s not shown in the HUD since its scan volume is beyond the limits of the HUD.

If the implementation is similar to how the AIM-120’s target size and RCS size options work, it probably would affect target acquisition and the fuzing. Maybe when those intricacies are added, the MSL SPD knob would work too.

I would like to point out that the missile still goes active at 10 nm but the F-14's RWR picks it up at 7 nm thanks to how HB implemented signal to noise ratios and made the RWR accurate/more intricate than others. So maybe trying with other modules would be good too to see how it fairs.

The AIM-120s doesn't have the active_radar_lock_dist parameter which causes the AI to defend the AIM-54 and other missiles (SD-10 is another one) at that parameter's set distance (which is roughly 10nm for both).

I think all the AIM-54s can HOJ but they go HOJ like any other Fox-3. They'll get a missile warning once it goes active on them but they also get a missile launch warning as well but you can try to mitigate that with using PH ACT or something.

From what I'm seeing here, you manually lofted the missile in such a manner which made it go higher than it usually would and it couldn't get down to thicker air in time to engage the target. If you didn't manually loft it at like 20-30 degrees and used a more modest 13 degrees, the missile would've probably hit since it wouldn't have been so high while having a higher terminal velocity. Lofting at that high of a pitch would maybe be applicable against targets like 80 nm out but not at the range that you fired at the F-15. This is combined with you having an extrapolated track which basically made the missile rely on its own seeker and stuff and in DCS with the older API/scheme, it means that the missile goes active at a point and looks for the original target and it seems that it might've attempted to look for it but went active later on than the point you wanted it to go active at.

Set Q Mode -> QDES

Do you have time of flight for the missiles in each of those tests? From my experience, the TOF drastically increases also you manually loft the Phoenix higher and higher.

Hmm Lunar New Year airplane announcement? Would be pretty pog ngl.

Check your DLC and your deadzones for you stick. DLC is required for ACLS landings and sometimes not having large enough deadzones can cause issues with the ACLS.

Bug: When the radar is in standby, you can pickup radar contacts and the radar clutter is still generated. Can I reproduce it 100%: Yes How to reproduce/description: Step 1: Turn the radar to standby. Step 2: Pickup and lock up a target. Result: You will be able to lock up targets when the radar is in standby. The clutter is displayed as well. DCS Version: Open Beta 2.8.1.34667.2 Mods: None.

Currently it seems that you can only change the flare and chaff countermeasure program settings in the mission editor and not when you're actually in the jet. Something like how the laser codes are changed on jets like the F-14 or Mirage 2000C using the kneeboard. FYI, the Mirage F1 also lacks the ability to change the laser codes outside of the mission editor iirc.