Nealius Posted August 7, 2024 Posted August 7, 2024 (edited) In the ME Kandahar's UHF is listed as 300.20, which does not function. F10 map info and functioning UHF is 360.20. Updated title; Clicking on Kandahar airfield in the ME shows heliport info. Clicking on the airfield in F10 map shows airfield info as it should. Edited August 7, 2024 by Nealius
Minsky Posted August 7, 2024 Posted August 7, 2024 23 minutes ago, Nealius said: In the ME Kandahar's UHF is listed as 300.20, which does not function. F10 map info and functioning UHF is 360.20. Sure you're not confusing Kandahar aerodrome (UHF 360.20) and Kandahar Heliport (UHF 300.20) ? Dima | My DCS uploads
Nealius Posted August 7, 2024 Author Posted August 7, 2024 (edited) 17 minutes ago, Minsky said: Sure you're not confusing Kandahar aerodrome (UHF 360.20) and Kandahar Heliport (UHF 300.20) ? That seems to be part of the problem. Clicking on Kandahar (TACAN area) causes the heliport info to pop up instead of the airfield info. In the F10 map they're properly separated. Edited August 7, 2024 by Nealius
Nealius Posted August 7, 2024 Author Posted August 7, 2024 (edited) Appears to be a "hitbox" issue. The hitbox for the heliport is in red, airfield in blue. The heliport hitbox is prioritized over the airfield hitbox, and covers a majority of the airfield. This hitbox does not exist on the F10 map. This is also affecting radio usage, as spawning anywhere on the ramp within the red circle results in being unable to contact ATC on 360.20, while spawning outside the red circle works fine. Edited August 7, 2024 by Nealius
Nealius Posted August 8, 2024 Author Posted August 8, 2024 Good news is I figured out the comms issue: If you spawn on ramps November, Oscar, Sierra, Yankee, or Zulu, the comms tree defaults to the heliport as the F1 entry. Voice Attack profiles are programmed to press F1 as that should always be your spawn airfield.
Recommended Posts