Search the Community

Does anyone know the 3 laser codes used by the KA-50 for the Kh-25? I want to try budy lasing with Su-25 T, or use JTAC soldier with FAC mission, or try to use lua function : Spot Object Spot.createLaser(Object Source , Vec3 localRef , Vec3 point , number laseCode) The objective is to create a laser designation for the Kh-25 ML. But there is no documentation on the laser codes used by the KA-50. There is a 3-position rotary button in the cockpit to change the laser code of the KA-50, without knowing which laser codes are used. @ED, can you give us some feedback? Is budy lasering possible: - Between devices of different coalitions - Between Russian aircraft (such as the Su-25 and the KA-50)? Buddy lasing is already possible between KA-50 knowing the Kamov laser codes would allow us to carry out tests between different devices

Hi all, I hope this post finds everyone well. I'm not really a big-time poster here on the forums, so apologies if this post is in the wrong area or not the right thread. With the pending releases of the Afghanistan and Iraq maps and the introduction of Global War on Terrorism ground unit participants (insurgents, insurgent-type vehicles, etc.), I wanted to offer my experiences as a USMC JTAC to any of those who are looking to get a more realistic experience with JTACs in their campaigns, missions, or even to Eagle Dynamics (who I'm sure have a long list of individuals with a wealth of knowledge regarding this topic). While DCS does an okay implementation of an AI JTAC, it leaves a lot to be desired. Ranging from Air Control Measures, actual communications and their meaning, the execution of the 12-step process for CAS, rotary wing 5-lines, to Gunship/Apache Call for Fire, I'd be more than happy to advise on the implementation of such unit types to get the highest level of immersion. Having completed my first campaigns (FIWOS and Debden Eagles Campaigns) and seeing how much room there is for customization and scripting, I think there could be a lot to explore with JTAC implementation within campaigns and missions. I'm sure there are more JTACs/TACPs/CCTs in the community that would also be willing to chime in, but I figured I'd get the ball rolling as I haven't found any sort of posts for advisement/implementation. In short, I'm here to help the DCS community get the most immersive experience when flying campaigns and missions. Let me know if I can be of any assistance. Thank you for your time and happy flying!

Since updating, lasers aimed by other aircraft do not appear on NVGs. First encountered in multiplayer with a player using lightening pod - confirmed laser was ON and IR pointer was ON, did not render in my NVGs. Next encountered in a multiplayer server using CTLD JTAC. prior to update, CTLD JTAC had laser visible on NVGs, now it is not. Created a test mission with an MQ9 as AFAC lasing targets using inbuilt AFAC - confirmed that missiles tracked AFAC laser, but pointer never appeared in NVGs - tracks attached for this occurrence showing behavior in both MT and ST versions. YouTube video showing the problem at As a side note, it appears that the AFAC cannot hit the broad side of a barn in MT. All myhellfires missed in the MT test, but they all hit in ST. laser spot mt.trk laser spot st.trk DxDiag.txt dcs.log laser spot mt2.trk

Hello dear flight enthusiasts, I am posting / linking the ASENA mission here. For feedback - improvements, general suggestions etc. . The goal was to create a relatively simple mission - which entertains through voiceovers - and requires spotting with the TGP. The mission should offer beginners a causal start and give a rough feeling for CAS missions. It is a close air support mission. A JTAC provides various information to you so that you can support the to ground forces. TGP & GBU-12 are in focus. I thought about processing complete 9liners - but this seemed too overwhelming for beginners, even if you only listen to them via audio. That's why I simplified it. No scripts or mods. Triggers, flags and voiceovers were used. If one or the other has any feedback. Thank you very much. ______________ https://www.digitalcombatsimulator.com/en/files/3335476/

Basically what the title says: FC3 aircraft can't communicate with JTACs to make it lase a ground target. The only alternative is to use a scripted one

Yesterday in a retribution campaign I had 2 x PL-5EII, 2 x GBU-12, 2 x BRM-90 and WMD7 TGP. When contacting JTAC the pilot reported only the bombs and cannon. Unluckily I don't have a track rn but I'll try to recreate it

When an A-10C II (without ammunition) or F-18C send 1688 laser on target, can other friendly AV-8B Harrier find A-10C's/F-18C's laser on DMT? Can we use aircrafts like as JTAC officers in multiplayer games?

Let's say you go up in a Harrier or A10 with APKWS rockets and are relying on the JTAC drone to lase targets for you in a built up area. For that first target you likely don't know what it is that the JTAC is targeting, sure when you destroy a target it then display on screen what the next target is, but you don't know that of the first target. You also don't know exactly where it is and whether it is surrounded on 3 sides by building or trees all of which will stop an APKWS rocket before it gets to the target. Surely in real life the operator of the JTAC drone would be able to tell you pretty much on-demand what the target is and where it is on the map and allow you to reccy the area so that you could identify a suitable ingress course. Sometimes a target area will have several of those red smoke plumes and you wont know which target is being painted. Perhaps on the target area that a JTAC is circling the target being splashed could be identified in some way - color change perhaps to orange, or a sunburst halo around it or something that gives you a fighting chance to get a rocket past whatever cover that target may have.

