JTAC for KA-50

thanks

Help. No JTAC menu avilable. When I set the SPU-9 on VHF-1, then use the communications menu, no option appears.

Yes, I did install the JTAC V1.3 files into the appropriate locations.

Any ideas..?

Not flying Ka50 at the moment but if I were I would use your mod.

Ps : why can´t I give you rep?

Help. No JTAC menu avilable. When I set the SPU-9 on VHF-1, then use the communications menu, no option appears.

 

Yes, I did install the JTAC V1.3 files into the appropriate locations.

Any ideas..?

Before you try again. Make sure the JTAC mod is the last one you've installed. Your auto-updater could have overwritten files after the latest update.

Read+understand the manual.

Is it only the JTAC option that does not appear? Are you sure there is active JTAC in the mission at the moment you open the menu?

@asparagin

Looks like it worked, thank you!:smilewink:

Are you sure there is active JTAC in the mission at the moment you open the menu?

SOLVED. I assigned the FAC role to a BLUE unit :doh:.

SOLVED. I assigned the FAC role to a BLUE unit :doh:.

And you were red?

The only condition required to make JTAC work is a western (NATO) unit. Red or blue is a matter of the mission designer's taste, although it makes more sense to use red for a USSR coalition.

Glad you got it working!

Thank you for your mod and simple trouble shooting.

Dear TurboHog.

Greetings from South Korea.

I think that your mod is one of the most brilliant mod that i ever saw, and i am really appreciating for your work. now i am enjoying your mod on 1.2.3 and it is really great. ^ ^

during installation (i installed this mod manually without any other program), i had a same problem just as "mastiff" experienced, which is that no communication menu on screen when i pressed "\" button.

i tried the same way as you wrote in end line of "#16", but i couldn't find the "keyboard.lua" on my dcs folder (now i know that file belongs to save game folder, not dcs folder).

but i resolve this problem simply by modifying options.

