buur Posted June 11, 2022 Posted June 11, 2022 If you add an EWR in mission editor the EWR has the callsign from the JTAC. When you contact the EWR you get the answer from an AWACS callsign. If you use a JTAC callsign which not correspondents to an AWACS callsign the EWR is broken. Axeman → Overlord Darknight → Magic Warrior → Wizzard Pointer → Focus Eyeball → Darkstar Moonbeam → EWR not working Whiplash → EWR not working ...
Hairdo1-1 Posted January 13, 2023 Posted January 13, 2023 A while back a bunch of callsigns got added to the ME. However when they are used there is just a gap in the radio comms. It’s been so long that I guess someone forgot about them so I thought I’d put it in here 1
Gierasimov Posted January 15, 2023 Posted January 15, 2023 Best to wait for the ATC overhaul that was mentioned few times will also influence other flights comms. I think there was a comment once that there is also a plan to redo callsigns. Maybe the new callsigns were added to support that development effort but it is simply not ready yet. 1 Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
riojax Posted April 3, 2023 Posted April 3, 2023 (edited) The EWR callsign is "Eyeball" in the F10 radio menu all is ok, but later it calls as "Darkstar" ewr2.trk Edited April 3, 2023 by riojax
ED Team BIGNEWY Posted April 4, 2023 ED Team Posted April 4, 2023 threads merged 1 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
riojax Posted April 24, 2023 Posted April 24, 2023 (edited) Latest OB 2.8.4.39313 is still ignoring the callsign in reply (only says "one") Edited April 24, 2023 by riojax 1
Recommended Posts