McCallaway Posted March 19 Share Posted March 19 If an aircraft group has a callsign with a flight number on multiple digits, interactions with AI ATC/AWACS/Tankers wont work correctly, or at all. Not necessarily a big deal, though in some cases this seems to cause problems to activate a tanker or get info from an AWACS. For example: With test aircraft is an F-14B plopped in a empty mission, cold at the ramp in Anapa. Test procedure is to plug external power, turn on the radio on 250 (Anapa frequency) and requesting startup. Results are as follow: Callsign Enfield-9-1 => message out is spoken as Enfield-9-1 => Anapa answers with audio Callsign Enfield-10-1 => message out Enfield-1-1 => Anapa answers with audio Callsign Enfield-19-1 => message out Enfield-9-1 => Anapa answers with audio Callsign Enfield-20-1 => message out Uzi-1-1 => Anapa answers with audio Callsign Enfield-50-1 => message out Ford-1-1 => Anapa answers with audio Callsign Enfield-75-1 => message out Pontiac-5-1 => Anapa answers with audio Callsign Enfield-79-1 => message out Pontiac-9-1 => Anapa answers with audio Callsigns with flight number over 80 (tested with Enfield-80-1, Enfield-81-1, Enfield-99-1, Enfield-100-1, Enfield-101-1) => there is no message out ==> Anapa responds with no audio (only text is shown). It's in this last case that some users reported inability to interact with a tanker. Toutes les grandes personnes ont d'abord été des enfants, mais peu d'entre elles s'en souviennent. Three Point Landing Link to comment Share on other sites More sharing options...
McCallaway Posted March 21 Author Share Posted March 21 SO far we have observed the issue with: => F-14A ; F-14B ; F-15C ; Mirage 2000C ; MiG-29S ; Mirage F1BE ; Mirage F1CE ; Mirage F1EE ; SU-25T ; SU-33 ; A-10C II Strangely, the F/A-18C doesn't seem affected. Other airframes not tested. Toutes les grandes personnes ont d'abord été des enfants, mais peu d'entre elles s'en souviennent. Three Point Landing Link to comment Share on other sites More sharing options...
Solution McCallaway Posted April 12 Author Solution Share Posted April 12 (edited) So apparently this was corrected in todays hotfix under "Error in wMessage::buildSpeech() ("F-15E - Communication issues with high-digit call signs, support high digits callsigns)". Tested it in the F-14B as well. And in the F/A-18 even though it was almost ok already. I'm talking to myself but oh well. Edited April 12 by McCallaway 1 Toutes les grandes personnes ont d'abord été des enfants, mais peu d'entre elles s'en souviennent. Three Point Landing Link to comment Share on other sites More sharing options...
Flappie Posted April 12 Share Posted April 12 1 hour ago, McCallaway said: I'm talking to myself but oh well. No, you're not. Thanks for your feedback. 1 Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Recommended Posts