OPTIONS->CONTROLS->KA-50 SIMS, RADIO COMMUNICATIONS-> clear the key (normally "\") assigned on "COMMUNICATION MENU".

then, re-assign the key on OPTIONS->CONTROLS->KA-50 SIMS, Ins Cyclic Stick->SPU-9 PTT.

that's it. it works perfectly.

i hope this simple tip would be helpful to other people. once again, THANX TurboHog.

OPTIONS->CONTROLS->KA-50 SIMS, RADIO COMMUNICATIONS-> clear the key (normally "\") assigned on "COMMUNICATION MENU".

 

then, re-assign the key on OPTIONS->CONTROLS->KA-50 SIMS, Ins Cyclic Stick->SPU-9 PTT.

Didnt this change anything else? I would like to know why there is even a key binding for COMMUNICATION MENU if you can reach the same with SPU-9 PTT.

Does anybody know this?

Didnt this change anything else? I would like to know why there is even a key binding for COMMUNICATION MENU if you can reach the same with SPU-9 PTT.

Does anybody know this?

I believe the original binding works if you're using Simple Radio mode. If you're using realistic mode, you have to use the SPU-9 PTT key, which I've bound to RAlt+\. The original binding doesn't work on UK keyboards so I had to change it.

I believe the original binding works if you're using Simple Radio mode. If you're using realistic mode, you have to use the SPU-9 PTT key, which I've bound to RAlt+\. The original binding doesn't work on UK keyboards so I had to change it.

Thanks for your answer. Ive tested this statement in realistic mode. I dont see any difference between using the communication menu or the ptt button except the headline of the menu. If you press communication menu the headline is "Main" and if you use the ptt button the headline states the currently selected radio. Apart from that i dont see any difference. Im able to call the ground crew with the door open and wrong radio selections with both keys. Im not able to call the ground crew with the door closed unless the intercom is selected. This works for both keys. ATC works as expected with both keys. As long as the radio is tuned correctly and VHF2 is selected im able to contact ATC. Again, this works for both keys.

As conclusion: Both keys do the same in realistic mode without the JTAC mod installed. Maybe in easy mode the PTT uses the radios as in realistic mode and the communication menu utilizes the easy communication simplifications? Finally, it seems that both keys are different at some level internally as the JTAC mod requires the usage of the PTT button. However, i havent tested the JTAC mod at all so this is just repeated from other posts.

Thanks for your answer. Ive tested this statement in realistic mode. I dont see any difference between using the communication menu or the ptt button except the headline of the menu. If you press communication menu the headline is "Main" and if you use the ptt button the headline states the currently selected radio. Apart from that i dont see any difference. Im able to call the ground crew with the door open and wrong radio selections with both keys. Im not able to call the ground crew with the door closed unless the intercom is selected. This works for both keys. ATC works as expected with both keys. As long as the radio is tuned correctly and VHF2 is selected im able to contact ATC. Again, this works for both keys.

 

As conclusion: Both keys do the same in realistic mode without the JTAC mod installed. Maybe in easy mode the PTT uses the radios as in realistic mode and the communication menu utilizes the easy communication simplifications? Finally, it seems that both keys are different at some level internally as the JTAC mod requires the usage of the PTT button. However, i havent tested the JTAC mod at all so this is just repeated from other posts.

Interesting. Perhaps an update has changed things but I do recall people being unable to even get the Radio menu to appear until they setup and used the SPU-9 key rather than the simple radio key.

Interesting. Perhaps an update has changed things but I do recall people being unable to even get the Radio menu to appear until they setup and used the SPU-9 key rather than the simple radio key.

They changed it with one of the DCS World updates long ago...

In this post I explain how you can use your old profile with the new SPU-9 combo...

http://forums.eagle.ru/showpost.php?p=1509178&postcount=32

Any plans to port your awesome mod to the huey? Its looking like they may not have implemented it.

I was reading a post from someone and he said: If the A10C has JTAC, then why is it not possible to add it for the KA-50?

Just an inquiry does your jtac v1.3 still work with the new dcsw 1.24 system, or does it need a rehash.

Cheers, Ian.

I can contact with the JTAC in the Fast Mission creator, but they say there's nothing I can do. Any idea? There are plenty of targets in F10 map.

I can contact with the JTAC in the Fast Mission creator, but they say there's nothing I can do. Any idea? There are plenty of targets in F10 map.

Try with the special mission that I've made for it?

And it should work OK. I was able to use JTAC with 1.2.4 but I don't know about today's update.

Next step JTAC for UH-1H ? Would be great!

Next step JTAC for UH-1H ? Would be great!

Having problems implementing it. Miniguns are probably not recognized as a valid weapon yet as there is no sound file for it and scores or hits are not detected when using the minigun. The Check-in line and remarks won't work so this mod is not ready for a Huey version, yet.

Try with the special mission that I've made for it?

 

And it should work OK. I was able to use JTAC with 1.2.4 but I don't know about today's update.

Will try tonight and get back with the results.

You have an error. Jtaс does not issue corrections. if the mission is AAA.

Look in the file NATO can be there.

v 1.2.4

You have an error. Jtaс does not issue corrections. if the mission is AAA.

Look in the file NATO can be there.

v 1.2.4

Could you check out if the following two attached files fixes the problems?

NATO.lua goes into: ...\DCS World\Sounds\Speech\NATO.lua

comm.lua goes into: ...\DCS World\Mods\aircrafts\Ka-50\comm.lua

comm.zip

NATO.zip

I will apply the mod from scratch using the updated files.

I will wait untill 1.2.5 as ED is suggesting that 1.2.5 will fix the remaining bugs, suggesting that their focus will shift to the unfortunately-not-dcs-at-all F15 and SU27 modules and maybe that desert.

I will be abroad for a month in june but I hope to release JTAC 1.4 right or sometime after the 1.2.5 update.

I'm also looking into the possibility to add JTAC to the Huey. I need some DCS world sound files that I hope will be added to the default installation in a future update. At the moment I can't get it to work.

EDIT:

Disregard, see below!

Could you check out if the following two attached files fixes the problems?

 

NATO.lua goes into: ...\DCS World\Sounds\Speech\NATO.lua

comm.lua goes into: ...\DCS World\Mods\aircrafts\Ka-50\comm.lua

Works with the Ka-50.:)

Does not work with the A-10.:(

But if you replace the file in the default NATO. That JTAC with the A-10s works.

So the file gets JTAC to work for the Ka-50, but then breaks it for the A-10?

Need tester for V1.4. I'm interested in people who encountered problems with v1.3 in DCS 1.2.4. PM me.

I simply ported all lines associated with the JTAC mod to the corresponding DCSW v1.2.4 files.

It works for me so now I only need a couple of people to confirm that v1.4 is ready for release. :thumbup: