-Cipher-

Hi there old friend I guess this would be the only official documentation you might be looking for hope it helps https://www.digitalcombatsimulator.com/en/support/faq/scripting_engine/

for now you can enter AI mode 1 and 3 transponder codes in pilot name field until ED develops a field for aircraft properties. mode 2 can be changed only for specific aircraft such as only F-15E and I guess the Mirage-F1 via mission editor special properties. to set mode 3 and mode 1 for ai aircraft put this in the pilot name : #IFF_M3=<4-digit code>,#IFF_M1:<2-digit code> i.e : #IFF_M3=4444,#IFF_M1=11

this also applies to the F-16C JSOWs as I couldn't enter terminal parameters in CNTL page. I will double check to make sure of it

Hi JSOWs and SLAMER (not the old SLAM) are refusing to accept terminal profiles, I have reported it a couple of times.

Sorry if non of the solutions I provided did not help, but I'm just doing what I can, at least I can guarantee you that I have reported to the team regarding your issue, they'll do their best. Thanks.

Hi for now, if you are playing in dedicated servers, the only solution is : if jtac must be a ground unit then try using in-game jtac system which can be setup by placing a ground unit then applying "perform command" frequency , set callsign then in assign task : "FAC - Assign Group" task with it's setting, or you can use the scripted CTLD Jtac system . if you want a player to do the job , until we get a fix you have to use an aircraft I suggest you F/A-18C (Litening II), A-10C-II & AV-8B since these are the only platforms able to fire both IR and laser for a friendly, we have tested client aircraft and it is working fine. this is my temporary solution for you until we get a fix. if you had any questions regarding this topic feel free to ask me. thanks

Ok I have run another test in a dedicated server with a friend and I can confirm this is an issue, we have reported it to the team Thanks

Ok so I have not yet tried doing it with the host being the JTAC and me being the A-10 I am available to test it if you are interested.

No I was not host, the apache guy was the host. but it was not a dedicated server.

Hi I have completed a test with several players and myself as a human JTAC. the hornet could easily spot the laser via tgp. the apache could easily guide his hellfire using my laser and could spot the IR pointer in his night vision goggle. F-16C could spot the laser via tgp easily as well. A-10CII could also track the target via tgp and spot the IR pointer on his goggles. [he was struggling with his tgp since he hadn't flown the plane for a very long time]. here the track files : mine (JTAC) : TEST_Cipher.trk airplane track files :Test_OP_IRPLST-20240203-201046.trk I can confirm that I did not detect any problems with CA JTAC. I suggest all participants to perform a slow repair, delete game cache (metaashers). let me know if your problem were solved. Thanks.

Hi sorry for the delay I have investigated the track files you posted. I have recreated the situation and I could easily detect the laser via default AI JTAC. but something I noticed was the F-18 initiated the LST far before the laser detection range but however in my personal test I tried the same in further range but still managed to pick up the laser at 15nm. to make sure you are searching correctly make sure the targeting pod is placed in proximity close enough so the gimbal would have LOS towards the target, (there was an instant where the F-18 was in a pretty close butt out of LOS relative to the target.). try different laser emitters. if nothing worked try performing a slow repair. I will share you my personal test track file to show you how it worked. here is the track file : Hornet_LST.trk I can confirm that this is not an aircraft module problem at least for the F-18. if you want to make sure that the laser fired via combined arms player is actually working, ask a player to fly an AH-64 with laser hellfires, and ask the pilot to manually select the hellfires. try lasing, the apache pilot can easily pick up laser by only looking at the zone within 9.9 Km. sadly I got no one around to help me perform the test but I think you can do it with your friend. also keep that in mind that IR pointer =/= laser so don't expect an ordinance or LST/LSS to pickup IR pointers, they are only visual pointers working with night visions, make sure you are using the laser with properly matching codes. let me know the results. thanks

I will investigate tomorrow

Phantom Phorever.

@xanstin, make sure other players LST or LSS code does match with your designator code, and they are searching the right spot.

Hi it has something to do with the livery files (Skins) for the E-2 and S-3. also there is usually one log file is enough try posting the log file in : =log analyser discord channel of ED's official discord, it's a great tool is there any livery file that needs to be downloaded or something?