I've spent countless hours trying to get my JTAC to archive my desired goals with no luck. The Goal Jtac designates the two targets in Zone 1 PT-76 is the priority 1 ; with WP Troops priority 2; with WP Once the all targets in Zone 1 are destoryed, JTac proceeds to Waypoint 3 2. Jtac designates the two targets in Zone 2 BTRs are the first priority; with WP Troops second priority; with WP This is a demo I've created to get a better understanding of how to set this up. My Demo map is using the Syria map. I'd appreciate any and all help! Thanks! Leif Operation 1st and Goal-Test.miz

Something I really miss in the Huey is the ability to talk to "jtac" and "ewr/awacs" unit's in the radio menu. For the Hind this feels like a must have sice it's a attack helo and will (from what I understand) get the R60. But I guess the jtac would require a big rework of the core mechanic/communication so maybe something for the future? Just my two cents...

Hi , I have started a single player mission in combined arms and want to direct a a10c onto a target with the jtac. I can mark the target with smoke or lase it , but how do,you contact the a10c to attack. I have added a path so,they are overhead target. I am using a humvee near the target and using the ‘b’ key. thanks adrian

In the built in DCS World F/A-18C mission "Paveway II Laser-Guided Bombs", the JTAC gives you an 8 digit MGRS coordinate for artillery targets. "KN81960551". However the WPT UFC only lets you type in 6 digits, entering only the first 6 digits does not give an accurate location. If switched to PRECISE, I don't have the full 10 digits and entering the 8 digits does not give the correct grid. Any help is appreciated!

For some obscure reason the JTAC menu disappears from the comms menu completely if I use a radio menu command to spawn a group via MIST. The JTAC unit itself is still there and alive but I can't call him up.

Good afternoon! I have been enjoying flying with JTAC laser designation in the Through the Inferno servers. I tried to create a simple JTAC scenario using CTLD and the JTACAutoLase feature. I am getting an error attempting to index local "_enemyUnit" con the 'createSmokeMarker' function. What do you believe could be missing from the very (VERY) basic implementation I did? I can share the .miz file, but maybe the log is enough, so I'm attaching the log, if someone thinks that adding the mission file is useful, I'd be happy to attach it: 2023-01-09 01:04:11.013 WARNING SCRIPTING (Main): MIST|init|1206: Init time: 0 2023-01-09 01:04:11.013 INFO SCRIPTING (Main): Mist version 4.4.90 loaded. 2023-01-09 01:04:11.014 INFO VISUALIZER (Main): Preload() camera=-281894.172614, 944.316886, 645324.389769 radius=60000.000000 2023-01-09 01:04:11.014 INFO EDTERRAINGRAPHICS41 (Main): ITerrainGraphicsImpl4::forceLoading(): pos=(-281894, 944.317, 645324), radius=60000 2023-01-09 01:04:11.513 INFO EDTERRAINGRAPHICS41 (Main): surface5 clean up LOD 0: left 2 released 20 2023-01-09 01:04:11.514 INFO EDTERRAINGRAPHICS41 (Main): surface5 clean up LOD 1: left 6 released 45 2023-01-09 01:04:11.514 INFO EDTERRAINGRAPHICS41 (Main): surface5 clean up 2.338500 ms 2023-01-09 01:04:17.079 INFO VISUALIZER (Main): Preload() finished 2023-01-09 01:04:17.146 INFO APP (Main): Screen: mission_offline 2023-01-09 01:04:17.161 INFO Dispatcher (Main): precache units resources in slots 2023-01-09 01:04:17.163 INFO LUA (Main): Lua CPU usage: metric: average mission loading: 17.5165 % 2023-01-09 01:04:17.163 INFO Dispatcher (Main): loadMission Done: Сontrol passed to the player 2023-01-09 01:04:19.684 INFO APP (Main): MissionSpawn:spawnLocalPlayer 3,F-16C_50 2023-01-09 01:04:19.689 WARNING EDCORE (Main): Source mods/aircraft/f-16c/cockpit/shape is already mounted to the same mount /models/. 2023-01-09 01:04:19.701 INFO VISUALIZER (Main): cockpit ILV loaded 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver/transmitter "UHF_RADIO" with id - 0 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: enabled VOIP capability for radio UHF_RADIO 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "ARC-164 Guard Receiver" with id - 1 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: added guard receiver - ARC-164 Guard Receiver 2023-01-09 01:04:19.723 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver/transmitter "VHF_RADIO" with id - 2 2023-01-09 01:04:19.723 INFO COCKPITBASE (Main): WebRTC VOIP init: enabled VOIP capability for radio VHF_RADIO 2023-01-09 01:04:19.724 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "Base ILS localizer receiver" with id - 3 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active DED, 26 (status undefined) 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active EHSI, 28 (status undefined) 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active UHF_RADIO, 36 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active VHF_RADIO, 38 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active INTERCOM, 39 (status undefined) 2023-01-09 01:04:21.039 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "Base TACAN receiver" with id - 4 2023-01-09 01:04:21.039 INFO COCKPITBASE (Main): lua state still active MACROS, 52 (status undefined) 2023-01-09 01:04:21.039 INFO COCKPITBASE (Main): lua state still active TGP_INTERFACE, 58 (status undefined) 2023-01-09 01:04:21.040 INFO COCKPITBASE (Main): lua state still active DTE, 65 (status undefined) 2023-01-09 01:04:21.043 INFO WORLDGENERAL (Main): loaded from mission Scripts/World/birds.lua 2023-01-09 01:04:21.053 INFO LUA (Main): Lua CPU usage: metric: average mission execution: 91.4732 % 2023-01-09 01:04:26.708 INFO SCRIPTING (Main): I - CTLD - Loading version 20211113.01 in 2 seconds 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): I - CTLD - Initializing version 20211113.01 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): T - CTLD - ctld.alreadyInitialized=[false] 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): T - CTLD - force=[nil] 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): Generating Laser Codes 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated Laser Codes 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generating UHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated UHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generating VHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated VHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generating FM Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated FM Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Searching for Crates 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): END search for crates 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): CTLD READY 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): D - CTLD - ctld.JTACAutoLase(_jtacGroupName=JTAC1, _laserCode=1688 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _laserB=6 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _laserCD=88 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _frequency=40.4 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): D - CTLD - ctld.notifyCoalition(_message=JTAC1, lasing new target, BTR-80. CODE: 1688. POSITION: @ 42 14.461'N 42 02.832'E - MGRS 38T KM 56371 80758) 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _radio= .freq=40.4 .name=JTAC1 .mod=fm 2023-01-09 01:04:32.995 ERROR SCRIPTING (Main): Mission script error: [string "C:\Users\xxxx\AppData\Local\Temp\DCS.openbeta\/~mis00000EBC.lua"]:5618: attempt to index local '_enemyUnit' (a nil value) stack traceback: [C]: ? [string "C:\Users\xxxx\AppData\Local\Temp\DCS.openbeta\/~mis00000EBC.lua"]:5618: in function 'createSmokeMarker' [string "C:\Users\xxxx\AppData\Local\Temp\DCS.openbeta\/~mis00000EBC.lua"]:5470: in function 'JTACAutoLase' [string "ctld.JTACAutoLase('JTAC1', 1688, true, "all", 1)"]:1: in main chunk 2023-01-09 01:04:34.697 INFO SCRIPTING (Main): T - CTLD - jtacTargetsList for JTAC1 is : .1= .dist=985.09104359134 .unit= .id_=16777472 2023-01-09 01:04:59.635 INFO LUA (Main): Lua CPU usage: metric: average mission execution: 4.9010 % 2023-01-09 01:05:02.052 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] Thanks in advanced, best regards, Rafa.

I often run into trouble when in the ME when I run into a roadblock and can't tell if its a bug, or simply how I have things setup. IDK, I am hoping this is just my misunderstanding of what it takes to get the JTAC to lase a target. I am drawing inspiration from @Wags video below. All I am trying to do is practice some LOAL hellfire shooting during the day. Eventually, once I get the bugs worked out, I will change time to night. Unfortunately, I cannot even get the JTAC to lase the target for me. Below is how I have the JTAC unit configured I have tried all sorts of settings on the JTAC and am now asking for help here. I have an Apache sitting 6mi south of this location. I contact the JTAC on the radio and checkin. He gives me the 9-line and tells me to engage with Laser Hellfire. BUT ... he doesn't lase. He's expecting me to find the target, lase and engage. What am I missing? There's no option to lase whatsoever (I don't even know if there should be). Attaching the trackfile in case that helps. I'm running MT. Thanks for any assistance here. NOTE: I have adjusted the laser code on the JTAC in the ME to 1588 thinking that I possibly had an improper code (too high). NoJTACLaser.trk

I would really like to be able to use the Reaper for spotting and lasing targets as a FAC-A. Currently in combined arms I can only use the ground vehicles. The Reaper already has all of that functionality as far as tasking usage, why not make it playable for FAC-A's? This could really add a lot of value to missions. Thanks.

Hi, I've created a couple videos going into some detail about conducting CAS or close air support. I am testing the waters to see if there is a number of people that would like to see something like this continue. Its my first attempt at making a Youtube video and my two videos do have a watermark until I see if others can use this info or even care to take their DCS experience to another level. Thanks for your time! Rifle.