Radio Patch for DCS v1.1.1.1 v1

[Snaut]

Anyone care to check the radio volume buttons. The volume control buttons for the VHF AM and UHF radios seem to be reversed ? Anyone else seeing this.

 

Yes, I just noticed UHF button affects VHF radio.

[Speed]

Yes, I just noticed UHF button affects VHF radio.

 

Considering I didn't touch any of the scripts dealing with the aircraft's radios (I don't even know offhand where those scripts are), and only modified the scripts that govern what the AI say on the radios, and that NATO.lua and common.lua live in their own separate module namespace from anything that actually does control aircraft radio knobs, one can be reasonably certain that this mod has nothing to do with that.

Edited April 20, 2012 by Speed

[Snaut]

Sorry, I wasn't clear enough, it happens with the clean install.

[FMano]

Radio Russia

 

-Thanks a lot for your work!!!

Nato radio calls are working perfectly precise now!

 

I still have problems with Russian radio calls,

and maybe you could help?

 

-First thing is, Russian bulls-calls seem to measure in METERS?

Doesn't make sense to me, at least not while operating the A-10C and measuring MILES and FEET.

Is this an option that can be changed somewhere in the ME?

 

-Other thing is, Russian AWACS doesn't seem to be functional.

Well, it seems to be working, at least it talks, but the only thing I get is "BRA.." and then, nothing else!

Is this happening on purpose or is it a publicly known problem or is there something wrong with my system?

And, is it possible to transfer all that NATO-talk to the Russians, so that I can have the same functionality as the blue team?

 

It would be nice if one could create missions with blue and red being more or less equal. (I also have problems with Russian tanker/refueling and FAC/JTAC)

 

Any help/idea is very much appreciated.

[Speed]

-Thanks a lot for your work!!!

Nato radio calls are working perfectly precise now!

 

I still have problems with Russian radio calls,

and maybe you could help?

 

-First thing is, Russian bulls-calls seem to measure in METERS?

Doesn't make sense to me, at least not while operating the A-10C and measuring MILES and FEET.

Is this an option that can be changed somewhere in the ME?

 

-Other thing is, Russian AWACS doesn't seem to be functional.

Well, it seems to be working, at least it talks, but the only thing I get is "BRA.." and then, nothing else!

Is this happening on purpose or is it a publicly known problem or is there something wrong with my system?

And, is it possible to transfer all that NATO-talk to the Russians, so that I can have the same functionality as the blue team?

 

It would be nice if one could create missions with blue and red being more or less equal. (I also have problems with Russian tanker/refueling and FAC/JTAC)

 

Any help/idea is very much appreciated.

 

Any idea if it was like this before the "Radio Patch"? I didn't test Russian comms at all, to be honest, but I thought they would be just fine.

 

Anyway, what units a country uses for radio comms can be changed in ./Sounds/Speech/common.lua. Look to line ~78 (the "~" means approximate- I or you may have made Lua edits to make this line different), which should be the beginning of the "countryUnits" table. For example, if you want to change Russia to imperial (nautical miles and feet instead of km and m) then change line ~79 from:

[base.country.RUSSIA]			= unitSystems.metric,

 

to this:

[base.country.RUSSIA]			= unitSystems.imperial,

 

I think that's all that is necessary to affect this change, but I haven't tested it myself. Don't forget the comma at the end of the line.

Edited May 7, 2012 by Speed

[FMano]

-And again, thanks a lot!!!

That was easy to fix!

 

Any idea about or comment on the AWACS-problem?

 

Russian bulls-calls are as precise as Nato's now.

(It's just a pity the guys sound quite retarded)

 

But from the Russian AWACS I only get a call like "BRA-" followed by silence.

No bearing, range or altitude at all, just silence.

 

Unfortunately I don't know how the Russians behaved before the patch, sorry.

[Speed]

-And again, thanks a lot!!!

That was easy to fix!

 

Any idea about or comment on the AWACS-problem?

 

Russian bulls-calls are as precise as Nato's now.

(It's just a pity the guys sound quite retarded)

 

But from the Russian AWACS I only get a call like "BRA-" followed by silence.

No bearing, range or altitude at all, just silence.

 

Unfortunately I don't know how the Russians behaved before the patch, sorry.

 

Ok, I just tested the behavior.

 

Without the Radio Patch mod, Russian AWACs calls do not work. I just get "BRA" and that's it. With the Radio Patch mod, I get the same behavior.

 

I'm sure this is something I can fix, but with a new A-10 patch coming up... I'm not sure if it's worth my time trying to fix this one now. Once we get the A-10C patch for DCS world, if this bug still exists, then I'll look about fixing it.

[FMano]

Great, thanks!

 

I hope, the DCS-guys know about the problem.

 

And, strange that nobody else has noticed before.

At least I couldn't find a hint.

 

Anyway, your work is a big help, thanks again!

[Speed]

And, strange that nobody else has noticed before.

At least I couldn't find a hint.

 

Well, you need to be flying a Russian aircraft, have an A-50 airborne on AWACs, be properly tuned, have bandits airborne, and call the AWACs to notice it. Once all those factors stack together, this bug has a very high probability of being missed. And for it to be reported, if the person is not an ED tester then someone needs to make a forum post about it. So not really that strange. Good job taking the initiative and posting about it! Regular forum members can be the second line of defense against bugs, especially if they take the time to properly characterize bugs and report them in a clear and concise manner.

 

Anyway, if this one still exists in DCS: World, I will take the time to fix it and also create a decent bug report on it. Well, I can probably fix it, but even if I can't, I should certainly at least be able to pin down what is malfunctioning in the code.

Edited May 9, 2012 by Speed

[FMano]

It's good to have the opportunity to talk about those things here on this forum and find help!

A friend and I bought the DCS A-10C just a few weeks ago, so we are still quite new to this whole world.

And from the beginning we tried to create missions with both sides, blue and red, being more or less equal, so that we could fight against each other.

Just, that you can understand my intention.

 

And, concerning equality we noticed this AWACS problem, but also, we have problems with the Russian TANKER. Wich answers the call for refueling, but obviously has no device and functionality for giving fuel to another aircraft.

 

So, I know this it not the right place to ask and I don't want to get on your nerves, but maybe you can tell me where to go with this. Or shall I better forget about the whole equality idea?

 

Anyway, thanks for your work!

[Jona33]

As for the tanker that's a difference in the way the USAF tanks and the way the rest of the world tanks. Basically, to tank: one plane has a hole, the other a probe. For the USAF the tanker has a probe and the receiver a hole. For Russians it's the other way round. Obviously that means the A-10 and the RUS tanker have holes so it doesn't work.

[Gisen]

Dcs world

 

Does this work/ is this needed in DCS world?

If so is it installed the same way?

Thanks!

[Gisen]

Anyone tell me how to install in DCS world?

[Jona33]

Don't know if it's needed, haven't checked yet.

[nAyo]

Version 1.2.0 has been released :

http://forums.eagle.ru/showthread.php?t=90967

 

For some reason, they didn't decide to fix this radio comms issue even though it's a very known and terribly annoying bug. So what about it now? this v1 patch doesn't work anymore, I tried. Will you work on a 1.2.0 version of it or?

 

Once we get the A-10C patch for DCS world, if this bug still exists, then I'll look about fixing it.

This is making me optimistic :D

Edited July 11, 2012 by nAyo

[kobac]

It would be great if Speed would adapt this very useful mod for DCS World 1.2.0.

[Speed]

It would be great if Speed would adapt this very useful mod for DCS World 1.2.0.

 

Well.. how many of the bugs were fixed? I haven't gotten a chance to test myself yet.

[nAyo]

# Azimuthal error removed from bullseye radio calls

No clue, it's a detail I didn't pay attention to yet.

 

# Bullseye calls now work for multiplayer clients

Not fixed, ranges given are still huge and irrelevant.

 

# JTAC Remarks "table index is nil" Lua error fixed

No clue, the bug didn't occur for me.

 

# UTM grid zone added to JTAC radio comms

Not fixed, the grid is not given.

 

# Tanker is not properly located by the AWACS also.

[FMano]

Concerning AWACS, esp. Russian AWACS:

 

I tested the AWACS in DCS World A-10C Module today.

http://forums.eagle.ru/showthread.php?t=88808

 

Nato and Russian AWACS were both working fine.

As far as possible I compared the AWACS calls with TACAN and steerpoint read-out.

Appears to me the difference is small.

For example approx. 5 degrees at 15 miles, or 7 degrees at 26 miles distance.

The numbers could have been my fault, but there definitely is a difference.

Maybe a Radio Patch for DCS World could fix this?

[parxuk]

Still playing 1.1.1.1 as dcs world a10 is jerky as hell for me so am very grateful of this fix, thx.

[Speed]

# Azimuthal error removed from bullseye radio calls

No clue, it's a detail I didn't pay attention to yet.

 

# Bullseye calls now work for multiplayer clients

Not fixed, ranges given are still huge and irrelevant.

 

# JTAC Remarks "table index is nil" Lua error fixed

No clue, the bug didn't occur for me.

 

# UTM grid zone added to JTAC radio comms

Not fixed, the grid is not given.

 

# Tanker is not properly located by the AWACS also.

 

Thanks, I'll check out the "Tanker is not properly located by the AWACs" issue. Unfortunately, it looks like the fix for client bullseye didn't make it into the release version of 1.2.0. Hopefully, next patch it will. I haven't checked the JTAC remarks issue yet.

 

Anyway, I guess I'll make a radio patch for 1.2.0 once I get done with a few more things for Slmod.

[WildBillKelsoe]

I'm crying!! :...(

 

This made me happ'e...

[cichlidfan]

Unfortunately, it looks like the fix for client bullseye didn't make it into the release version of 1.2.0. Hopefully, next patch it will.

 

Would it not be easier to figure out why so many things that the testers were told would be fixed in the patch, were not. The fix already exists.

[WildBillKelsoe]

guys, I installed it manually. please correct me, I can't hear the JTAC except his remarks.

 

1) Open up your DCS install directory.

2) Rename the file "debriefing.lua" in ./Scripts/UI to "debriefing_original.lua".

 

regarding renaming these files, do I add .lua to the filename, or just to the L in _original?

 

6) Paste the "delimeter-begin.wav" and "delimeter-continue.wav" files into ./Sounds/Speech/Sound/ENG/Common/JTAC/Alphabet, AND ALSO PASTE THEM INTO ./Sounds/Speech/Sound/ENG/DCS A-10C/Player/Alphabet if you are installing into A-10C, and/or ./Sounds/Speech/Sound/ENG/DCS Ka-50/Player/Alphabet if you are installing into BS2.

 

