Jump to content

Changing "Activate TACAN" option sets Channel Mode to X


Recommended Posts

image.png

TCNTestED.miz

I've included a mission featuring three tankers to represent the stages of this issue, and in this case have only adjusted the "Unit" option, but this bug occurs when adjusting Channel, Callsign, or Unit on this panel. Regardless of the Channel Mode setting, changing any one of these options in the TACAN options will force the Channel Mode to X while it visibly remains on Y. Checking the unpacked mission file from the .miz, "modeChannel" appears to remain on Y for all three tankers as well. While the below uses the Unit option, the same trick to re-enable it applies for all options in my testing.

 

- In the mission for Tanker "Aerial 3" I set the Channel to 1Y, then assigned Unit to "Aerial-3-1". When loading the mission, range info will only appear on TACAN 1X despite still showing as 1Y in the panel.

 

- I similarly changed the Unit on "Aerial 4", which was set to Channel 37Y, but after unit selection I toggled the Channel Mode back to X, then re-selected Y. It now broadcasts range correctly on channel 37Y.

--- I also further tested 37Y by changing the unit back to the default "Nothing," and it would again only broadcast on 37X until I toggled the Channel Mode again.

 

- Lastly for a control I changed the Channel to 40, then set mode Y for "Aerial 5" and did not set a unit at all. This tanker correctly broadcasts range on 40Y upon load.

 

I'd be happy to provide any further details. Thanks for your time.


Edited by JCofDI
Words go poof.
Link to post
Share on other sites
  • JCofDI changed the title to Changing "Activate TACAN" option sets Channel Mode to X

Did some further testing inside the mission file of the unpacked .miz today. I noticed that the only notable difference among the "Activate Beacon" section appeared to be the "system" flag. Here's the full portion of that action from "TCNTestED" in the first post. This tanker gives correct range info on the Y mode. Notice that the `system` flag is set as 5.

["id"] = "ActivateBeacon",
["params"] = 
{
    ["type"] = 4,
    ["AA"] = true,
    ["callsign"] = "TKR",
    ["modeChannel"] = "X",
    ["name"] = "Action Created, No Unit Ever Set",
    ["channel"] = 40,
    ["system"] = 5,
    ["bearing"] = true,
    ["frequency"] = 1127000000,

 Looking at the section for the tanker on channel 1Y which did not correctly broadcast range, I noticed that the `system` flag was set to 4.

With changing no other variables I set this flag to 5 and repackaged the mission, which correctly gave range info on channel 1Y. Conversely, I can put the system flag to  4 on correctly working tankers and they will exhibit the same "Default to X" mode behavior on their respective channels.

 

The attached .miz is of the same mission as the original post, with only the system flags for each tanker set to the "opposite" of what it was in the original mission, and the results are likewise exactly opposite. 1Y is the only correctly behaving tanker in TCNTestEdit, while 37Y and 40Y only show range info on the X TACAN.

 

Hope this helps.

TCNTestEdit.miz

Link to post
Share on other sites

Hi

 

we have this issue already reported.

 

It happens with  KC-135MPRS

 

thank you

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 10 Pro x64, NVIDIA MSI RTX 2080Ti VENTUS GP, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 32GB DDR @3000, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to post
Share on other sites
16 hours ago, BIGNEWY said:

Hi

 

we have this issue already reported.

 

It happens with  KC-135MPRS

 

thank you

Thanks for the response, BN.

 

I believe that the issue is a full tanker-wide issue however. Here's a KC-130 exhibiting the same results, caused using the same steps.

image.png

image.png

The unpacked mission file again shows the "System" flag set to 4 with this KC-130.

 

Thanks for your time.

 

Link to post
Share on other sites

I have marked this report earlier, the team do have a report and investigation open internally.

 

thank you

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 10 Pro x64, NVIDIA MSI RTX 2080Ti VENTUS GP, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 32GB DDR @3000, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...