Callsign JoNay Posted March 19, 2023 Posted March 19, 2023 My virtual squadron and me noticed a bug in the latest OB. AI JTACs are unresponsive on comms. I tested the same miz in the following conditions: MT+SP = JTAC responds to check-in. MT+MP = JTAC is unresponsive. ST+MP = JTAC is unresponsive. I haven't tested ST+SP yet, I assume that works since MT+SP works.
Flappie Posted March 23, 2023 Posted March 23, 2023 Would you care to share your miz file, please? ---
Jenson Posted May 7, 2023 Posted May 7, 2023 On 3/24/2023 at 7:11 AM, Flappie said: Would you care to share your miz file, please? me and my squadron encountered the same issue, in single player or in local server hosting multiplayer mode, I could call JTAC and Tankers, but in multiplayer with real clients, they couldn't call out the JTAC, and a lot of the radio menu are greyed out. Attached our test mission. JTAC frequency from channel 11-18, tanker frequency from channel 8-10. Operation Hormuz Mission 12 test.miz 1 PC Specs: GTX4090, i9 14900, Z790 Pro, DDR5 96G, 4TB SSD M.2, 1200W Power Flight Gears: Logitech X56 HOTAS & Rudder, Pimax Crystal Light Modules: F-4E, F-14A/B, F-15C, F-15E, F-16C, F/A-18C, AV-8B, A-10C I/II, AH-64D, Supercarrier Location: Shanghai, CHINA Project: Operation Hormuz [F/A-18C Multiplayer Campaign]
vCheckmates Posted May 7, 2023 Posted May 7, 2023 (edited) On 3/19/2023 at 8:58 AM, Callsign JoNay said: My virtual squadron and me noticed a bug in the latest OB. AI JTACs are unresponsive on comms. I tested the same miz in the following conditions: MT+SP = JTAC responds to check-in. MT+MP = JTAC is unresponsive. ST+MP = JTAC is unresponsive. I haven't tested ST+SP yet, I assume that works since MT+SP works. Same issue , Jonay. Occasionally I can get it to work on MP with a restart but mostly its borked. Update: Seems that if you load a different mission on the server then load the desired mission it seems to work more often. Edited May 7, 2023 by 4WingRCAF
Jenson Posted May 8, 2023 Posted May 8, 2023 4 hours ago, 4WingRCAF said: Update: Seems that if you load a different mission on the server then load the desired mission it seems to work more often. You will encounter all kinds of weird bugs in DCS, just like in real life. PC Specs: GTX4090, i9 14900, Z790 Pro, DDR5 96G, 4TB SSD M.2, 1200W Power Flight Gears: Logitech X56 HOTAS & Rudder, Pimax Crystal Light Modules: F-4E, F-14A/B, F-15C, F-15E, F-16C, F/A-18C, AV-8B, A-10C I/II, AH-64D, Supercarrier Location: Shanghai, CHINA Project: Operation Hormuz [F/A-18C Multiplayer Campaign]
ED Team NineLine Posted May 10, 2023 ED Team Posted May 10, 2023 We have a report about Multithreading but not ST, are you still seeing an issue? Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
ED Team NineLine Posted May 10, 2023 ED Team Posted May 10, 2023 Looks like there is a fix in testing for this, so I hope to see it in the next Open Beta or shortly there after. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Flappie Posted May 18, 2023 Posted May 18, 2023 It should now be fixed in OB: Quote Dedicated server. Fixed - JTAC unresponsive in MP. ---
Flappie Posted June 3, 2023 Posted June 3, 2023 I've just tested @Jenson's mission above in MP, with an MT client : I jumped into the first Hornet slot and was able to communicate with Axeman31. Maybe it has to do with server settings? 1 ---
Ian Boys UK Posted June 4, 2023 Posted June 4, 2023 That's interesting. Here's a mission where we can't talk to the JTAC. He is on 133MHz and we are calling from Apaches. It does work if we run it as single player. It rarely works if we run it as a multiplayer server and never if there are 2 Apaches tuned to the freq. MULTI Caucasus West.miz
Jenson Posted June 5, 2023 Posted June 5, 2023 3 hours ago, Ian Boys UK said: That's interesting. Here's a mission where we can't talk to the JTAC. He is on 133MHz and we are calling from Apaches. It does work if we run it as single player. It rarely works if we run it as a multiplayer server and never if there are 2 Apaches tuned to the freq. MULTI Caucasus West.miz 609.51 kB · 0 downloads This is exactly what we encountered in our squadron. Our current solution is never put two JTAC (or Tankers) in the same frequency, otherwise, you won't be able to communicate with them in multiplayer (even if they have different name and callsign) 1 PC Specs: GTX4090, i9 14900, Z790 Pro, DDR5 96G, 4TB SSD M.2, 1200W Power Flight Gears: Logitech X56 HOTAS & Rudder, Pimax Crystal Light Modules: F-4E, F-14A/B, F-15C, F-15E, F-16C, F/A-18C, AV-8B, A-10C I/II, AH-64D, Supercarrier Location: Shanghai, CHINA Project: Operation Hormuz [F/A-18C Multiplayer Campaign]
Ian Boys UK Posted June 5, 2023 Posted June 5, 2023 That's a bit different: you're talking about two JTACs etc, I'm talking about 2 humans trying to listen to them. But yes, probably related. 1
Flappie Posted June 5, 2023 Posted June 5, 2023 (edited) I ran your mission on my dedi. I tried to contact Pointer21 aboard the AV-8B once in the air, frequency 133 AM, and the JTAC answered me. Does it work on your end if you're alone on the server? Edited June 5, 2023 by Flappie 1 ---
Flappie Posted June 5, 2023 Posted June 5, 2023 (I've just tested MT client with ST then MT server: the JTAC answered in both cases) 1 ---
Ian Boys UK Posted June 8, 2023 Posted June 8, 2023 On 6/5/2023 at 9:59 PM, Flappie said: I ran your mission on my dedi. I tried to contact Pointer21 aboard the AV-8B once in the air, frequency 133 AM, and the JTAC answered me. Does it work on your end if you're alone on the server? Starting in an Apache in Multiplayer and running server on the PC I'm playing on: No, it doesn't work. Tuned 133 and nothing.
Flappie Posted June 8, 2023 Posted June 8, 2023 Maybe it's an Apache-only bug, then? I'll try the Apache. 1 ---
Flappie Posted June 9, 2023 Posted June 9, 2023 I've just tried the Apache on my dedi. I was able to communicate with the JTAC on VHF 133AM. Apache_JTAC_133AM-20230609-190821.trk ---
Gypsy Posted April 2 Posted April 2 Still an issue, AI JTAC doesn't work in MP (multi-threading). Works fine in mission editor and as loading up as a singleplayer .miz, but as soon as it's added to a server the JTACs no longer respond even to initial check-in. Hasn't worked for at least a year, if not longer. Definitely hasn't been fixed yet. "Would you say we'd be venturing into a "Zone of Danger?"
Flappie Posted April 2 Posted April 2 Please attach a DCS track or at least the mission file. We can't help you if you don't attach one. 1 ---
Gypsy Posted April 2 Posted April 2 (edited) 5 hours ago, Flappie said: Please attach a DCS track or at least the mission file. We can't help you if you don't attach one. Sorry, was just frustrated last night, rage quit and forgot to post the miz before bed. Here you go. JTAC works in local singleplayer, but not a single response from either JTAC in multiplayer on a Fox3 server. Removed any mods that was in the mission and issue still continues. This has been an ongoing issue for a while. Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev2.miz Workups_WK3_Ai-JTAC-Helo-9Line3-OOBEJTAC-rev1-zapp-20250402-121433.trk Edited April 2 by Gypsy Added track 1 "Would you say we'd be venturing into a "Zone of Danger?"
Flappie Posted April 2 Posted April 2 The good news is that I'm able to reproduce the absence of answer from Moonbeam (at least), even in SP. I'll check what's wrong. 2 ---
Hexpul Posted April 2 Posted April 2 1 hour ago, Flappie said: The good news is that I'm able to reproduce the absence of answer from Moonbeam (at least), even in SP. I'll check what's wrong. I couldn't get Hammer to respond, although I did try in Single Player and it seemed to work with both ¯\(°_o)/¯ but putting the same .miz on a FOX3 server all JTAC's just stopped working... We had the same issue a year or so ago but nothing came of it... I am surprised more users haven't reported this the Base line JTAC functionality is pretty sweet!
Flappie Posted April 2 Posted April 2 (edited) @Gypsy I managed to fix the mission but I'm not sure where the problem comes from exactly. This is what I did: Initial Moonbeam frequency is 133 AM: Moonbeam doesn't respond. Changed Moobeam frequency to 135 AM: Moonbeam responds. 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 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. Edited April 2 by Flappie 1 ---
Recommended Posts