Tanker TACAN on Mouse Tooltip
-
Version: 4.36.3 (x64)
Build 26590
Detailed Description
The mouse hover tooltip on the campaign map shows the tanker flight TACAN channel with the 63 offset while the in-game briefing tells the actual TACAN channel of the tanker aircraft.Pictures
An example picture of the linked TE. The discrepancy appears on campaigns too.
Example files
An example TE: https://drive.google.com/file/d/19qTiqPaeO9GNwyN_pZ4X0swaGdri0Gnx/view?usp=share_linkCrash logs
Not applicableReproducibility Procedure
- Create an empty TE.
- Add a tanker flight into the TE. Tanker aircraft type doesn’t seem to matter: I’ve seen this with the KC-135R and the KC-10.
- Add a fighter flight to the TE nearby the tanker station area.
- Check the fighter flight briefing. The tanker TACAN should be correct.
- Hover the mouse over the tanker aircraft on the campaign map. The TACAN channel on the mouse tooltip should show the TACAN with the 63 offset compared to the in-game briefing of the fighter flight.
Expected Behavior
Shouldn’t the tanker flight TACAN show the same channel i.e. the actual TACAN channel of the tanker aircraft everywhere throughout the UI?Lastly, pardon my ignorance if this has been reported already.
-
-
This issue exists still in BMS 4.37.1 (x64) build 451. Here’s a screenshot from the Falcon Online Battle for Lapland online campaign. The issue can be easily reproduced in the default KTO theater too as described in the opening post.
-
-
Not a bug per say but more a decision to make internally if we want the reciever part or the emitting part…
-
@MaxWaldorf
Would you not like the transmitting channel on the UI map?You plan a flight, several tankers available, would be nice to just have the TACAN channel by looking on the map. What would you need the recieving channel for (from an flying point of view)
I didnt actually notice that it was the offset between them. I just noted the UHF freq for the tankers. Is it the transmitting or recieving you get from the AWACS when you call for an tanker thats not the one in your briefing? (never checked that out)
-
@Guard_85
Awacs always return “real” (input) tacan. Since… forever@MaxWaldorf
while at it … I’ve noticed strange tacan when asking for fleet location09:23:00: Dragnet 3 Dog 8-1 request vector to carrier group 09:23:02: Dog 8 Dragnet 3 carrier group bearing 1-9-0 40 miles TACAN channel 9-2 Yankee
Wasp tacan is set to 15X so it’s not that
92Y could be - don’t know
now … when better look at it… even bullseye loc is wrong , fleet is at 214/175 (at beginning of the mission) and imho it couldn’t get that far in matter of 1h, 1h1/2… also that loc is on landok , got it … 190/40 is Udbina airport , Balkans theater… but it has no tacan (001 X 0 - range)
maybe is something with theater… need to investigate more
But nevertheless - awacs fleet calls are erroneous -
@white_fang bearing refers to your position. It is not a bullseye call, if I am not mistaken.
-
@Le_Beau
Aw… fck it. You’re right. It was a BRAA. (no bullseye word in response).Ok… need to correct that above…
But still Tacan is wrong. Probably reading wrong variable.
Cheers