GrEaSeLiTeNiN Posted November 6, 2021 Posted November 6, 2021 (edited) Hi, I'm using the latest open beta. In semi-auto and auto modes, forward on the countermeasure switch seems to do nothing. Should it not dispense program 5 as stated in the manual (see screenshot)? The switch works fine (fwd and aft) in Manual and Bypass modes. For example, in fwd, it will dispense Prog 5 in Manual mode. But in both Semi-Auto and Auto modes, fwd on the switch does not dispense anything. I can't figure out why. Was there an updated change? Please also see attached track file. Thanks! Hornet Countermeasures Switch Fwd Issue.trk Edited November 8, 2021 by GrEaSeLiTeNiN AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Chain_1 Posted November 6, 2021 Posted November 6, 2021 Might be WIP, but that's what is supposed to happen. It's not happening for me either. From the manual (p. 491): "Forward. When in BYPASS mode, this will release one chaff bundle. If not in BYPASS mode or OFF, it will initiate manual program 5." 1
Shimmergloom667 Posted November 7, 2021 Posted November 7, 2021 On 11/6/2021 at 2:59 PM, GrEaSeLiTeNiN said: Hi, I'm using the latest open beta. In semi-auto and auto modes, forward on the countermeasure switch seems to do nothing. Should it not dispense program 5? The switch works fine (fwd and aft) in Manual and Bypass modes. For example, in fwd, it will dispense Prog 5 in Manual mode. But in both Semi-Auto and Auto modes, fwd on the switch does not dispense anything. I can't figure out why. (Is this intended?) Please see attached track file. Thanks! Hornet Countermeasures Switch Fwd Issue.trk 563.05 kB · 6 downloads That is correct behaviour: in Semi-Auto DISPENSE SWITCH FWD irl provides semi-auto consent, as in "go and release the countermeasures that you deem necessary". Auto is fully automatic and thusly dispense fwd does nothing. DISPENSE AFT dispenses the selected pgm. i7 - 9700K | 32 GB DDR4 3200 | RTX 2080 | VKB Gunfighter Mk II /w MCG Pro | Virpil T-50CM2 Throttle | TrackIR 5 | VKB Mk. IV AJS-37 | A/V-8B | A-10C | F-14A/B | F-16C | F-18C | F-86F | FC3 | JF-17 | Ka-50 | L-39 | Mi-8 | MiG-15bis | MiG-19 | MiG-21bis | M2000-C | P-51D | Spitfire LF Mk. IX | UH-1H
GrEaSeLiTeNiN Posted November 8, 2021 Author Posted November 8, 2021 8 hours ago, Shimmergloom667 said: That is correct behaviour: in Semi-Auto DISPENSE SWITCH FWD irl provides semi-auto consent, as in "go and release the countermeasures that you deem necessary". Auto is fully automatic and thusly dispense fwd does nothing. DISPENSE AFT dispenses the selected pgm. But the manual does not put it that way. AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Tholozor Posted November 8, 2021 Posted November 8, 2021 (edited) The DCS manual needs an bit on an update on the logic. The behavior @Shimmergloom667 described is correct as-per the NATOPS manual. In MAN mode: - FWD will initiate manual program 5. - AFT will initiate the selected manual program. In S/A mode: - FWD will provide semi-automatic consent. - AFT will initiate the selected manual program. In AUTO mode: - FWD has no function. - AFT will initiate the selected manual program. In BYPASS: - FWD will dispense chaff singles doubles. - AFT will dispense flare singles doubles. Edited September 13, 2023 by Tholozor Updated bypass logic 1 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
Shimmergloom667 Posted November 8, 2021 Posted November 8, 2021 (edited) 3 hours ago, GrEaSeLiTeNiN said: But the manual does not put it that way. Oh yeah, sorry: I didn't notice if you were wondering about the manual (which is wrong, if we take real life behaviour) or about the behaviour itself (which is correct). @Tholozor kindly clarified that again, as well Edited November 8, 2021 by Shimmergloom667 1 i7 - 9700K | 32 GB DDR4 3200 | RTX 2080 | VKB Gunfighter Mk II /w MCG Pro | Virpil T-50CM2 Throttle | TrackIR 5 | VKB Mk. IV AJS-37 | A/V-8B | A-10C | F-14A/B | F-16C | F-18C | F-86F | FC3 | JF-17 | Ka-50 | L-39 | Mi-8 | MiG-15bis | MiG-19 | MiG-21bis | M2000-C | P-51D | Spitfire LF Mk. IX | UH-1H
GrEaSeLiTeNiN Posted November 8, 2021 Author Posted November 8, 2021 Thanks guys! I got it now. Part of the confusion I had (aside from the manual) was that in Semi-Auto and Auto modes, the little number below the mode name was actually the manual program which I could initiate with Aft. I had thought it was the program self-selected and dispensed by Semi-Auto and Auto modes. But while testing, I noticed something odd. I'll try to explain it... Semi-Auto: Fwd consents and stops it as intended. But if I stop the dispensing halfway, I cannot resume (re-consent to dispense) while the initial audio warning is still going on. I have to wait for the initial warning sounds to end then re-consent when a new audio warning starts, in order to dispense again. Auto: Consent is automatic and Fwd stops it as intended. But similarly, it will not auto resume after I stop it halfway, so long as the audio warning that started it is still going on. It will only auto dispense again after the initial audio warning ends and a new audio warning starts. Is this correct? AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
GrEaSeLiTeNiN Posted November 12, 2021 Author Posted November 12, 2021 (edited) Thanks guys! I got it now. Part of the confusion I had (aside from the manual) was that in Semi-Auto and Auto modes, the little number below the mode name was actually the manual program which I could initiate with Aft. I had thought it was the program self-selected and dispensed by Semi-Auto and Auto modes. But while testing, I noticed something odd. I'll try to explain it... Semi-Auto: Fwd consents and stops it as intended. But if I stop the dispensing halfway, I cannot resume (re-consent to dispense) while the initial audio warning is still going on. I have to wait for the initial warning sounds to end then re-consent when a new audio warning starts, in order to dispense again. Auto: Consent is automatic and Fwd stops it as intended. But similarly, it will not auto resume after I stop it halfway, so long as the audio warning that started it is still going on. It will only auto dispense again after the initial audio warning ends and a new audio warning starts. Is this correct? Hi, so in the OP, I get that it is correct as is. But can someone shed light on the other issue described above? That is, for Semi-Auto and Auto, I am unable to resume dispensing if I cancel dispensing halfway, so long as the current RWR warning beeps are still going on. Thanks!UPDATE: Reported as likely a bug. Edited November 12, 2021 by GrEaSeLiTeNiN AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Recommended Posts