[REPORTED]"chaff flare" on gear retraction

See trackfile (near end of file). Afaik Betty won't say chaff flare unless you deploy chaff or flare.

BettyChaffFlareOnGearRetractEvent.trk

This is the 2nd time that an F-16 track shows something different to you than to me... (touch-and-go was the previous one, https://forums.eagle.ru/showthread.php?t=265837 )

What do you think of this test, for testing purpose, back up your F18 controls, uninstall F/A-18 Module, test this trackfile again to see if it's related to any Hornet-code (and then reinstall Hornet)? (After there was that RWR issue on F-16-release for non-Hornet-module-owners, I never totally can stop thinking about the thing that F-16 could still share some part/parts of code with Hornet module......)

I once had a failing TM Warthog throttle that - once it got really bad - dropped chaff/flares when trying to extend the airbrake (and vice versa). Turned out that either a broken wire or solder was the problem. After replacing the throttle with a new one, no more issues. Just a thought - maybe OP has a similar issue that's creeping up.

Could it be related to my modified CMDS.lua file? (attached below)

CMDS_ALE47.lua

I had this problem many times during the last weeks.

Once gear up, I can hear that message.

I'm using a modified .lua as well.

Thanks for confirming, I would suggest using an unmodified file. thanks

Sorry to say that: NO, I won't. Programming is a nightmare in VR and waste of life time. Not meant to be offensive, OK? :) Never would I ...

Programming is a nightmare [...] and waste of life time.

THIS, exactly. Please, BigNewy! :(

By that I assume a preset data-cartridge that we DON'T have to reprogram everytime we spawn in, correct??

As this issue only arises with an edited lua file it is not a bug.

That .lua part was created by ED for that specific reason, BigNewy, to BE edited by users for custom programs.... So this definitely should fall under "ED supported file-customization"

That .lua part was created by ED for that specific reason, BigNewy, to BE edited by users for custom programs.... So this definitely should fall under "ED supported file-customization"

Again your assumption is incorrect...the file was created to allow cockpit functionality and nothing else.

People have chosen to modify the lua to suit their own purposes (which is fine) but please make the correct distinction. In essence people adapt the lua to speed up their personal start up process and that's where errors can occur.

FWIW I use a custom lua for chaff/flare and I don't get the audio bug as described. So perhaps you have corrupted your lua.

Seems that maybe you should backup your modified files and do a repair to test it. If it works then you have your answer.

Or I directly PM Panther and ask him for his custom .lua and then I compare where I have floats (0.1 to sth. around 30 or so I guess) where I possibly should have zeros, that's currently what I suspect to be the culprit. PMd you, Panther.

Again your assumption is incorrect...the file was created to allow cockpit functionality and nothing else.

 

People have chosen to modify the lua to suit their own purposes (which is fine) but please make the correct distinction. In essence people adapt the lua to speed up their personal start up process and that's where errors can occur.

Aaah okay! interesting

Then the question that comes up, is, why would the "default" DCS F-16 program not be set up in the way that 1 CM button is 1 chaff and another is 1 flare? (as that makes most sense on modern battlefield feat. A2A engagements...)

Ok I managed to narrow it down even more, BigNewy.

Below, I attached the file where it still occurs ("stillBugged"). The "working" custom file (big shoutout to Panther for helping in testing!) can be found on this page on their group's website

The ONLY different lines are these 2 parts (I use https://www.diffchecker.com/ to quickly find the differences)

-- MAN 1 part

and

-- MAN 5 part

So I conclude one of those 2 parts is the culprit. (I doubt it can be the titles, as the "--" lines are comments and DCS fully ignores those afaik?)

Hope you (or someone) has a theory what it is/can find out what it is.

CMDS_ALE47stillBugged.lua

Ok I managed to narrow it down even more, BigNewy.

 

Below, I attached the file where it still occurs ("stillBugged"). The "working" custom file (big shoutout to Panther for helping in testing!) can be found on this page on their group's website

 

The ONLY different lines are these 2 parts (I use https://www.diffchecker.com/ to quickly find the differences)

-- MAN 1 part

and

-- MAN 5 part

 

So I conclude one of those 2 parts is the culprit. (I doubt it can be the titles, as the "--" lines are comments and DCS fully ignores those afaik?)

 

Hope you (or someone) has a theory what it is/can find out what it is.

This file is coded ANSI.

I think it would not work, since IIRC it should be coded UTF-8. Can someone confirm this?

Ok I managed to narrow it down even more, BigNewy.

 

Below, I attached the file where it still occurs ("stillBugged"). The "working" custom file (big shoutout to Panther for helping in testing!) can be found on this page on their group's website

 

The ONLY different lines are these 2 parts (I use https://www.diffchecker.com/ to quickly find the differences)

-- MAN 1 part

and

-- MAN 5 part

 

So I conclude one of those 2 parts is the culprit. (I doubt it can be the titles, as the "--" lines are comments and DCS fully ignores those afaik?)

 

Hope you (or someone) has a theory what it is/can find out what it is.

:thumbup: