Jump to content

Recommended Posts

Posted

I mean honestly. When tacan and ILS stop working entirely because the scripting engine can't manage to remember to keep them on, that's a supercarrier breaking bug. I get that it's a DCS engine problem but it's DIRECTLY impacting your brand new module, and it really really needs to be fixed after all this time.

Posted

Are you talking about the TACAN giving false indication if you fly too far away from the carrier? Until this is fixed, a temporary solution is to toggle TACAN off and on in the Hornet, when you're returning to the carrier and it should give correct indications then.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Posted

No, the TACAN bug he's referencing is the one that's been around for well over a year. Carrier TACAN just stops working - randomly - during the course of a MP mission.

Posted
just add waypoints with new activation. Boring to do but working.

 

Can you explain what you mean by this a little further please? I've run into this problem as well and would love to have a workaround.

  • 1 month later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...