EWS // Data Cart: Flares do not sequence properly
-
Hi all,
Apologies if this has already been reported. I did a search on the forums and came up short.
I’m having an issue getting my flares to sequence properly.
Version: 4.34.0 (x64)
Expected behavior:
Flare program settings should burst/sequence as programmed the same way Chaff program settings do.Actual behavior:
Flare programs do not sequence properly. They only deploy the initial burst of the sequence, and none of the remaining sequence, if there are no chaff settings applied to the program.See video:
-
Look for sequence and quantity values of 0 which are bad news.
-
Look for sequence and quantity values of 0 which are bad news.
I’m not sure I understand your reply. Why are quantity values of 0 bad news? Is this a known issue?
How do you go about setting programs specifically for only chaff or flare in 4.34?
-
Good catch - reported on Dev.
Let’s hold off on speculations until we can get a definitive answer.
-
hi
is your ploblem like this?
https://www.benchmarksims.org/forum/showthread.php?36642-BUG-report-Flare-Sequence-Quantity-don-t-work-when-Chaff-Sequence-Quantity-is-0sorry i can’t post link,but you can find my post in this technical support category.
regards. -
hi
is your ploblem like this?
https://www.benchmarksims.org/forum/showthread.php?36642-BUG-report-Flare-Sequence-Quantity-don-t-work-when-Chaff-Sequence-Quantity-is-0sorry i can’t post link,but you can find my post in this technical support category.
regards.Yes, this appears to be the same bug I’m reporting. Good to know it’s not just me then.
-
Watched video. First note is that your DTE load won’t work because CMS system is not in standby (or off?). But it was loaded anyway on spawn. That step is doing nothing.
Second you’ll find that if you try to enter that program manually into DED/EWS page that it’s not valid. Let this be a lesson not to use data cartridge for debugging.Valid values
Burst Quantity: 0*,1-99, step 1
Burst Interval: 0.020-10.000, step 0.001
Sequence Quantity: 0**,1-99, step 1
Sequence Interval: 0.50-150.00, step 0.001*Results in no dispense of that store.
**Minimum 1 recommended in all cases. Dispenser was noted not to dispense flares and to dispense too many chaff when certain SQ was set to 0.So the final sequence would normally be programmed:
BI 0.750 BQ 5
SI 1.000 SQ 1SI 1.000 is essentially meaningless but 1.000 is a good, valid, safe default number. Hopefully CMS-AUTO will be changed so it uses SI between sequences in a future version.
-
Watched video. First note is that your DTE load won’t work because CMS system is not in standby (or off?). But it was loaded anyway on spawn. That step is doing nothing.
Second you’ll find that if you try to enter that program manually into DED/EWS page that it’s not valid. Let this be a lesson not to use data cartridge for debugging.The bug report pertains to the the data cartridge as mentioned in the subject title. How can a person debug the data cartridge without using the data cartridge for debugging?
Dispenser was noted not to dispense flares and to dispense too many chaff when certain SQ was set to 0.
What part of my video did you see too many chaff dispensed?
Why do my settings properly deploy chaff even when flare settings are zero’d?
Why do my settings properly deploy flares if chaff is also set on the same program?
Are you suggesting the simulator is behaving as intended? -
Test request for you. Please can you try the same thing only instead of zero-ing the chaff inteval, turn off the chaff power switch and then try the same program dispense experiment. You need only try this with one program from the 1-6 set – results will always be symmetrical in that regard. I think I see why you are getting the behavior in question and this test will help make that certain. If I’m right it’s probably a simple fix but aside from always having non-zero chaff no workaround for now, I’m afraid.
-
For Boxer:
-
Yep – that pretty much seals the deal. Definitely a bug. Simple fix.
I want to take a moment to thank you for clear and complete reporting – your information sent me to exactly the right place in the code in a matter of minutes. Would that all bug reports were so easy to follow.
Oh, and sorry about the bug of course
-
Cool. Glad to help.
-
I do like a happy ending…
The bug was found and this will be fixed in Update 1.