Penecruz/VAICOMPRO-Community

[BUG] Latest DCS update seems to have broken Link Host command

Opened this issue · 14 comments

l-e-o commented

Describe the bug
I have been practicing ACL with the F-14 last week. After the recent DCS update, I didn't understand why the ACL needles weren't activating properly after I issued the commands to Jester, "TACAN Tune ..." and "Link Host ..." despite Jester acknowledging the commands. The ACL needles on the HUD and VDI remained perfectly centered. I then tried communicating with Jester without VAICOM and the needles behaved as expected. I suspect the "Link Host ..." command is now broken. The "TACAN Tune ..." command works fine still.

To Reproduce
Using VAICOM to ask Jester to "Link Host ..." Jester acknowledges, configure the aircraft (F-14) for ACL and the needles in the HUD and VDI are perfectly aligned. Issue the same command to Jester using the Jester wheel (VAICOM off) and configuring the aircraft for ACL and the neddles appear off centre as expected.

Expected behavior
"Link Host ..." command should perform the same as asking Jester to tune the Data Link to the Host (Supercarrier). It seems this command is now broken.

Screenshots
Not applicable

Additional context
This was all working alst week perior to update DCS 2.8.4.38947 Open Beta.

Thanks we will take a look at it and see what changed on the DCS side.

l-e-o commented

Appreciate the support Penecruz and I kook forward to an upcoming update to VAICOM.

After we put out the next relaese can you test again. I am unable to reproduce on our latest test builds.

l-e-o commented

Happy to test and validate. It's the least I can do to support you and the team's efforts, which are much appreciated. I'll look out for the next release.

l-e-o commented

After we put out the next relaese can you test again. I am unable to reproduce on our latest test builds.

Confirming that "Link Host [carrier]" command does not work, still. To test, position the F-14 20nm away from the supercarrier inbound. In cockpit, set VEC/PCD switch to ACL (autopilot panel). Engage autopilot. Set mode to LDG (landing) and Steer CMD to AWL/PCD.

In this configuration I issue Jester the following commands:

"TACAN Tune Washington", Jester acknowledges and the TACAN direction tunes in
"Link Host Washington", Jester acknowledges but the needles in the HUD do not confirm linking to the carrier. I have set a VoiceAttack trigger that runs via the Jester menu and this is also acknowledged and the needles move to confirm the host (Washington) has been linked.

It seems the "Link Host [carrier]" command, despite being acknowledged by Jester, does not set the link.

Have you been able to reproduce this on the latest release?

l-e-o commented

I tested this again with the latest release of VAICOM Pro (community) and the issue persists. Same behaviour. When I issue the "Link Host [carrier]" command to Jester, he acknowledges but the host link to the carrier is not set. I try an alternative voice command via VoiceAttack that executes the equivalent Jester wheel options and the result works. Again, it appears the integration with DCS for the "Link Host" command is broken.

l-e-o commented

I will test this today on the latest release and see if I can reproduce

Can confirm jester is not changing the DL

Just tested it again, same result of the command being generated and processed, but Jester not changing the DL

Just wondering when a fix for this issue is planned to be released? Appreciate the hard work of the community developers.

I wanted to report that this has been a bug since earliest Vaicom versions before it went community. What jester seems to want to do is link-host to one of the escort ships (usually Ticonderoga if available) instead of the carrier.
It almost seems like its wired into the game and that might be due to how , when tomcat and jester were first released, the carrier had to be specifically assigned a tacan in multiplayer or else it was in 'deep water' mode and going silent, but escort ships always have their tacan on automatically.

I wanted to report that this has been a bug since earliest Vaicom versions before it went community. What jester seems to want to do is link-host to one of the escort ships (usually Ticonderoga if available) instead of the carrier. It almost seems like its wired into the game and that might be due to how , when tomcat and jester were first released, the carrier had to be specifically assigned a tacan in multiplayer or else it was in 'deep water' mode and going silent, but escort ships always have their tacan on automatically.

Thanks for the reply @marcocom. So, is there a work around either within the Mission Editor or VAICOM, or is it a deeper issue with the F-14, Jester and the super carrier? My work around is to issue a Voice Attack command specific to the Jester wheel options. Ideally, it would be great to have Jester switch the Link Host correctly when given the command using VAICOM.