JTAC is slow to respond and may not respond at all

[neroroxxx]

World 1.2 with updated A-10C module.

 

JTAC takes a while to answer (compared to 1.1 and to standalone) by that i mean up to 3 minutes for each question, then it get stuck on "Ready to copy remarks" as well.

 

Also when I got stuck on ready to copy remarks then if i send the CHECKING OUT command it will answer me right away.

 

I'm not sure if this is a reported bug but it's made it difficult to finish missions (because by the time JTAC answered the AI killed all targets) or even do them at all without the JTAC to tell me what to do.

 

Last thing was that when JTAC does answer and you send the CONTACT command to confirm that's the target the command isn't sent at all.

 

I will post a track tonight :-)

[Gisen]

Seconded. Definitely happens a lot more often in the newest update 1.2

[RevoFx]

In my case JTAC always stucks at the second target request. After i'm ready to copy remarks the JTAC stops to respond until i abort and recontact him.

Until now i thought it was my fault, because there are no other threats about this prob. It is an prob ... right?!

 

greatings revo

[Settingz85]

Having the same issue with ATC and Jtac. This happens in SP and Mp. Some players report the same Problem.

[MainSail]

Same here. JTAC response takes way to long and after ready to copy 9-lines, JTAC keeps looping ABORT ABORT ABORT. Needed to change the freq. to shut him up. This happened on various multi-player missions and different JTAC freq.

[svedan]

Uncheck the "Allied flight reports" in the gameplay options seems to ease the problem a little bit. But I still allways get stuck on "ready to copy remarks" the second time I contact him. Is there a official comment on this problem from the ED team?

Edited August 2, 2012 by svedan

[Gate-5]

Same problem here. I also get stuck during the second talk on and sometimes it continues after several minutes, but never properly works again. Check out didnt work either, couldnt check in anymore afterwards.

[Speed]

Please, upload a track and dcs.log.

 

dcs.log is in C:\Users\<Your User Account Name>\Saved Games\DCS\Logs\dcs.log

 

Thanks.

[svedan]

Please, upload a track and dcs.log.

 

dcs.log is in C:\Users\<Your User Account Name>\Saved Games\DCS\Logs\dcs.log

 

Thanks.

 

Here you go.

JTAC gets stuck on "ready to copy remarks". It seems to allways happen on the second time I contact him for a new target, and this mission was no exception. the 1st, 3rd, 4th, 5th I contact him on this mission it worked.

 

JTAC is a little slow to answer sometimes. It could be because of the radiochatter from wingman and other allied flight. I have unchecked "allied flight reports" and it seemd to ease the problem. Maybe JTAC should should have higher priority over other AI. That way I dont have to wait for my wingman and other allied flights to call out every target in the area so Im not able to get an answer from JTAC.

 

I uploaded both dcs.log and dcs.log.old. I watched the track after I saved it so maybe the dcs.log was created when I played the track and the dcs.log.old is the one from the actual mission.

 

I created this mission using the "create fast mission"

JTAC problem.rar

Edited August 3, 2012 by svedan

[Speed]

Here you go.

JTAC gets stuck on "ready to copy remarks". It seems to allways happen on the second time I contact him for a new target, and this mission was no exception. the 1st, 3rd, 4th, 5th I contact him on this mission it worked.

 

JTAC is a little slow to answer sometimes. It could be because of the radiochatter from wingman and other allied flight. I have unchecked "allied flight reports" and it seemd to ease the problem. Maybe JTAC should should have higher priority over other AI. That way I dont have to wait for my wingman and other allied flights to call out every target in the area so Im not able to get an answer from JTAC.

 

I uploaded both dcs.log and dcs.log.old. I watched the track after I saved it so maybe the dcs.log was created when I played the track and the dcs.log.old is the one from the actual mission.

 

I created this mission using the "create fast mission"

 

Yup, thanks for the report. There's something going wrong in there, I can see the Lua errors in your dcs.log.

[Speed]

I modified C:\Program Files\Eagle Dynamics\DCS World\Sounds\Speech\NATO.lua to try to fix at least some of the problems. If you guys want to try it out and let me know if you still have problems, that would be great.

NATO.lua

[neroroxxx]

I modified C:\Program Files\Eagle Dynamics\DCS World\Sounds\Speech\NATO.lua to try to fix at least some of the problems. If you guys want to try it out and let me know if you still have problems, that would be great.

 

Thank yous Speed, i will try it right now.

 

Would you suggest unchecking the allied reports?

[neroroxxx]

Speed, I tried your mod and it helped a lot, JTAC still takes a little longer to respond than it was on stand alone but at least now he always responds with your mod, thank you!!!!

[svedan]

