Aernov Posted September 27, 2021 Share Posted September 27, 2021 If at the moment of pressing CM Flare or Chaff commanded release was impossible (either because required expendables are not present - spent or not loaded, or if EXP selector knob is inhibiting release from the only group of dispensers that contain required CM type (for example, UP selected and no flares in upper dispensers)), that release command gets "stored" and is executed at the first chance in the future, either when needed CM type is loaded or EXP selects correct dispenser group. AV-8B CM release command stored if inhibit.trk In the track - quick start "Ready on the ramp", standard 120 flares 60 chaff loadout (chaff is only in the two of the UP dispensers). I made chaff release program (burst 4 interval 0.3 salvo 1) to easily see the release. With EXP in ALL or UP program releases immediately, in DN - no release, but when knob is returned in UP or ALL - program releases immediately, no matter how long the interval between the command and release possibility. Only one last command is stored. Also, should EXP knob straight up prohibit release from unselected dispensers? Shouldn't it just set priority to the selected ones? If I have flares in top and bottom blocks, select upper ones and spend all the flares in them during attack run, I will be unable to immediately continue flaring until I remember to turn the knob, even though I still have 60 charges on the bottom? How does it work in the real plane? In my opinion (that is not supported by anything except my guess), this EXP selector logic would allow release from unselected dispensers if required CMs in selected ones are spent, just to prevent life threatening issues in emergency situations. 1 Link to comment Share on other sites More sharing options...
AlphaJuliet Posted October 28, 2021 Share Posted October 28, 2021 Issue confirmed and reported. Thanks for the report Link to comment Share on other sites More sharing options...
Recommended Posts