Ahmed

Bumping this one as the recent changelog shows some fixes on AI launching issues fixed, but this particular one still remains and does break gameplay.

Together with this flares "bug" report, it is worth noting that the IFLOLS at the boat (the actual IFLOLS at the waist of the ship, not the overlay) is not lighting up now unless using CATCC. It used to work before, and it was how I guess most MP groups used it. Please restore the old behavior. Disregard, the actual IFLOLS at the waist of the ship si broken regardless of using CATCC or not. The meatball itself is not visible.

you know that the IFLOLS already has wave off lights intended for that effect, right? No need for made up flares

Enforcing the deck crew setting through the ME Mission Options setting doesn't work. After looking into the mission setting, the setting is being saved in forcedOptions under: when it likely should be saved (because it works if manually edited this way) under:

Posted in new thread, to cleanly report it, as this can now be easily reproduced. AI aircraft in multiplayer sessions are getting stuck in the catapult, if a player has launched off it before. Steps to reproduce: Launch off catapult Have AI (S-3B at least) try to launch off same catapult Dedicated server track attached. server-20241014-102904.trk

Same likely observation

Hi, When using the "SET ATC SILENT MODE" trigger on a supercarrier, ACLS won't work in the Hornet. Not even like it does in the Non-SC carriers. For any users NOT interested in using the AI CATCC (eg, 99.9% MP groups/users), can this be changed so that selecting "SET ATC SILENT MODE" reverts the logic to the Non-SC carrier one (lock on at 6nm)??

Hi, The SET_CARRIER_LIGHTING_MODE trigger is available in the ME but is not callable from mission scripts. Can this be added as a trigger function? Rgds

Exiting A/A mode with a STT lock results in the lock being broken if obtained from ACM submode In the attached track, the STT is dropped as soon as I exit A/A. This only seems to happen when the lock was made from ACM. It doesn't happen if the lock was obtained by other means (e.g., AACQ). acm.trk

can we get any update on this? Since a few months ago, AI aircraft (especially S-3) are getting constantly stuck on deck while hooking to the catapult. May be a more prominent issue in MP.

Noticed that I'm getting trackfiles on the SA for the Hawk missiles shot in the attached track, despite being in MAP (A/G) mode. hawk.trk

Reposting old unacknowledged report as the old thread is very outdated and messy. The yaw rate tone should begin beeping at 40º/s yaw rate, and the frequency of the beeping should increase with yaw rate until 60º/s where it becomes a steady tone. Observed outcome: currently in DCS the yaw rate tone is only beeping at constant frequency from 40º/s onwards Desired outcome: beeping starts at 40º/s, beeping frequency increases with yaw rate until 60º/s, steady tone past 60º/s Track attached. NOTE: do not confuse steady AOA tone (>35º AOA) in track with steady yaw rate tone. The steady tone in the track is due to AOA excursions above 35º, as I couldn't reproduce it while keeping AOA below 35º at all times. All yaw rate triggered tones in DCS are a constant frequency beeping that does not follow the description above. Source doc: NFM "Departure Warning Tone" (2.8.2.5) Video of expected outcome (1:35): yaw_rate.trk

Bumping this issue to see if it can get acknowledged

Most SLAM and SLAM-ER format options don't become available until selecting the unlabeled OSB 3 slam.trk

Let's try this again in an isolated thread... In the test conditions of the attached track, left rudder results in minor left yaw, right roll and heading increasing CW. No control surfaces other than rudder move in the FCS format, so this comes from a flight model issue. Expected results: left yaw (primary effect), left roll (secondary effect), heading decreasing CCW. rudder.trk