Flappie

About the radio menu, I still can reach Wingman 4, and you should too. null BS3_radio.trk

According to documents I found online, the Marker Beacon Volume knob is supposed to turn off the marker beacon receiver when the volume is set to zero. Source 1: https://www.aircav.com/cobra/cockpit/pilot/vor.html Source 2: https://f4.manuals.heatblur.se/systems/nav_com/vor_ils.html (Heatblur F-4E manual) So maybe the glideslope indicator is OK, but the position indicator is bugged, after all. What do you guys think?

I was about to report this, then I read page 60 of the DCS: UH-1H manual, as you spotted it, @Volator: So it's unclear to me if the glideslope+position indicator should work at all when volume is set to zero... I'll keep investigating.

Maybe your issue comes from your WinWing MFDs:

Your antivirus claims that this DLL contains a virus, so it prevented its use, thus triggering this error 225 caught by DCS. The simplest solution is to add DCS as an exception in your antivirus.

One bug per thread, please! There's an internal reports about the absence of 4th wingman for some aircraft. I'll test then edit this report. This one was reported some months ago. Please create a new thread with a DCS track here: https://forum.dcs.world/forum/1186-ground-ai-bugs-non-combined-arms/

Please attach a short DCS track demonstrating the performance issue.

@bojote You need to update Helios.

@sinluz Si tu veux remonter un bug ici-même, il faut faire l'effort de parler anglais, comme le reste du monde. Si tu ne veux pas te donner ce mal, il y a une section francophone sur le forum, là.

If you are using Helios, ensure it is up-to-date:

@Darkgamer @jojyrocks Are you gents using Helios? If you are, ensure it is up-to-date:

Thanks for your feedback. Enjoy the sim.

It does not exist by default. You need to create it. autoexec.cfg

I'm not sure how this came into the changelog, though. It seems there were a few other errors in that changelog (B-52 weapons, for instance).

Then I have no clue what's happening to you, since your game is up-to-date. Maybe an anti-malware?

@Chesster@Moezilla Is the issue still present?

I'm able to reproduce the issue.

Thank you, all affected mission reported.

Yes. What has changed is that the missile doesn't explode in its launcher anymore. That's some progress. The explosion of the first missile close to the launcher ship is reported. That's already reported as well.

If you don't use it, ensure Force Feedback is turned off in DCS.

@equinox137 Is that Persian Gulf? If so, it could be this issue: So far, I'm unable to reproduce it. Please share a short DCS track along with your options.lua (from Saved Games/DCS/Config).

Thanks for your feedback. Modders need to update their mods so they keep working with DCS.

Have you set an exception for DCS in your antivirus?

Your issue seems to come from this error message about M61 cannon shells: 2025-03-20 22:46:41.061 ALERT APP (Main): Unhandled exception: Descriptor not found weapons.shells.M61_20_HE_gr 2025-03-20 22:46:41.061 ERROR APP (Main): Stack trace: 2025-03-20 22:46:41.061 INFO EDCORE (Main): try to write dump information 2025-03-20 22:46:41.126 INFO EDCORE (Main): # -------------- 20250320-224641 -------------- 2025-03-20 22:46:41.127 INFO EDCORE (Main): DCS/2.9.14.8222 (x86_64; MT; Windows NT 10.0.19045) 2025-03-20 22:46:41.128 INFO EDCORE (Main): 2025-03-20 22:46:41.129 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff6a5f7f471 00:00000000 My first guess would be to remove your F-15EX mod and see if that fixes your issue. 2025-03-20 22:45:26.586 ALERT Scripting (Main): loadfile: no file 'E:\Games\Saved Games\DCS\Mods/aircraft/F-15EX/Weapons/Loadouts/f15_mk-82.lua' 2025-03-20 22:45:26.590 ALERT Scripting (Main): loadfile: [string "E:\Games\Saved Games\DCS\Mods/aircraft/F-15EX/Weapons/Loadouts/..."]:391: unexpected symbol near '}' 2025-03-20 22:45:26.601 ALERT Scripting (Main): loadfile: no file 'E:\Games\Saved Games\DCS\Mods/aircraft/F-15EX/Weapons/Loadouts/f15_aim-174b.lua'

Thank you!