unable to reproduce issues caused by mods Radio preset frequency desync when entered rapidly

[FalcoGer]

I wrote a tool

that can enter preset data for the AH64 rapidly by using an exports script.

However using this rapid data entry causes desync in that the back seat has the correct frequencies and the front seat has the incorrect frequencies on the presets.

For example on preset 4 the backseat has FM2 on 35.0FM while the front seat gets the default 30.02FM.

Furthermore, this happens even if the copilot joins later after the presets have been put in.

To reproduce:

1. Join busy server
2. Have your buddy join
3. Use coordinate converter to input preset data rapidly. Seems more prone on FM and UHF, but could be random. not sure.
   1. Select seat after joining aircraft
   2. Select Menu/DCS/Aircraft/AH64/DTC...
   3. In the Radio Presets tab select the preset you want to change
   4. In the bottom enter frequency data for that preset by ticking the checkbox and then enter the number
   5. repeat for a bunch of presets (go to step 3)
   6. click the play button on the top
4. Observe com page discrepancies between the two players

Tracks attached.

Georgia At War v3.0.24_evening-20240420-180921-plt.trk

Can't attach CPG track due to size limitation.

Please update allow for larger files.

This track will be deleted from google drive whenever I feel like it.

https://drive.google.com/file/d/18Gb3TsynNAkaRU3R7rbtoLJVe7YTOYKG/view?usp=sharing

Edited April 20, 2024 by FalcoGer

[FalcoGer]

Why way this moved?

Even if the tool was faulty, it shouldn't result in desync between the cockpits.

All the tool does is cause button presses, it does not interface with any code or memory of dcs directly and only interacts through the buttons in the cockpit. it just so happen that the timing of the button presses causes the issue.

In other words, the tool can't be fixed. I press the right buttons. The issue is with the module.

If you do not wish to install my tool for security reasons, i can provide the json data to send over a tool like netcat to the lua export script instead. the lua script will interpret the data the same way as though it came from the tool. alternatively i could provide a lua file with the data baked in. but I won't bother wasting my time unless you intend to investigate the issue further.

Perhaps the next time you could reach out for further information and/or assistance instead of concluding it's my fault, move the topic and label "can't reproduce, it's your fault" without a comment.

Edited April 23, 2024 by FalcoGer