Unable to resolve radio issue - Sochi-Adler

[Nialfb]

I have a mission starting at Sochi-Adler. There are two planes set to 'Take off from ground' ... Strike Force 1 and Test-1. Using the communication menu, neither plane gets a response from ATC when requesting start-up. However, if I copy Test-1 to Gudauta (Test-2), the radio menu works fine! In the 'Triggers' menu, I use  StopGaps in the mission, but I have tested with StopGaps both enabled and disabled and it makes no difference. StopGaps is not the problem. 

If I create a new mission from Sochi-Adler and copy 'Test-1' into the mission, the radio works fine!

Any ideas?

Thanks

Su-25T Airfield Strike.miz

[Nialfb]

By the way ... If I call up the ground crew for external power supply, or if I call up ATC to announce 'Inbound' during the flight, the radio works fine!

[MAXsenna]

Have you tried with an FF module instead of FC? (You don't really specify which FC module you're using neither).

I'm thinking. Could it be a Sochi-Adler problem? 

Cheers! 

[Ironhand]

In my experience with the ME, there are times when something weird will happen. Often the best approach is to start over and you’ll find that the problem won’t be there anymore. If I get a chance a bit later (when I’m at my computer, I’ll check your mission and see if I have the same issue with it.

Edited October 9 by Ironhand

[Nialfb]

10 hours ago, MAXsenna said:

Have you tried with an FF module instead of FC? (You don't really specify which FC module you're using neither).

I'm thinking. Could it be a Sochi-Adler problem? 

Cheers! 

I'll try it.

2 hours ago, Ironhand said:

In my experience with the ME, there are times when something weird will happen. Often the best approach is to start over and you’ll find that the problem won’t be there anymore. If I get a chance a bit later (when I’m at my computer, I’ll check your mission and see if I have the same issue with it.

Yeah, this is weird. I put this mission together ages ago and it has always worked. It's only recently that I noticed the radio issue. It's not the end of the world but it would be nice to identify the issue.

[Ironhand]

29 minutes ago, Nialfb said:

I'll try it.

Yeah, this is weird. I put this mission together ages ago and it has always worked. It's only recently that I noticed the radio issue. It's not the end of the world but it would be nice to identify the issue.

The issue is with one/some of the units in the mission--either static or active. I deleted all units except for the 4 clients (Su-25Ts). Once I did, the tower started responding to the start up request. If there is a unit mod of some sort in the mission, you might try deleting that one first. I left all triggers intact. So it's definitely a unit that's corrupting the mission.

Edited October 9 by Ironhand

[Nialfb]

2 hours ago, Ironhand said:

The issue is with one/some of the units in the mission--either static or active. I deleted all units except for the 4 clients (Su-25Ts). Once I did, the tower started responding to the start up request. If there is a unit mod of some sort in the mission, you might try deleting that one first. I left all triggers intact. So it's definitely a unit that's corrupting the mission.

Thanks, I'll work through the units as you did. I don't have any mods enabled as far as I can tell, but the three SAM sites spawn randomly via a lua file - maybe they're a good suspect. Thanks for your input ... I'll report back once I figure it out. 

[Nialfb]

 Okay ... here it is, go figure! ...

There are two Russian, PAD Single, Heliports in my mission at Sochi-Adler. They have always been in the mission since I put it together some time ago because I was trying something, they're actually redundant now. I deleted the helipads and the Su-25T radio works fine! Incidently, I dropped in an Su-27 and the radio worked with or without the helipads, it was only my original mission Su-25T radio that was affected by the helipads!

My hat comes off to the mission designers who probably have to trouble shoot this stuff on a daily basis - and what worked today, might not work after the next update! How frustrating!

Su-25T Airfield Strike.miz

[Ironhand]

Good. Glad you got it sorted out. And thanks for letting us know.

[draconus]

16 hours ago, Nialfb said:

I deleted the helipads and the Su-25T radio works fine!

Good that it's working for you. Unless they were somehow designated as FARP or had their own comms vehicles I doubt that's real problem - I'd blame scripts. Otherwise how would it work with airborne aircraft calling inbound?

When I tested your mission I suspected two things but it was not that. 1. Strike-1 had no radio option ticked. 2. There was easy comms set - not needed for FC3.

Edited October 10 by draconus

[Nialfb]

2 hours ago, draconus said:

Good that it's working for you. Unless they were somehow designated as FARP or had their own comms vehicles I doubt that's real problem - I'd blame scripts. Otherwise how would it work with airborne aircraft calling inbound?

When I tested your mission I suspected two things but it was not that. 1. Strike-1 had no radio option ticked. 2. There was easy comms set - not needed for FC3.

Yes, anything is possible. I had made so many changes, anything could have been changed  I went back to my original mission and however I set communications, it did not work until I had deleted the helipads. I could delete the scripts and try to isolate an issue in one of those. It would be interesting to know.

Edited October 10 by Nialfb

[Nialfb]

I took my original mission and deleted all triggers ... still no radio until I delete the helipads!