Flappie

I understand now, thank you.

I cannot reproduce your issue. Please attach your dcs log file from "Saved Games/DCS/Logs" and explain the steps to reproduce the issue.

DCS Controls page allows you to assign several buttons to the same command. Isn't it a satisfying solution for you?

@ThorBrasil @VPS_Choki Can you please explain exactly how you fixed this issue?

@Nealius I looked but couldn't find any report describing your issue.

This issue has been fixed internally. The fix should be part of the next core update.

Here's what we'll get with the next update. It seems to be correct.

Thank you very much. I've added your findings to the report.

And thank you for your precious feedback.

Thank you. I'll tag this thread "fixed". Ping me in case you see this issue again.

Yes, the present section is for the full fidelity F-5E, but it's OK. Issue reproduced and reported. Thanks for the heads up.

Please note the "General" category is not used by any aircraft. They each have their own category(ies). So if you have a controls issue with, say, your F-16C module, check controls in the "F-16C" category. If you've already checked your aircraft categories as well, start by running DCS with no devices other than the keyboard and mouse, and see if the issue persists. If the issue is gone, plug back your devices one by one.

Hi @hotstick. Can you please share you script so I can reproduce the issue?

Hi. I checked this mission but couldn't find any weapon issue for the SEAD F-4E group: F-5E > Mission > AWACS Hunt (Caucasus) If you refer to a different mission, please give us the path to the mission file.

Before you try anything else, please replay this track and tell us if you still get the Russian ATC. If you keep hearing Russian, try a DCS cleanup: https://www.digitalcombatsimulator.com/en/support/faq/709/#2463807 F-4E_English_ATC.trk

Please attach a DCS track.

Ensure your Phantom does not belong to REDFOR.

This should get fixed with the next core update.

You have exactly 0 pagefile, which is bad. 2025-04-04 19:56:07.119 INFO APP (Main): CPU cores: 8, threads: 16, System RAM: 32486 MB, Pagefile: 0 MB Either let Windows decide the size of the pagefile ("Auto" setting) or manually set a pagefile of 16GB or 32GB. Use this guide.

At last, a track. Thank you, now I can see the issue by myself. As soon as I remove the custom views in your track, the issue is gone. So please follow this guide and you won't have this issue anymore:

Don't bother, the beta test team now manage to reproduce the bug on purpose after a few minutes. Still, devs have a hard time tackling the issue.

No such issue for me. Try a DCS cleanup and repair.

Devs added more logs and tried to locate the source of the issue, without success so far. It seems to be server-side.

@beacon Unfortunately, tracks don't replay this issue, which greatly complicates debugging.

Tested in MP: Moonbeam (133 AM) "Test East" F/A-18C : OK "Test West" F/A-18C : no answer, maybe a matter of range? Hammer (144 AM) "Test East" F/A-18C : OK "Test West" F/A-18C : OK I used the fixed mission from this post of mine: