F/A 18 Tacan on Sinai Map

[aphill]

Has anyone had a problem with the tacan in the F/A 18 not tracking the station on the Sinai map? I have not had problems on other maps just the Sinai.

Thanks

I have uploaded a test mission.

Sinia Tacan testing.trk

Sinai Tacan test.miz

Edited August 17, 2023 by aphill
add miz file

[OnReTech]

Thanks, added to the bug list. Priority - medium

[ChaosRifle]

yes. particularly 71X is problematic. I have also noticed basically all stations drift as you fly (only about 100m usually, only visible if you enable map underlay), but the 71X freq will drift up to like 50nm off target.

[Kondor77]

35 minutes ago, ChaosRifle said:

yes. particularly 71X is problematic. I have also noticed basically all stations drift as you fly (only about 100m usually, only visible if you enable map underlay), but the 71X freq will drift up to like 50nm off target.

Because there is a 71X already on the map as a tacan. You'll have to use a different tacan. 

[ChaosRifle]

32 minutes ago, Kondor77 said:

Because there is a 71X already on the map as a tacan. You'll have to use a different tacan. 

where? its not in the list on the mission editor beacons list at all, which means its not in there at all.

Edited October 31, 2023 by ChaosRifle
evidence

[sonic_NO]

Had a similar issue. As posted there is a problem with duplicate TACAN channels on this map. I think I found a fix for it: If you navigate to: 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains\Sinai

(or wherever you have your main DCS install) and open the beacons.lua file in a text editor you can see alle the beacons.

I altered the "96" value on Hatzerim to the correct "100" that caused a conflict because "96" was also used on Wadi al Jandali. The section to look for is:

display_name = _('Hatzerim');
        beaconId = 'airfield7_0';
        type = BEACON_TYPE_VORTAC;
        callsign = 'BRA';
        frequency = 114900000.000000;
        channel = 96; 
        position = { 131543.724991, 208.862773, 329208.708252 };
        direction = 104.503260;
        positionGeo = { latitude = 31.234946, longitude = 34.679870 };
        sceneObjects = {'t:361406851'};

In the section above, change channel=96; to channel=100;

Hatzerim TACAN will now be displayed correctly in the hornet (and any other aircraft that use tacan I presume)

I don't know if duplicate TACANs on this map affects all TACAN use, but its worth a try.

Tested in both multiplayer and singleplayer.

 

 

[Recoil16]

On 11/1/2023 at 10:02 PM, sonic_NO said:

Had a similar issue. As posted there is a problem with duplicate TACAN channels on this map. I think I found a fix for it: If you navigate to: 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains\Sinai

(or wherever you have your main DCS install) and open the beacons.lua file in a text editor you can see alle the beacons.

I altered the "96" value on Hatzerim to the correct "100" that caused a conflict because "96" was also used on Wadi al Jandali. The section to look for is:

display_name = _('Hatzerim');
        beaconId = 'airfield7_0';
        type = BEACON_TYPE_VORTAC;
        callsign = 'BRA';
        frequency = 114900000.000000;
        channel = 96; 
        position = { 131543.724991, 208.862773, 329208.708252 };
        direction = 104.503260;
        positionGeo = { latitude = 31.234946, longitude = 34.679870 };
        sceneObjects = {'t:361406851'};

In the section above, change channel=96; to channel=100;

Hatzerim TACAN will now be displayed correctly in the hornet (and any other aircraft that use tacan I presume)

I don't know if duplicate TACANs on this map affects all TACAN use, but its worth a try.

Tested in both multiplayer and singleplayer.

 

 

Just to be clear, while this will "fix" it in the sense that you can then use the TACAN, the problem is not actually with the Hatzerim TACAN. It is confirmed to be on 96X by Israeli Air Force documentation.

It's rather the Wadi Al Jandali TACAN that is either on the incorrect channel, or (in my opinion more likely) it should not exist at all, as there is no antenna visible on real world satellite images where the Wadi TACAN is placed in game.

So yes, while this is an interim "fix" you can do for yourself in the moment, this should not be the long term solution to be implemented for the map as a whole.

[Kondor77]

On 10/31/2023 at 10:07 AM, ChaosRifle said:

where? its not in the list on the mission editor beacons list at all, which means its not in there at all.

 

I apologize for the late response, but your snark certainly didn't help. 

 

Edited November 14, 2023 by Kondor77