Eagle7907 Posted June 6, 2019 Posted June 6, 2019 (edited) Something strange with flight callsigns. I have a mission flying the Hornet with the callsign assigned for flight as Chevy 4-1. (AWACS) Wizard and Axeman (JTAC) calls me 7-4-1. ???? Sent from my iPhone using Tapatalk Pro Edited June 6, 2019 by Eagle7907 Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer
Harker Posted June 6, 2019 Posted June 6, 2019 I'm Dodge 1-1 and they call me 5-1-1. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Grimes Posted June 6, 2019 Posted June 6, 2019 Appears to correspond with the number Id associated with those callsigns. 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
Harker Posted June 6, 2019 Posted June 6, 2019 Interestingly enough, when I use Voice Attack with VAICOM, I get the correct callsign The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Eagle7907 Posted June 7, 2019 Author Posted June 7, 2019 Interestingly enough, when I use Voice Attack with VAICOM, I get the correct callsign I just flew the tomcat and the callsigns with it are correct. Sent from my iPhone using Tapatalk Pro Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer
Wesjet Posted June 7, 2019 Posted June 7, 2019 Flew a Hornet last night and both my pilot and the ATC called out as 7-1-1. Some parts came through with the new voice from the updated carrier ATC. A friend in a F-14 correctly called out as and got a reply as Pontiac 1-1, but he did hear my call as 7-1-1 and the altered voice too. My Rig: CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz. Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD. Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.
Ironwulf Posted June 7, 2019 Posted June 7, 2019 Wouldn't be the board number would it? The voice sounds a lot like the one in the carrier comms update demo'd by wags
Harker Posted June 7, 2019 Posted June 7, 2019 Wouldn't be the board number would it? The voice sounds a lot like the one in the carrier comms update demo'd by wags I thought it might be related, but my board number was 317 and I got called 5-1-1. During a carrier approach later, it correctly used 317 for carrier comms. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
ED Team NineLine Posted June 7, 2019 ED Team Posted June 7, 2019 Some of the new carrier comms managed to leak out into this build, it will be fixed. Thanks for the report. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Recommended Posts