Aries Radio System

[towsim]

@astiles5470

If it helps, you may continue with 3.0.14. The versions before 3.0.14 do have an older internal API level define by TeamSpeak. This prevents using the current radio version with TeamSpeak < 3.0.14. But I am afraid, that the DirectX issue (if it exists) came up before 3.0.14.

[CallsignFrosty]

Hi,

 

it was my fault. Something was wrong when I updated from 3.0.14. After reinstalling TS 3.0.15 from scratch everything worked again. Yesterday we had a test with different DCS mods and it was quite satisfying. We will keep testing.

 

BTW, some people in my squadron fly with Saitek X-55 and used Saitek's software to develope their profiles. It seems there is an issue with Saitek's software since the last TS versions doesn't support Direct Input, so they keep working with and old TS version. Therefore they are unable to use Aries. I'd like to ask you if somebody in your group is using X-55 hotas with Saitek's profiles aswell and, if it is the case, which solution they found.

 

Thanks again

 

Ok so I am using X52 pro, maybe the software is the issue for me too. I love the software but the implementation seems so buggy and weird.

[towsim]

As promised, the bug fix version 1.931 is available at

http://www.ariescon.com/index10.html

The Version 1.931 does not include any new function. It is a simple bug fix. If you are happy with version 1.930, you need not to upgrade.

It is important to uninstall any older version of Aries Radio before you install the bug fix (even version 1.930). Your configuration will be saved automatically.

The manual installation package is upgraded to version 1.931 as well.

Bugs fixed in version 1.931:

Radio DLL

 

 

• 
  
• The 'Pop/Hide Radio GUI'function can now be used with the keyboard
  
• The evaluation of keystrokes is reworked. Now it is for sure, that modifier + key is well separated from key only.
  
• The bug, that DCS crashes if you start with a Combined Arms Vehicle is solved.
  

Installer

 

• 
  
• The edit fields for the Open Beta path definition works normal now.
  

Quick installation Guide

 

• 
  
• Some typos solved
  
• Added some explanations for the use of keystrokes for frequency dialing.
  

[Esac_mirmidon]

Hi Towsim.

 

I really appreciate your constant work to improve an update your ARIES radio system. Thanks for all.

 

I will try to explain my problems to make ARIES works properly.

 

This new version is the first i´m able to make it work every time i running it. The radio box is showed OK, the channels, radio activation and the hide options works as intended. But i have a persistent problem with my X-55 HOTAS and the radio assignation functions.

 

I use a Saitek X-55 with the RHINNO software to load profiles.

 

Team Speak only works for me on direct input ( with old versions ) , or using the Keyboard & Mousse only function when i load a profile for my X-55. If i use Default setting, my profile turns crazy. It starts to press by itself all the functions programmed without control and every press of a button or a switch is always showed as double, triple or continuous pressure.

 

Changing to Keyboard and Mousse solves this issue but i have to face another problem.

 

Randomly, when i change a profile for a different DCS module, the X-55 HAT assigned for every radio, to hide the radio box and the PTT programmed stops working. Not only any touch over the X-55 HAT don´t have any reaction but also using the keyboard with the same key combo don´t cause any effect over the ARIES program.

 

Then the only solution i have found is close DCS, close Team Speak, Close RHINNO Software and start open every application again. First TS, and reloading the ARIES pluggin, then the RHINNO software and at last loading the dessired profile.

 

Doing this makes ARIES work again, and the radio box works perfect, with every HAT pressure recognized, the box again hides and shows and my PTT is OK again.

 

Another problem is that i´m suffering persistents crash when quit for a mission. This is also happening randomly without any apparent cause. I get the " DCS Stops working" right when i hit the QUIT option from thre ESC menu.

 

 

Please forgive my bad english and if you have any suggestion about my problem or you need more info about it i will thank you for any help.

 

Thanks again.

Edited June 27, 2014 by Esac_mirmidon

[towsim]

@Esac_mirmidon

It is hard to predict any working solution. You should first check your Rhino profile if the buttons a configured to produce pulse, repetitions or any others. Most applications and even Aries Radio and DCS, expect simply a push and a release signal. My first question would be, if your troubles appear even with Aries Radio deactivated. The only logic I see, comes from the loading sequence.Any device like joysticks or throttles can be interrogated by any running software via Direct Input. The program calls an initialization function and will be inserted in a data delivery chain for the device. And this could be the point. The last loaded software is the first in the chain. Every application in the chain may modify the data. What I assume in your case is, if loading the Rhino driver as the last, it will be the first in the chain. All modifications made by Rhino are given to the subsequent applications like TS3 and Aries as well as DCS. The modifications made by Rhino are that what the other programs expect. Vice versa, if Rhino is the last in the chain (loaded first), all applications get the raw data from your X55 which could be unreadable for most of the programs. This is only an assumption. I would ask any X55 specialist here in the forum , if they experience the same situation and have probably a solution.

