fixed JTAC unresponsive in multiplayer, both ST and MT...

[Hexpul]

22 minutes ago, Flappie said:

@Gypsy I managed to fix the mission but I'm not sure where the problem comes from exactly. This is what I did:

1. Initial Moonbeam frequency is 133 AM: Moonbeam doesn't respond.
2. Changed Moobeam frequency to 135 AM: Moonbeam responds.
3. Changed back Moonbeam frequency to 133 AM: Moonbeam responds.

Then I did the same for Hammer (144 > 140 > 144) and he now responds.

I assume this mission was made with a previous version of DCS, and it looks like the latest DCS version does not accept some parts of it, especially JTAC frequencies. I'll report this to devs for analysis. Thank you for bringing the mission file with you, it helps a lot.

Here's your fixed mission. Please tell me if it works for you, now.

Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev2_FIXED.miz 5.01 MB · 0 downloads

By the way, I recommend to use VHF frequencies between 118 and 140 (included), because some modules can't reach 144 AM. See my spreadsheet, here.

PS: the F/A-18C "West test" was moved and set to Invisible for my test, don't forget to edit this.

Thanks Flappy, I will load it up on our server and @Gypsyand I will give it a go.

[Hexpul]

48 minutes ago, Flappie said:

@Gypsy I managed to fix the mission but I'm not sure where the problem comes from exactly. This is what I did:

1. Initial Moonbeam frequency is 133 AM: Moonbeam doesn't respond.
2. Changed Moobeam frequency to 135 AM: Moonbeam responds.
3. Changed back Moonbeam frequency to 133 AM: Moonbeam responds.

Then I did the same for Hammer (144 > 140 > 144) and he now responds.

I assume this mission was made with a previous version of DCS, and it looks like the latest DCS version does not accept some parts of it, especially JTAC frequencies. I'll report this to devs for analysis. Thank you for bringing the mission file with you, it helps a lot.

Here's your fixed mission. Please tell me if it works for you, now.

Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev2_FIXED.miz 5.01 MB · 1 download

By the way, I recommend to use VHF frequencies between 118 and 140 (included), because some modules can't reach 144 AM. See my spreadsheet, here.

PS: the F/A-18C "West test" was moved and set to Invisible for my test, don't forget to edit this.

Dang.. No joy on this.. I took you .miz dropped it onto our FOX3 server and loaded it up. I attempted to contact the Hammer but got nothing. The hornet is defaulting to calling any JTAC "AXEMAN" 

So I made a copy and edit the Freq to be 120 and 128 and now under JTAC menu I get "Scout HMMV..." twice instead of Moonbeam... and Hammer.. (See screen shot attached)

I believe all we have as far as mods are concerned is SRS and Tacview on the server? Could those be changing the freq some how?

Also including the DCS Log file

Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev2_FREQset.miz dcs.log debrief.log

[Flappie]

I've only tested SP (because I was able to reproduce the issue in SP).

I'll now test it with my very simple dedicated MP server and see if I get a different result.

I used the F/A-18C "test" aircraft to test by the way.

Edited April 2 by Flappie

[Flappie]

Tested in MP:

Moonbeam (133 AM)

• "Test East" F/A-18C : OK
• "Test West" F/A-18C : no answer, maybe a matter of range?

Hammer (144 AM)

• "Test East" F/A-18C : OK
• "Test West" F/A-18C : OK

I used the fixed mission from this post of mine:

 

[Parkour]

On 4/2/2025 at 1:55 PM, Hexpul said:

Dang.. No joy on this.. I took you .miz dropped it onto our FOX3 server and loaded it up. I attempted to contact the Hammer but got nothing. The hornet is defaulting to calling any JTAC "AXEMAN" 

So I made a copy and edit the Freq to be 120 and 128 and now under JTAC menu I get "Scout HMMV..." twice instead of Moonbeam... and Hammer.. (See screen shot attached)

I believe all we have as far as mods are concerned is SRS and Tacview on the server? Could those be changing the freq some how?

Also including the DCS Log file

I'm experiencing the exact same issue. I can not get JTACs to work in multiplayer at all; however, AFACs work fine. 

I have tried every conceivable combination in the last few days verifying the dedicated server isn't preventing something, double checking my own mission and the mission linked above by @Flappie.  I have tried every combination of both easy comms and regular comms, both radios, frequency settings in manual or preset (both in aircraft and in the mission).

No matter the change, the JTACs always show as Axeman and do not respond. Whereas the same exact mission in single player works find with the correct JTAC names and responses.

There is definitely an issue with JTACs in multiplayer working when not using scripts and just using the basic advanced waypoint functions.

@Flappie Are you able to verify again that the dedicated server is working correctly.   Is there any server online that has JTACs in a mission that is working?  Attached is the same file linked above that was used for a multiplayer test. I also included a very simple basic JTAC mission that works fine in single, but doesn't respond in multiplayer.

Thanks!

Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev2_FIXED.miz JTAC Test.miz