Odessa Posted January 22, 2023 Posted January 22, 2023 (edited) Good day Test case: Kobuletti. When I create a mission with "Take off ... hot" - everything is OK, radio works. When I create a mission with "cold start" - radio does not work. Actually I can hear but cannot transmit So if I start moving ATC will tell "Cleared for taxi..." and then I can hear all other their commands. But they cannot hear me. So when I ask "Request to startup" - nothing. No mods. Edited January 22, 2023 by Odessa Added "No mods"
razo+r Posted January 22, 2023 Posted January 22, 2023 Are you using the correct key combination to transmit with the correct radio? Can you give a track?
Odessa Posted January 22, 2023 Author Posted January 22, 2023 (edited) 2 hours ago, razo+r said: Are you using the correct key combination to transmit with the correct radio? Can you give a track? I will prepare track later today but actually there is nothing in that track. Mission "hot start up" started=> setup frequency=>call ATC-=>got response Mission "cold start up" started=> battery ON=> Inverter On=> setup a frequency=> call ATC=>silence=>start moving=>hear ATC but still cannot transmit I use the same button for both cases: cold and hot starts. Update - Module itself is OK I think. My apologies. I can use radio in my hand-made "cold start "mission and in mission from some campaign. I found that APU should be switched ON for that. Radio does not work from battery only. But still have issue in attached track - it is mission from "The Enemy Within 3" campaign Thank you glitch.trk Edited January 22, 2023 by Odessa
Yurgon Posted January 22, 2023 Posted January 22, 2023 Thanks for the track. In this particular mission, I see the same behavior, and in a fresh mission, Kobuleti responds as expected. I've filed a bug report with Baltic Dragon. The entire campaign The Enemy Within 3.0 is undergoing an overhaul right now, mostly because there are known radio issues. I'm not sure if this is one of them, but in either case I've alerted BD about it. It's probably best to give BD some time and wait for the updated version. All this used to work fine when the campaign was released and for a long time after release. Now there's been a change outside of the campaign, hence the need to update it. 1 1
Odessa Posted January 23, 2023 Author Posted January 23, 2023 11 hours ago, Yurgon said: Thanks for the track. In this particular mission, I see the same behavior, and in a fresh mission, Kobuleti responds as expected. I've filed a bug report with Baltic Dragon. The entire campaign The Enemy Within 3.0 is undergoing an overhaul right now, mostly because there are known radio issues. I'm not sure if this is one of them, but in either case I've alerted BD about it. It's probably best to give BD some time and wait for the updated version. All this used to work fine when the campaign was released and for a long time after release. Now there's been a change outside of the campaign, hence the need to update it. Thanks for quick response. Could you please clarify one more question? If BD will prepare the upgrade\fix of campaign then how I will get it? Will I have to do anything manually like download and replace some files or it will be normal DCS World upgrade?
Solution Yurgon Posted January 23, 2023 Solution Posted January 23, 2023 40 minutes ago, Odessa said: If BD will prepare the upgrade\fix of campaign then how I will get it? Campaign updates come through the DCS Updater; that'll be part of a DCS update and you'll be offered to install it as soon as it becomes available. In case you run DCS through Steam, it'll even auto-update in the background as soon as Steam detects a new version. But don't ask me how long it'll take to update The Enemy Within; I think BD is right on it, but it may still take a while. 1 1
Recommended Posts