Going on 4 years of Carrier TACAN/ILS shutting off with no fix.

[Hawkeye91]

Can this please get more attention? I'm so sick of spending 20 minutes, setting up and flying a Case III approach only to have the carrier shut off the TACAN/ILS while I'm on a 10 mile final in the pitch black night. This is incredibly frustrating. I don't know how to force it to happen, it only seems to happen to me when Im playing multiplayer so the trackfiles would be too big and useless.

[Flappie]

This issue is reported, but as you said, big trackfiles are useless to devs, which means it's tough to reproduce internally. This probably explains why this bug is still around.

Apparently, adding a name to the TACAN emission makes the bug happen less often.

Edited January 25, 2022 by Flappie
typos

[Hawkeye91]

Just now, Flappie said:

This issue is reported, but as you said, big trackfiles are useless to devds which means it's tough to reprodue internally. This probably explain why this bug is still around.

Apparently, adding a name to the TACAN emission makes the bug happen less often.

I figured it was, but I want to draw attention to it so it doesn't get ignored. It is EXTREMELY frustrating. How are you supposed sim a case III properly when this happens all the time? This is a basic functionality that should just work properly. Its not a complex system and having instrument navigation equipment is the basic foundation of any flight sim, military or civilian that should just work. These basic things should be top priority because it comes down to, if the basics don't work, everything else is pointless. 

[Jakko]

29 minutes ago, Hawkeye91 said:

Can this please get more attention? I'm so sick of spending 20 minutes, setting up and flying a Case III approach only to have the carrier shut off the TACAN/ILS while I'm on a 10 mile final in the pitch black night. This is incredibly frustrating. I don't know how to force it to happen, it only seems to happen to me when Im playing multiplayer so the trackfiles would be too big and useless.

as a work-around i reactivate the TACAN in my mission every 20 minutes. for this i use "moose".
this is how it works for me.

 

local Washington = UNIT:FindByName("CVN-73 Washington")
local WashingtonBeacon = Washington:GetBeacon()

local TimerTacan = TIMER:New(
function()

    WashingtonBeacon:ActivateTACAN(73, "X", "WSH", true)
    WashingtonBeacon:ActivateICLS(13, WSH)

end
)

TimerTacan:Start(10, 1200)                          -- Tacan re-activte every 1200 seconds

[Hawkeye91]

2 minutes ago, Jakko said:

as a work-around i reactivate the TACAN in my mission every 20 minutes. for this i use "moose".
this is how it works for me.

 

local Washington = UNIT:FindByName("CVN-73 Washington")
local WashingtonBeacon = Washington:GetBeacon()

local TimerTacan = TIMER:New(
function()

    WashingtonBeacon:ActivateTACAN(73, "X", "WSH", true)
    WashingtonBeacon:ActivateICLS(13, WSH)

end
)

TimerTacan:Start(10, 1200)                          -- Tacan re-activte every 1200 seconds

They do this on Hoggit too but if it shuts its TACAN/ICLS off just after a reset, you're S.O.L. for a long time.

[Jakko]

4 minutes ago, Hawkeye91 said:

They do this on Hoggit too but if it shuts its TACAN/ICLS off just after a reset, you're S.O.L. for a long time.

i have not noticed any downtime with my 20 minutes interval. i do not know the interval of hoggit.
maybe i've just been lucky so far.

[norman99]

On the 4YA servers, using the F10 menu to display Carrier & Tanker frequencies (TACAN, ILS & Comm) also restarts the TACANs. I think this manual reactivation method is a better solution and seems more reliable.

[Bankler]

It's super annoying. My best advice until they fix it is to setup a template mission with the functionality to manually reset it. And whenever you build a mission, build it on top of that template. It's frustrating that you need to do this, but at least it works.

 

[Hawkeye91]

4 hours ago, Bankler said:

It's super annoying. My best advice until they fix it is to setup a template mission with the functionality to manually reset it. And whenever you build a mission, build it on top of that template. It's frustrating that you need to do this, but at least it works.

 

Thanks for the work around, but I generally don't play SP missions. I'm usually on Hoggit or TTI online and I'm at the mercy of server admins to put these fixes into the server. I thought they had them, but I still end up getting the problem. Seems like they're down at least 25% of the time I try to use them. 

[Bankler]

9 hours ago, Hawkeye91 said:

Thanks for the work around, but I generally don't play SP missions. I'm usually on Hoggit or TTI online and I'm at the mercy of server admins to put these fixes into the server. I thought they had them, but I still end up getting the problem. Seems like they're down at least 25% of the time I try to use them. 

Aah, got it. I'm not doing SP either, but our missions are played on our own server, so we have the opportunity to fix it ourselves. My best suggestion then, would be to make the admins of those servers aware of the work-around and point them in the direction of that post. There are timer based automatic solutions, and I'm sure some of the public servers use those, but just like you said, it won't help if TCN and/or ICLS dies when you're on final. Then you need the panic button to fix it yourself.

Edited January 27, 2022 by Bankler