Locating targets tasked by JTAC

Thanks Matt for the great video. Question re IP... in this mission the IP is FORDD. Do you simply add it as a waypoint or is it datalinked as well? I noticed an X over the ground in the HUD, but I couldn't find an explanation in the manual....is it related?

Thanks Matt for the great video. Question re IP... in this mission the IP is FORDD. Do you simply add it as a waypoint or is it datalinked as well? I noticed an X over the ground in the HUD, but I couldn't find an explanation in the manual....is it related?

Yes please someone explain the X ??? I know it designates friendly forces but how do it work? I take it the HUD dont magicaly know where friendly forces are :P

Also can we use the TISL to track reflected laser energy from say a JTAC ?

And how do we setup this in the editor. For them to iluminate with a certain laser code?

There is a new button in the ME to add IPs.

Ahh, got it. So the IP issued by the JTAC shouldn't come as a surprise?

Yes please someone explain the X ??? I know it designates friendly forces but how do it work? I take it the HUD dont magicaly know where friendly forces are :P

 

Also can we use the TISL to track reflected laser energy from say a JTAC ?

And how do we setup this in the editor. For them to iluminate with a certain laser code?

My understanding of the "X" is that it simulates the transmission of an IFF (Identify Friend or Foe) code to your AC. The actual workings behind IFF are HIGHLY classified, but the "idea" is implemented.

When it comes to the JTAC, I would hope that, if possible, TISL code will be randomly generated each time - makes it essential to pay attention to the info transmited.

*EDIT*

Speaking of which.. I would also like to see the issue, again if TISL manual code selection is possible/implemented, if two pilots happen to NOT set different codes that it interferes with their ordinance delivery if they both have their repesctive lasers going at the same time.

It's the data from the EPLRS.

 

TISL is never used in the A-10C, TGP does it all and a lot more. TISL will not be implemented.

Wags, do you guys have the intentions of having manually set laser codes for buddy lasing and such?

Or is it too early to tell?

Understood, thanks for the input thus far.

It's the data from the EPLRS.

 

TISL is never used in the A-10C, TGP does it all and a lot more. TISL will not be implemented.

Ah ok thanks, had to google the EPLRS but makes sense.

Anyone have any info on how the LSS search function of the TGP works?

Or well i know how it works(i think) but im wondering how i can get something lased in the mission editor. I found some old LOMAC threads about the editor where they said for the A10 you had to set something and the object would then be permently lased and you could located it with the TISL.

Can you get the JTAC to lase a target for you instead of using the SADL.

Can you explain how you get the JTAC to work? I added a BComd to a mission but no option was there to call in.

You need to give an AI unit a FAC/JTAC task using the 'advanced' option in the waypoints interface. There's a PDF in the docs directory which details the new AI task system. Looks really awesome.

I've only been able to get the JTAC to work properly when used with ground units - haven't been able to get an airborne FAC to actually check me in. Not sure if I'm doing something wrong, or if it's just not fully implemented yet, but I'm leaning toward the latter.

You might want to have a look at the 'Shooting Gallery' mission to see how to set it up. It's a very straightforward mission. They've really done a marvelous job with the JTAC, even though it's not finished yet and still a little buggy.

P.S. I think the battlefield commander is related to the ability to give orders to units via the map screen, and nothing to do with JTAC/FAC.

My understanding of the "X" is that it simulates the transmission of an IFF (Identify Friend or Foe) code to your AC. The actual workings behind IFF are HIGHLY classified, but the "idea" is implemented.

...

I believe A-10C can't interrogate with IFF - it can only answer to interrogation. As for "X" - data is received via SADL datalink (manual - page 311).

Speaking of the manual p311, it says "Blue diamonds indicate friendly ground forces", but the icon shown is a green cross, and that's what's used in-game too. Is the green cross a placeholder, or is the manual wrong?

Speaking of the manual p311, it says "Blue diamonds indicate friendly ground forces", but the icon shown is a green cross, and that's what's used in-game too. Is the green cross a placeholder, or is the manual wrong?

Please post this in the manual thread too, one or the other will get fixed.

Nate

Mission Editor: Set an IP for JTAC to reference?

So I figured out how to get JTAC into a mission but when I call for a 9 line the first 3 lines always come up as N/A. I tried naming waypoints in my flight plan but that didn't help. Anyone know how to set the IP that JTACs reference when giving briefs?

Check this post - The Mission Editor should have an "Add IP" function in the next beta.

LOL well that explains why I couldn't find it last night :D

Thanks for the link.

 

TISL is never used in the A-10C, TGP does it all and a lot more. TISL will not be implemented.

Why not wags?TISL has some interesting features that TGP doesn't have like the ability of stick ADI to TISL target via navigation mode select panel. And it's a characteristic equipment of the wathog. By the way, it seems quite developed in dcs: a-10c manual!

Regards

Sadness. I was just messing with the TISL panel and going mad why the navigation system triangle for TISL wouldn't light up. Turns out ED isn't modeling it not because the system is deactivated or classified but because they'd "rather not."

TGP hardly replaces the TISL. Can't scan for laser targets LSS/LST while using the TGP elsewhere, can you?