Tusky Posted December 23, 2023 Posted December 23, 2023 (edited) Hi all! While creating a mission, I noticed that there's a discrepancy or omission between the tanker's callsign assigned in the Mission Editor and the one displayed in the SA page when EPLRS is activated in the tankers. When a KC-135 is involved: - Arco X-X >>> Texaco 1-1 (TX11) - Shell X-X >>> Texaco 1-1 (TX11) - Texaco X-X >>> Enfield 1-1 (ED11) When a KC-135MPRS is involved, no callsign is displayed. In the missions run from the attached files I used for testing, all tankers are shown as "donors" in the SA page. Maybe I'm doing something wrong? Thank you! Test DL16 C-135.miz Test DL16 C-135MPRS.miz Edited December 23, 2023 by Tusky 2
Tusky Posted December 26, 2023 Author Posted December 26, 2023 (edited) Ok, I figured it out: in the AIRCRAFT ADDITIONAL PROPERTIES tab, the "Voice Callsign Label" and "Voice Callsign Number" should be manually set to match the flight's callsign. What I've noticed though is that sometimes the two Voice Callsign fields do match the callsign correctly (e.g. -2 and on) whereas sometimes they don't (most of the time, the leader). In the mission I am working on, the E-2D had it wrong (a default TO11) but the E-3A had it correct (Magic 1-1 > MC11). Shouldn't there be a consistency thoughout the units? Edited December 26, 2023 by Tusky
Solution rob10 Posted December 26, 2023 Solution Posted December 26, 2023 Have you changed the callsign for those units? Currently the info in that tab defaults to whatever the Callsign is when you place the unit and don't update when you change it. Would that make sense to what you're seeing? Definitely a pain. 1
Tusky Posted December 27, 2023 Author Posted December 27, 2023 hace 29 minutos, rob10 dijo: Have you changed the callsign for those units? Currently the info in that tab defaults to whatever the Callsign is when you place the unit and don't update when you change it. Would that make sense to what you're seeing? Definitely a pain. Yes, I changed the callsign after placing the unit... Thank you for the heads-up!
Recommended Posts