Volator Posted January 15, 2024 Posted January 15, 2024 (edited) When you call GCI/AWACS for a vector to homeplate in a Blufor aircraft with English ATC, GCI/AWACSwill erronously give the location of the homeplate in relation to bullseye, which of course is always the same. You do not get a vector. In Soviet/Russian aircraft with Russian ATC this works perfectly fine, you get the vector as required. Track shows the bug. Creech AFB is Bullseye, Nellis AFB is homeplate, aircraft is east of Nellis. Vector should be something like 270°, but GCI always just gives "bulls 124 for 34", which is from Bullseye to Nellis AFB. Test_vector_to_homeplate.trk Edited January 15, 2024 by Volator 1./JG71 "Richthofen" - Seven Eleven
Flappie Posted January 30, 2024 Posted January 30, 2024 I have no knowledge about all this, but according to Hoggit's wiki, what you witnessed with Blufor is normal: Quote Vector to home plate The AWACS will provide the player with a bearing and range from bullseye to their home airfield ---
Volator Posted January 30, 2024 Author Posted January 30, 2024 6 minutes ago, Flappie said: what you witnessed with Blufor is normal Hm, then it shouldn't be called "Vector to homeplate", as it doesn't provide a vector. Also, what's the point of giving the location of the homeplate in relation to Bullseye? It's always the same, and I know where my homeplate is in relation to Bullseye. Since it works properly for REDFOR and ATC seems not to differentiate between BLUEFOR and REDFOR except for language, plus it doesn't make sense in the way it works here, I thought it must have been a bug. But I guess the revamped ATC is around the corner, right? 1 1./JG71 "Richthofen" - Seven Eleven
Flappie Posted January 30, 2024 Posted January 30, 2024 It could be a very old bug or a feature. I'll ask. 1 ---
Recommended Posts