Regarding the crash at the end, please send the session's log files from

 

Users\[username]\Saved Games\DCS\Logs (.log and .crash)

and

DCS World\AriesWings\logs\AriesAirborneRadio_log.html

 

to support@ariescon.com

Edited June 28, 2014 by towsim

[CallsignFrosty]

just wanted to say, this update fixed my problems!

 

Cheers towsim

[Esac_mirmidon]

Thanks for your reply Towsim.

 

It seems that my problem with the X-55 profile when its loaded shows with or without ARIES software running. The only way to stop suffering continuous undesired buttons strokes is using Direct Input mode or Keyboard & Mouse only.

 

In my profiles all settings are recorded as buttons and only push and release. No macros or continuous action in any way for any switch, button or hat.

 

Talking about the software loading order. What is better to be loaded first? The X-55 profile software? Or this must be running at the very last moment, after Team Speak?.

 

Thanks for all.

 

Im gonna send you my crash logs to your email about my crash problems.

[towsim]

@Esac_mirmidon

according to your statement:

Then the only solution i have found is close DCS, close Team Speak, Close RHINNO Software and start open every application again. First TS, and reloading the ARIES pluggin, then the RHINNO software and at last loading the dessired profile.

you should load the Rhino as the last. After thinking a bit about the sequence it seems, that it is vice versa to that what I explained in Post #258. If you load Rhino first, it will be the first in the chain and sends its messed data to succeeding applications. But I think you should first test, if you can set your configuration inside DCS without the Rhino Software. I do the same for my ThrustMaster Hotas. I do not use the Target Software. All applications get the data directly from the device. It is a bit tricky if you deal with 3 position switches. But it is possible.

[astiles5470]

Hi,

a colleague in my squadron has told me that in the Signal Distribution Panel of the Huey, only he is able to change the switch into three positions. He can't use neither the Intercom nor the position 4 of the switch.

 

Thanks

[towsim]

@astiles5470

The bug is confirmed. It will be solved with the next release.

Thank you.

 

P.S.

The bug is solved. The entire switch logic is reworked. It is possible now to dial other position than 1,2 or 3.

The rotary switch selects now

1 = VHF AM (was 3 before)

2 = UHF

3 = VHF FM (was 1 before)

The receiver switches are now integrated. It is now possible to switch a single receiver on or off.

Edited June 30, 2014 by towsim

[Home Fries]

@Towsim,

 

This looks awesome, especially with the Line of Sight/power updates you have done.

 

I made Aries Radio compatible with my TARGET profile (see my signature), at least so far as Flaming Cliffs goes. However, I was wondering how the press to talk function is implemented for the other planes.

 

Do you use the standard PTT key (in my case DX21) for the P-51, Ka-50, and UH-1 and the message is filtered by frequency and (except for the P-51) radio selector? Or do I need to free up another PTT key for Aries Radio functionality. Also, how are the three radios in the A-10C handled? Do they use the same PTT buttons as the three FC3 radios, or do they use the common PTT with the last radio selected being the active radio (again, like FC3)?

 

With the FC3/CA radio setup, is it alright to use my standard PTT key for one of the radios (i.e. Radio 1/VHF AM), or should that only be used for Common?

 

Do I need to program any other buttons used for other channels as PTT in TeamSpeak 3?

 

Is it possible to use combinations or modifiers for the radio frequency change keys (i.e. DX30+DX15, using a modifier like DCS)?

 

Thanks in advance.

Edited July 3, 2014 by Home Fries
removed wrong answers

[Home Fries]

Possible bug report for 1.931:

 

In Teamspeak, when selecting Export.lua entry on/off in the Plugins pull-down, if the user does not have an Export.lua in DCS\scripts then he gets a dialog box saying that export.lua could not be found.

 

Perhaps modifying the routine to create export.lua if one does not exist would be a fix.

 

 

EDIT: One more report:

 

If you use an aircraft with multiple radios (i.e. A-10C) and leave radio 2 or 3 as default, then when you get into the P-51 with a single radio it isn't selected by default. You need to have that radio selector mapped to your P-51 HOTAS, even though the VHF is the only radio. Recommend coding the P-51 so that the default radio is automatically radio 1.

 

Regards,

Edited July 3, 2014 by Home Fries

[Robin_Hood]

This new versions looks pretty good, I must say! :thumbup: There is only one thing that is bothering me: is there a way to tune the background noise level (volume)? As it stands, my team mates and I find it kinda high, and it really garbles the transmission. I'd hate to turn it off, because I think it brings a lot of immersion, but I'd love to reduce it, say, by half.

 

Is there anyway (preferably simpler than messing with sound files) to do it? I looked in the manual, but didn't find anything about that.

[towsim]

@Home Fries

The use of PTT is completely up to the user and independent of TeamSpeak.The following rules apply:

 

 

• 
  
• As soon as you are in the game, the TeamSpeak PTT has no function anymore.
  
• Radio Box select for a single radio box works even as PTT.
  
• Common PTT, if defined, can be used, regardless of what box is selected for the moment. Even this key is completely independent of TeamSpeak.
  
• Voice activation, if used, it must be configured in Teamspeak and in Aries Radio.
  

FC3 radios and CA radios cannot be configured with different keys. The key definitions for box select and PTT applies to all models.

Modifiers can be defined only for keyboard use. If you use a device like joystick or throttle, only single buttons are evaluated.

Configuring buttons or keys for Aries Radio should always be observed with the DCS configuration. If you configure Joystick button 2 as PTT in Aries Radio and as Toggle Gear in DCS, you will move the gear every time you use PTT. But PTT works as well as toggle gear.

 

I will have a look to the P51. It is a good idea to enable the box automatically if only one radio is available.

The Export.lua activation/deactivation has a confirmed bug. It will be solved for the next bug fix release.

 

 

 

@Robin Hood

You may open \DCS World\AriesWings\ AriesAirborneRadio.ini with a text editor. At the end of the file you find some sections like [A10C_mod]. The numbers you find in PRIMARY_BUFFER and after the BKGND_nnn keys are intensity definitions.If you lower the number for any BKGND_nnn definition, the volume for this sound will be decreased. I promise to install a slider in the configuration program for this case. You need to make the changes for each player in your community. If it is done only in your INI file, only your voice will change in radio communications.

[Schleudi]

@Robin Hood

 

 

You can influence the level of the background noise in \DCS World\AriesWings\ AriesAirborneRadio.ini.

At the end you find sections for some types I support with sound mods.

There are numbers defined in PRIMARY_BUFFER and for each SND file. The numbers define a relation for the noise levels.

 

• PRIMARY_BUFFER is the level of the pilots voice.
  
• BKGND_ENGINE is the noise sound and level of the engine
  
• BKGND_COCKPIT is for the moment onl y a sound of streaming air. Same for each vehicle.
  
• BKGND_SILENCE (not supported for the moment) would be electrical generator and similar during startup.
  

 

The A10 has a relation of 99:3:5:0. if you increase the number 3, the engine noise becomes louder. Decreasing a number decreases the corresponding sound. Only integer values are accepted.

 

HULL :

the first value defines a frequency, how often per second a rotor or propeller blade passes in front of you. This is a combination of RPM and number of blades. The second number defines the decrease of loudness per pass in percent. The values 10 70 say, that the pilot voice is reduced 10 times per second by 70%. This produces the typical voice vibration of a Huey pilot.

You should keep in mind, that every change of these values effect only your local configuration. The results are audible for your fellow player only. It would make sense, if all participants have the same configuration.

 

The sound files contain 16 bit samples, mono, 48 kHz, raw format. You may fill in any sound in a file, even an opera if you like.

[Home Fries]

@Home Fries

The use of PTT is completely up to the user and independent of TeamSpeak.The following rules apply:

...

Thanks, Towsim.

 

I have to agree that I like what you've done with this version of Aries Radio. Had a chance to test it with a couple others last night and it worked well. I also think that the Mode IV implementation is genius. Looking forward to see that fleshed out.

 

I also agree with the suggestion about the option to reduce the static in the background. Perhaps the static gets its own slider on each radio and can also be dynamically adjusted using your existing range/power/line of sight algorithm. I didn't try the KY58 encryption on the A-10C, but I know from experience that when you go secure you don't hear static (it's all filtered out by the crypto); the static only hinders sync with other encrypted devices on initial transmission (think of a telephone modem on a dirty phone line).

[Robin_Hood]

Thank you! I only have an [A10C_mod] section, will that change the level globally? (I feared it would work only when flying the A-10C).

[Home Fries]

Another question (this is for working my TARGET profile):

 

For people who don't use PTT Common for A-10C/FC3, but instead use PTTs for each specific radio, which PTT is used for the P-51, Huey, and Black Shark (all of which have a common radio trigger/button)? Does a PTT Common need to be mapped for these, or do they default to one of the other boxes (i.e. Radio 1)?

[chromium]

@chromium, is the bug observed even in the New Version?

 

Hi,

 

we tested it for 2 evening, it works if:

 

1. PIlot enter in a slot, either C&D or already in flight, he will hear everyone from any channel (bug still there)

2. Than pilot go to spectator and re-enter a C&D cockpit: now it seems to work as intended, pilot can speak and hear only the same frequency of others.

3. Only for me there are some PTT issue (sometimes doesn't work) but I think it's a mine problem.

[towsim]

@Robin Hood

The main flight models have their own definitions. All the rest defaults to a standard background sound you should find the following sections:

[uH1H_mod]
FILTER=8
VOICE_MOD=1
HULL=10 70
PRIMARY_BUFFER=99
BKGND_ENGINE=UH1engine.snd 10
BKGND_COCKPIT=UH1CockpitNoise.snd 5
BKGND_SILENCE=UH1preStart.snd 0

[A10C_mod]
VOICE_MOD=1
FILTER=8
HULL=0 0
PRIMARY_BUFFER=99
BKGND_ENGINE=jet1.snd 10
BKGND_COCKPIT=UH1CockpitNoise.snd 5
BKGND_SILENCE=A10preStart.snd 0

[KA50_mod]
FILTER=8
VOICE_MOD=1
HULL=20 70
PRIMARY_BUFFER=99
BKGND_ENGINE=heli2.snd 3
BKGND_COCKPIT=UH1CockpitNoise.snd 5
BKGND_SILENCE=UH1preStart.snd 0

[P51D_mod]
FILTER=8
VOICE_MOD=1
HULL=80 70
PRIMARY_BUFFER=99
BKGND_ENGINE=Prop1.snd 4
BKGND_COCKPIT=UH1CockpitNoise.snd 4
BKGND_SILENCE=UH1preStart.snd 0

[chromium]

Does a PTT Common need to be mapped for these

 

Using only Ka-50, I use the common PTT only. This allowed me to set the SPU-9 rotary switch on the hotas and use the PTT as the real one.

[towsim]

@Home Fries

On startup, Aries Radio assumes three radios per model. The key definition in the configuration bases on this assumption. Once the model is loaded, all non existing radios are deleted internally. If you take the P51, two radios are deleted and only box 1 remains in place. Therefore the configuration for box 1 applies. In case of the KA50 with two radios, the configuration for box 1 and box 2 apply. For non supported models like MI8 (will be supported if an English labeled cockpit is released) or FC3 or CA, all three radios remain in the game and the corresponding configuration for the boxes apply. Once you decide to use common PTT, then it is used for all models. It is not possible to have different buttons for box select with each model.

Edit:

You can even configure the different rotary switches for Box select directly in the DCS options. Chromium obviously used this clever solution. Only the PTT signal is mandatory to be in the Aries Configuration

Edited July 4, 2014 by towsim

[towsim]

@chromium

this was a valuable information in your post # 272. Now I can compare the difference in the initialization sequence of the two situations. I keep you informed about the result.

Thank you

[chromium]

@chromium

this was a valuable information in your post # 272. Now I can compare the difference in the initialization sequence of the two situations. I keep you informed about the result.

Thank you

 

You're welcome! :)

 

we are really looking forward to ARIES capabilities: I hope you will overcome those issues, even if now it should be usable anyway :).

[Robin_Hood]

Thank you again, towsim.

 

Just to make sure I get this right: if instead of

[A10C_mod]
VOICE_MOD=1
FILTER=8
HULL=0 0
PRIMARY_BUFFER=99
BKGND_ENGINE=jet1.snd 10
BKGND_COCKPIT=UH1CockpitNoise.snd 5
BKGND_SILENCE=A10preStart.snd 0

I write the following

[A10C_mod]
VOICE_MOD=1
FILTER=8
HULL=0 0
PRIMARY_BUFFER=99
BKGND_ENGINE=jet1.snd 5
BKGND_COCKPIT=UH1CockpitNoise.snd 2
BKGND_SILENCE=A10preStart.snd 0

Then others will hear less background noise when I speak while I'm flying the A-10C (but not if I'm flying a P-51D or an F-15C), right?

 

If I may put your patience to the test and bother you one more (hopefully last) time, I suppose FC3 and other "partially supported" aircrafts (Mi-8 ) use some default configuration. Is there a section defining that?

 

Specifically what I want to do is lower the background noise, and as I'm flying FC3 aircraft, that is the bit I'm looking for.

 

I'm sorry this must be rather obvious to you.