Unwanted Chaff/Flare dispensing
-
The program itself is on ‘Manual’ so no dispensing should happen right?
Actually, even if you are in SEMI or AUTO you have to give consent before dispensing.
My only guess is unwanted inputs on the keyboard or throttle - either by accident on your part (pressing on a key without realizing it) or on the programming of your HOTAS.
-
Do you own a X-55 HOTAS by chance?
-
I own the HOTAS cougar. All buttons respond normally as far as I can tell.
I agree that it has to be some kind of unwanted input, but it isn’t by accident because it happens several times during different campaign, TE…
It did however happen in the same gaming session, so maybe it goes away after reboot. -
dont’t know about the cougar, (mine is a warthog with stick and throttle)
but i programmed also the leds on my throttle, and after some time,
that part isnt working anymore.
are the buttons assigned as dx buttons, or do they have a programmed behaviour?
if they are programmed, I’d suggest simplifying it (at least for testing purpose), add small steps of functionality and trial and error each step. -
No answer but its very similar to a mission killer I get now and then. Can go on for many flights but eventually ceases and weeks can pass before its return. In flight will suddenly announce “chaff, flare…” and go nose vertical. Investigation discovers maxed out trim input. If control regained it inevitably does the same after a duration and repeats. Mission abort.
-
No answer but its very similar to a mission killer I get now and then. Can go on for many flights but eventually ceases and weeks can pass before its return. In flight will suddenly announce “chaff, flare…” and go nose vertical. Investigation discovers maxed out trim input. If control regained it inevitably does the same after a duration and repeats. Mission abort.
Seen the same myself, very occasional. No chance of nailing it down, so I just accept it and restart the PC after which it goes away for indeterminate period of time.
Glad to hear it’s not only me that has seen this!
-
Using ControllerMate and the Warthog stick on my Macs with FAF I’ve programmed a .25 sec delay into my CMS switch - thus requiring a positive actuation and solving the issue.
Dunno if one can do this on a PC with BMS…haven’t gotten that far into BMS setup as of yet. REALLY wish there was a version of ControllerMate for PC, because it would make PC life a WHOLE lot easier.
-
Hi
Recently I encounter some problems with unwanted chaff and flare being deployed without triggering it myself.
It happens seemingly random throughout a mission or TE. Meaning I give no input by pressing joystick buttons or keyboard.
Only throttle and stick control and then the Freetrack of course.
I do use WDP for setting up my DTC for chaff and flare programs.
The program itself is on ‘Manual’ so no dispensing should happen right?Any thoughts suggestions?
CheersI’ve noticed the when going into a TE about 30-50% of the time you get some uncommanded chaff/flare the instant you enter the cockpit.
-
I’ve noticed the when going into a TE about 30-50% of the time you get some uncommanded chaff/flare the instant you enter the cockpit.
For me it was during a flight actually…
Must indeed be some unwanted input. Although if several people have the same.
Maybe we have the same piece of software (besides BMS) actually causing it. -
Actually, even if you are in SEMI or AUTO you have to give consent before dispensing.
My only guess is unwanted inputs on the keyboard or throttle - either by accident on your part (pressing on a key without realizing it) or on the programming of your HOTAS.
I thought that only in SEMI you have to give consent before dispensing.
-
I thought that only in SEMI you have to give consent before dispensing.
BMS-Dash 1, p30, 1.2.2.4 CMDS Panel.
-
BMS-Dash 1, p30, 1.2.2.4 CMDS Panel.
correct. I haven’t flew since last year and forgot about it….Waiting for the 4.33 though
-
It would be prudent to go through your key file and check for duplicate commands.
I found that using DX numbers for anything that needs to be pressed and held helps me to avoid problems with multiple key presses too. There are so many call backs that weird things can happen when trying to issue two commands at once.
Another thing that can happen is when doing button or key inputs while in BMS one can accidentally be inputting something else and not know it because some controllers can have buttons in an on state so you may think you programmed Ctrl-b but input button 9 instead. Better to edit keyfile manually to be safe.
-
It would be prudent to go through your key file and check for duplicate commands.
I found that using DX numbers for anything that needs to be pressed and held helps me to avoid problems with multiple key presses too. There are so many call backs that weird things can happen when trying to issue two commands at once.
Another thing that can happen is when doing button or key inputs while in BMS one can accidentally be inputting something else and not know it because some controllers can have buttons in an on state so you may think you programmed Ctrl-b but input button 9 instead. Better to edit keyfile manually to be safe.
Thanks for the suggestion, but as I said before: at some points I’m giving no input it all and it still dispenses chaff/flare.
The problem however disappeared again after reboot, so it’s hard to track down. But it must have something to do with unwanted input.