I've pasted the delimeter beg and cont to both ka-50 and a-10 player alphabet folders.

 

why can't I hear the JTAC?? before I did that, I had it working the opposite.

 

meaning I heard the 9 line, but the remarks were broken.

 

now the 9-line is broken and the remarks are functional, except on few occasions. I want to fix it once and fur alle.

[Speed]

guys, I installed it manually. please correct me, I can't hear the JTAC except his remarks.

 

1) Open up your DCS install directory.

2) Rename the file "debriefing.lua" in ./Scripts/UI to "debriefing_original.lua".

 

regarding renaming these files, do I add .lua to the filename, or just to the L in _original?

 

6) Paste the "delimeter-begin.wav" and "delimeter-continue.wav" files into ./Sounds/Speech/Sound/ENG/Common/JTAC/Alphabet, AND ALSO PASTE THEM INTO ./Sounds/Speech/Sound/ENG/DCS A-10C/Player/Alphabet if you are installing into A-10C, and/or ./Sounds/Speech/Sound/ENG/DCS Ka-50/Player/Alphabet if you are installing into BS2.

 

I've pasted the delimeter beg and cont to both ka-50 and a-10 player alphabet folders.

 

why can't I hear the JTAC?? before I did that, I had it working the opposite.

 

meaning I heard the 9 line, but the remarks were broken.

 

now the 9-line is broken and the remarks are functional, except on few occasions. I want to fix it once and fur alle.

 

Did you install it into 1.2.0? This is for DCS 1.1.1.1.

 

Also, the file names, "_original" etc, those could actually be any name. "_original" is just to allow you to easily identify the original files.

 

Also, go into folder options for windows (search "folder options" from the start menu), and uncheck "hide file extensions for known file types". That's a horrible option that should be removed from windows. It's a really freaking terrible idea to hide such vital information as file extensions from users.

 

Anyway, if you still have issues, try to use JTAC, then immediately upload dcs.log to the forums.

 

I did create a minor fix for the JTAC no remarks problem, FOR 1.2.0, get it here: http://forums.eagle.ru/showpost.php?p=1524369&postcount=11

 

I'm thinking about finally getting a radio mod created for 1.2.0 soon. As in, if I'm going to do it, it will be in the next few days. Understand it's also a question of whether my time spent on DCS is better spent making a mod to fix some issues, or finding issues and reporting them so that a mod is not needed in the first place. Also a radio patch for 1.2.0 would be incompatible with that Ka-50 JTAC mod by Turbohog, so we would need to possibly include both mods as one...