I can confirm this fix is working for me too, JTAC no longer gets stuck on "ready to copy remarks". Thank you for your support Speed.

[Gate-5]

Speed, I tried your mod and it helped a lot, JTAC still takes a little longer to respond than it was on stand alone but at least now he always responds with your mod, thank you!!!!

 

Same here too... many thanks to Speed for the quick fix :thumbup:.

[SUBS17]

I've found in the A-10C campaign Georgian Hammer the JTAC in mission 3 gives a false grid coordinate. First grid from JTAC Playboy GG314534 but 2nd tgt given is KM688559 which is quite a distance from the mission area(all tgts are in GG area) and there are no tgts there.:doh: As a 2nd backup I resorted to data link message in the remarks which gave lat/long grid which was correct.:thumbup:

[Speed]

I've found in the A-10C campaign Georgian Hammer the JTAC in mission 3 gives a false grid coordinate. First grid from JTAC Playboy GG314534 but 2nd tgt given is KM688559 which is quite a distance from the mission area(all tgts are in GG area) and there are no tgts there.:doh: As a 2nd backup I resorted to data link message in the remarks which gave lat/long grid which was correct.:thumbup:

 

Negatory. JTAC grids are never incorrect. They are just not giving you all the information.

 

A full MGRS grid includes the UTM zone. On Caucasus map, there are only ever going to be two UTM zones you will use: 37T or 38T. The "GG314534" coordinate was, in full, 37T GG 314 534, while the other coordinate was 38T KM 688 559. The problem is, you needed to change the UTM zone from 37T to 38T for that second coordinate, and you did not do so.

 

I will be releasing a mod in probably a week or two that will make the JTAC give the full MGRS coordinate to help solve this confusion, as well as adding other fixes.

 

The reason the JTAC skips the UTM zone is probably that, in real life, you as a pilot would already know this information (it would be obvious, UTM zones are very big). The problem is when the JTAC is giving target coordinates near a UTM zone boundry, as is the case for this mission.

[SUBS17]

That explains it thanks.

[St3v3f]

I modified C:\Program Files\Eagle Dynamics\DCS World\Sounds\Speech\NATO.lua to try to fix at least some of the problems. If you guys want to try it out and let me know if you still have problems, that would be great.

 

I installed that and the game crashed when the first JTAC I contacted was just about to give the remarks.

 

Could be a coincidence though

 

Update:

Had some JTAC contacts today and they worked fine. But response time is very long now

Edited September 13, 2012 by St3v3f

[thinkr]

What version of DCS is this intended for?

Does it fix anything for 1.1.1.1?

[bojangles_25]

Hi all,

I've tried the fix in this thread and it hasn't really made much of a difference. JTAC is still quite temperamental and may take several minutes to respond.

 

I put the file in "DCS World\Sound\Speech\NATO.lua" and renamed the original.. this is right yes?

 

Is there anything else I can do?

[Druid_]

My best advice for now is wait for the patch. A lot of bugs with JTAC have been fixed. I can't promise that all are fixed but it is something I have been working on with the dev responsible. So all I can say for now is have a little patience and hopefully your particular problem will be resolved.

 

Just one more thing with regards to JTAC, sometimes the mission builder does not implement the JTAC correctly so it is not necessarily a bug from the client. There are a number of threads related to JTAC implementation which explain in detail the correct methodology. If you are having any problems with version 1.2.1 then please post a trk file and I will take a look at it and try to resolve/fix the issue.

[bojangles_25]

Thanks Druid, great that you guys are working on it and have the time to let people know on the forums :)

 

Do you have any idea when the next patch will be released? Or a list of issues being worked on?

 

Many thanks

[SUBS17]

My best advice for now is wait for the patch. A lot of bugs with JTAC have been fixed. I can't promise that all are fixed but it is something I have been working on with the dev responsible. So all I can say for now is have a little patience and hopefully your particular problem will be resolved.

 

Just one more thing with regards to JTAC, sometimes the mission builder does not implement the JTAC correctly so it is not necessarily a bug from the client. There are a number of threads related to JTAC implementation which explain in detail the correct methodology. If you are having any problems with version 1.2.1 then please post a trk file and I will take a look at it and try to resolve/fix the issue.

 

We have a problem as the option to assign JTAC freq is no longer in the ME.

 

edit Found it

Edited October 29, 2012 by SUBS17

[bojangles_25]

Hi All,

Is anyone still seeing this problem in 1.2.2?

 

I'm still seeing it happen.. Can anyone pinpoint what is causing JTAC to behave in this way? Is it actually a problem with the way the JTAC unit is behaving or is it just caused by sound scripting?

 

IMHO this is a pretty serious regression, because it was pretty solid in 1.1.1.1

 

Has anyone tried anything else?

 

Cheers