Nialfb Posted Tuesday at 06:32 PM Posted Tuesday at 06:32 PM 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 Game setup - I9-13900K, 3000 MHz 24 Core 32 Logical Processors, NVIDIA RTX 4090, 42” ASUS 4K OLED monitor, TM HOTAS Warthog, TM TPR Rudder pedals, Bigscreen Beyond VR.
Nialfb Posted Wednesday at 08:29 AM Author Posted Wednesday at 08:29 AM 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! Game setup - I9-13900K, 3000 MHz 24 Core 32 Logical Processors, NVIDIA RTX 4090, 42” ASUS 4K OLED monitor, TM HOTAS Warthog, TM TPR Rudder pedals, Bigscreen Beyond VR.
MAXsenna Posted 22 hours ago Posted 22 hours ago 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 Posted 14 hours ago Posted 14 hours ago (edited) 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 13 hours ago by Ironhand YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 11 Pro x64, Asrock Z790 Steel Legend MoBo, Intel i7-13700K, MSI RKT 4070 Super 12GB, Corsair Dominator DDR5 RAM 32GB.
Nialfb Posted 11 hours ago Author Posted 11 hours ago 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. Game setup - I9-13900K, 3000 MHz 24 Core 32 Logical Processors, NVIDIA RTX 4090, 42” ASUS 4K OLED monitor, TM HOTAS Warthog, TM TPR Rudder pedals, Bigscreen Beyond VR.
Ironhand Posted 11 hours ago Posted 11 hours ago (edited) 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 11 hours ago by Ironhand YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 11 Pro x64, Asrock Z790 Steel Legend MoBo, Intel i7-13700K, MSI RKT 4070 Super 12GB, Corsair Dominator DDR5 RAM 32GB.
Nialfb Posted 9 hours ago Author Posted 9 hours ago 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. Game setup - I9-13900K, 3000 MHz 24 Core 32 Logical Processors, NVIDIA RTX 4090, 42” ASUS 4K OLED monitor, TM HOTAS Warthog, TM TPR Rudder pedals, Bigscreen Beyond VR.
Nialfb Posted 5 hours ago Author Posted 5 hours ago 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 Game setup - I9-13900K, 3000 MHz 24 Core 32 Logical Processors, NVIDIA RTX 4090, 42” ASUS 4K OLED monitor, TM HOTAS Warthog, TM TPR Rudder pedals, Bigscreen Beyond VR.
Ironhand Posted 3 hours ago Posted 3 hours ago Good. Glad you got it sorted out. And thanks for letting us know. YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg _____ Win 11 Pro x64, Asrock Z790 Steel Legend MoBo, Intel i7-13700K, MSI RKT 4070 Super 12GB, Corsair Dominator DDR5 RAM 32GB.
Recommended Posts