Does datalink (red triangle) work in SP?

[Bahger]

I was alarmed to hear that JTAC target i/d -- the red triangle in the TAD -- is borked in SP in the Release version. Maybe it's just MP. Can anyone confirm? Thanks.

[Lonecrow66]

I haven't had a triangle in a while. I was going to ask that question as well. I just got used to inputting the coords manually ahead of time instead of waiting for it.

[kingpinda]

If (not when) Jtac answers and your id is correct (check the tad for the NET osb) it should work. There are numerous reasons Jtac may not answer. most are beyond me. maybe something with the campaign missions. also there is apparantely a bug whenever your gear leaves the ground that net id is reset to 0. so you need to set both back to 1 again in the NET option on the TAD screen.

 

But in the regular missions and quick action missions JTAC works fine and i receive the red triangles.

[Lonecrow66]

No get the standby for data plenty of times mainly in campaigns and no triangle pops up. I thought it might have to do with a group ID. I am not quite that far into the manual yet. Still working on why the mavericks will not lock with TMS up SHORT while inside the DLZ half the time even though they are slaved to the SPI and on the right target. Works sometimes and other times it doesnt.. you ahve to get really close before it will lock.

[kingpinda]

yes if data isnt'received via triangle then (group) ID is wrong. So press the NET osb in lower right corner from your TAD. and then press 1 in the scratchpad beneath your hud and then push on the top ID. then press 1 again in scratchpad and push the lower ID. when both are set to 1 it SHOULD work.

 

regarding mavericks yeah I don't know if the different types matter much but they will lock in my experience anywhere between 7 and 5 nautical miles.

[mig29movt]

I receive the red triangle on my TAD but it doesn't fit the actual postion of the target!

Most of the time it's really hard to find it, because it is far away from the triangle symbol (or SPI).

I always cheated with the AWACS (F10) view and the pause key but that sucks. I understand that the triangle won't move along with a driving tank, but after 2 minutes of searching, the target could be everywhere...

[Lonecrow66]

yes if data isnt'received via triangle then (group) ID is wrong. So press the NET osb in lower right corner from your TAD. and then press 1 in the scratchpad beneath your hud and then push on the top ID. then press 1 again in scratchpad and push the lower ID. when both are set to 1 it SHOULD work.

 

regarding mavericks yeah I don't know if the different types matter much but they will lock in my experience anywhere between 7 and 5 nautical miles.

 

 

If that is the case then why is the actual DLZ range bracket longer ? I've had it down below half way and it wouldn't lock. But if I manually slew myself I can lock things up further range than slaving the mav to the TGP SPI.

[Lonecrow66]

Also why did the data always used to come up before? I checked all the mission parameters in the actual campaign notes and it never tells you what your group ID is supposed to be.. so I never knew what to c hange it to. You'd think with a campaign mission where start on the runway that might have been set up ahead of time. It was in the beta but not now..

[Mugenjin]

If that is the case then why is the actual DLZ range bracket longer ? I've had it down below half way and it wouldn't lock. But if I manually slew myself I can lock things up further range than slaving the mav to the TGP SPI.

 

Just because the seeker can't identify a target at a specific range doesn't mean that the missile wouldn't be able to fly even farther.

 

Not sure bout the last part since you should be able to lock things at the same range, whether you do it manually or via slave. You sure you did target the same vehicle with the same type of mav?

[Sticky]

I was alarmed to hear that JTAC target i/d -- the red triangle in the TAD -- is borked in SP in the Release version. Maybe it's just MP. Can anyone confirm? Thanks.

 

Works for me in SP, press NET on TAD and make sure your IDs are the same.

[Bahger]

If data isn't received via triangle then (group) ID is wrong. So press the NET osb in lower right corner from your TAD. and then press 1 in the scratchpad beneath your hud and then push on the top ID. then press 1 again in scratchpad and push the lower ID. when both are set to 1 it SHOULD work.

This is very helpful, thank you. My main area of interest is in SP mission design and anyone who played my missions in the Betas will recall that there is extensive use of JTAC. If JTAC datalink is broken, it will not be worth the trouble of building missions around it. So can someone please provide final confirmation re. whether or not it works properly in SP and if the above solution is the right one and applies to SP? Thank you.

Edited February 27, 2011 by Bahger

[RodBorza]

yes if data isnt'received via triangle then (group) ID is wrong. So press the NET osb in lower right corner from your TAD. and then press 1 in the scratchpad beneath your hud and then push on the top ID. then press 1 again in scratchpad and push the lower ID. when both are set to 1 it SHOULD work.

 

 

Thanks for the help. It will sure save a lot of frustated missions.

[Bullant]

So can someone please provide final confirmation re. whether or not it works properly in SP and if the above solution is the right one and applies to SP?

 

So far it has worked every time for me in SP missions (not sure about campaigns, haven't got that far yet).

[shagrat]

If that is the case then why is the actual DLZ range bracket longer ? I've had it down below half way and it wouldn't lock. But if I manually slew myself I can lock things up further range than slaving the mav to the TGP SPI.

 

Depends much on the MAV Type you use (D=IR, H=TV)...

 

The MAV "lock" is a search for heat difference (D) or difference in contrast (H). If a Tank sits on a yellow field it stands out/is easy to acquire.

 

What is true though, the slewed reticle has a better chance to acquire a target than simple TMS up short, from what if seen so far. :huh:

 

With the H you get pretty damn close into the SAM/AA Cover before you can pickle... :bye_3:

[gonvise]

Hello...

 

I have no problem receiving JTAC data in single missions, but I'm testing the first mission of the first campaign and I don't receive data via triangle and wilco button not appears. Previously, and following the tips of this post, I have changed the own id and group id, both to 1, a moment before JTAC contact. Anybody have tested this in this first mission? Any ideas?

 

Thanks!

Edited February 28, 2011 by gonvise

[Steel Jaw]

How do we know what net is numbers to set to link with JTAC?

[kingpinda]

How do we know what net is numbers to set to link with JTAC?

 

I don't know actually but in the campaign missions i have flown it seems to be ID 1. I did try to make some sense out of the mission editor information. I even tried to set my flight to group 1 instead of the 2 it was programmed to. Afterwards in flight I was over the comm identifying myself as 9-1??? Then after takeoff I looked at my net id and it was at zero. Presumably due to the net reset bug when gear leaves pavement. I manually made it id 1 and I got the data.

 

Be sure to check your id before contacting JTAC :p I was doing the first campaign I think received the nineline, got standby for data. No triangle. Checked my net id. It was set to zero, changed it to 1. Contacted JTAC tried to get the data again. Had to decline the mission. Again contacted JTAC: No further tasking.... lol.

[shagrat]

How do we know what net is numbers to set to link with JTAC?

 

It is in your call sign, I guess: Hawg 1-1 means ID: 1 Group: 1 Edit: the second one

 

Since only the group is relevant to connect to each other, it should be sufficient to change it to 1.

 

Take care to do this before the readback!!! ...after you initiated that, it seems there is no way back.:cry:

Edited February 28, 2011 by shagrat

[Bahger]

Is there a setting in the ME for this? I never had to set Net I/D in JTAC missions in the Beta but knowing this could save some trouble.

[kingpinda]

I haven't found it yet. But the problem is that there apparently is a bug that when your gear leaves the pavement your netid can be reset. So always check your ID when wheels up.

[zamboni]

Is there a setting in the ME for this? I never had to set Net I/D in JTAC missions in the Beta but knowing this could save some trouble.

 

I was messing around with the ME last night and was wondering just what determined the group ID number for aircraft. I have a sneaking feeling that it is determined by the order that aircraft are added when creating the mission and there is no way to manually change the group ID in the ME.

 

BTW...I was flying a SP campaign mission last night and I noticed that my ID #s changed when my Wingman's wheels left the ground and not my wheels lifted off the ground.

[kingpinda]

lol now thats even weirderder :p I do know that i'll be flying with easy radios from now on... just to have one buggy thing less to think about.

[gonvise]

Does anyone works red triangle in first mission of first campaign?

 

Fisrt mission of first campaign... own id and group id reset both to 1 in flight a moment before contact JTAC. I receive the nineline, got standby for data... and NO triangle. :doh:

Edited March 1, 2011 by gonvise

[Sticky]

Does anyone works red triangle in first mission of first campaign?

 

Yes works in first mission first campaign once I set the IDs.

 

Fisrt mission of first campaign... own id and group id reset both to 1 in flight a moment before contact JTAC. I receive the nineline, got standby for data... and NO triangle. :doh:

Yes I did the exact same thing, just a moment before contact with JTAC, it works everytime now. Are you sure you hadnt forgotten to switch on the SADL?

[awjudge]

For reference, I have the same problem as gonvise. I get everything from JTAC except the triangle... group and own IDs all set correctly.