Sierra99 Posted April 1, 2015 Posted April 1, 2015 Gentlemen... Does anyone know if fixing the AWACS callsign issue is on EDs radar or was it lost in the shuffle? As of right now, AWACS callsigns work out like this: OVERLORD - ENFIELD MAGIC - SPRINGFIELD WIZARD - UZI FOCUS - COLT DARKSTAR - DODGE it almost looks like it is using the A-10C callsigns for AWACS callsigns. ANYWAY... I'll just leave this here.:music_whistling: [sIGPIC][/sIGPIC] Primary Computer ASUS Z390-P, i7-9700K CPU @ 5.0Ghz, 32GB Patriot Viper Steel DDR4 @ 3200Mhz, ZOTAC GeForce 1070 Ti AMP Extreme, Samsung 970 EVO M.2 NVMe drives (1Tb & 500 Gb), Windows 10 Professional, Thrustmaster Warthog HOTAS, Thrustmaster Warthog Stick, Thrustmaster Cougar Throttle, Cougar MFDs x3, Saitek Combat Rudder Pedals and TrackIR 5. -={TAC}=-DCS Server Gigabyte GA-Z68XP-UD3, i7-3770K CPU @ 3.90GHz, 32GB G.SKILL Ripjaws DDR3 @ 1600Mhz, ZOTAC GeForce® GTX 970.
Grimes Posted April 1, 2015 Posted April 1, 2015 What do you mean? Is there a bug with AWACs identifying as Enfield or something? Callsigns are all indexed as enumerators starting at 1. So there is some overlap. Overlord, enfield, texeco and axeman all have an ID of 1, but depending on the type of unit using the callsign it will select whichever callsign is appropriate. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
Exorcet Posted April 1, 2015 Posted April 1, 2015 What do you mean? Is there a bug with AWACs identifying as Enfield or something? Yes. Awaiting: DCS F-15C Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files
Grimes Posted April 1, 2015 Posted April 1, 2015 Hmm, it seems the allied flight dialog isn't using the correct callsign when doing normal "allied flight" communications. When communicating via the awacs and tanker radio menu they are using the right callsign. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
Sierra99 Posted April 2, 2015 Author Posted April 2, 2015 Hmm, it seems the allied flight dialog isn't using the correct callsign when doing normal "allied flight" communications. When communicating via the awacs and tanker radio menu they are using the right callsign. EXACTLY! :huh: Wait...what'd you say? I actually figured this was a known issue since it doesn't appear to be I'll elaborate. I selected the Callsign Magic for an E3C. In game...when the E3 makes radio calls or responds a query...it uses the callsign Springfield. The table I included with my first post was lists what was selected and what happens in game. I actually expected to be told it was a known issue... Color me suprised. Thanks for the help grimes [sIGPIC][/sIGPIC] Primary Computer ASUS Z390-P, i7-9700K CPU @ 5.0Ghz, 32GB Patriot Viper Steel DDR4 @ 3200Mhz, ZOTAC GeForce 1070 Ti AMP Extreme, Samsung 970 EVO M.2 NVMe drives (1Tb & 500 Gb), Windows 10 Professional, Thrustmaster Warthog HOTAS, Thrustmaster Warthog Stick, Thrustmaster Cougar Throttle, Cougar MFDs x3, Saitek Combat Rudder Pedals and TrackIR 5. -={TAC}=-DCS Server Gigabyte GA-Z68XP-UD3, i7-3770K CPU @ 3.90GHz, 32GB G.SKILL Ripjaws DDR3 @ 1600Mhz, ZOTAC GeForce® GTX 970.
feefifofum Posted April 2, 2015 Posted April 2, 2015 I just stuck the first on-comm AWACS in my campaign, and was wondering about this thanks! THE GEORGIAN WAR - OFFICIAL F-15C DLC
DarkFire Posted April 2, 2015 Posted April 2, 2015 Out of interest, does anyone know what names the Russian AF assigns to their A-50 flights? System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit. Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.
Belgeode Posted April 2, 2015 Posted April 2, 2015 Out of interest, does anyone know what names the Russian AF assigns to their A-50 flights? AFAIK They don't use names... Only numbers (example 150). [sIGPIC][/sIGPIC] YouTube ~ Twitch
DarkFire Posted April 3, 2015 Posted April 3, 2015 AFAIK They don't use names... Only numbers (example 150). I thought that might be the answer. Is there a standard number for an operating AWACS flight, like 100 or something? Having the operating A-50 as flight 100 would make more sense than a random aircraft being so designated, i.e. the player. System Spec: Cooler Master Cosmos C700P Black Edition case. | AMD 5950X CPU | MSI RTX-3090 GPU | 32GB HyperX Predator PC4000 RAM | | TM Warthog stick & throttle | TrackIR 5 | Samsung 980 Pro NVMe 4 SSD 1TB (boot) | Samsung 870 QVO SSD 4TB (games) | Windows 10 Pro 64-bit. Personal wish list: DCS: Su-27SM & DCS: Avro Vulcan.
Belgeode Posted April 3, 2015 Posted April 3, 2015 From what I have seen creating aircraft, the default number for the first Russian Air unit placed is 100, and then it goes up from there. There is no real special treatment given to the type of aircraft it is, so as long as you placed the A-50 first, by default it would get callsign 100. Pretty much once a number is taken it goes with the next in numerical order from 100. [sIGPIC][/sIGPIC] YouTube ~ Twitch
Sierra99 Posted April 3, 2015 Author Posted April 3, 2015 Hmm, it seems the allied flight dialog isn't using the correct callsign when doing normal "allied flight" communications. When communicating via the awacs and tanker radio menu they are using the right callsign. So Grimes... Is there a work around/ fix or is this bug that'll be squashed in due time? [sIGPIC][/sIGPIC] Primary Computer ASUS Z390-P, i7-9700K CPU @ 5.0Ghz, 32GB Patriot Viper Steel DDR4 @ 3200Mhz, ZOTAC GeForce 1070 Ti AMP Extreme, Samsung 970 EVO M.2 NVMe drives (1Tb & 500 Gb), Windows 10 Professional, Thrustmaster Warthog HOTAS, Thrustmaster Warthog Stick, Thrustmaster Cougar Throttle, Cougar MFDs x3, Saitek Combat Rudder Pedals and TrackIR 5. -={TAC}=-DCS Server Gigabyte GA-Z68XP-UD3, i7-3770K CPU @ 3.90GHz, 32GB G.SKILL Ripjaws DDR3 @ 1600Mhz, ZOTAC GeForce® GTX 970.
Recommended Posts