MTSection

Hi Bones and thank you for your reply! I completely agree with all your considerations. You can easily replicate the problem I encountered by following these steps: select any map and open it from mission editor spawn any carrier and set its tacan (in my case I chose CVN-75 and set the tacan 75X) spawn a tanker and set its tacan (in my case 36Y) spawn an F14 and set it as "player" start the flight immediately in the cockpit (you will spawn in the air), we will find the tacan automatically set to 36Y; the moment you try to enter 75X, however, the range will remain "frozen" for a moment and then disappear until the carrier is about 19/20 nm away. Please let me know if you also get the same result, if you have the time and the will, of course. Thank you!

Have you noticed any changes in the normal functioning of the F14 tacan after the 2.9 update? It seems to me that by setting a different channel, and then returning to the carrier one, the tacan no longer seems to work (no range or direction information). On the other hand, it seems to work properly with other modules..

Yep I was aware of that function before writing and i totally agree that it would be much more realistic, my question was all about the difference of coordinates. Thanks and have a great day!

Thank you very much @MARLAN_ and @Tholozorthis was exactly the info i was looking for!

Hi, I searched for this information but did not find anything.. Using module F/A-18C with any targeting pod: I can see the target coordinates but if i write these down and when trying to insert them as gps coordinates for a strike (Jdam, Jsow ecc..) it says "ERROR" on UFC. I noticed that the pod coordinates are a bit different from the map precise coordinates. Can you please explain me why? Thanks