Aries Radio System

[Demo]

Are there any public servers using Aries comms?

Would love to try it!

[flanker0ne]

Are there any public servers using Aries comms?

Would love to try it!

 

Is not a server dependent feature.

It's a Community dependet element, it means that you have to organize with your Squad mate's in order to use it.

[Demo]

Is not a server dependent feature.

 

I am aware of that, but I still want to know "how to communicate" on the server.

To be more clear, via what means. TARS? Aries? Just TS?

Edited August 14, 2014 by Demo
misunderstood comms

[aaron886]

I am aware of that, but I still want to know "how to communicate" on the server.

 

Read... the manual? :huh:

[shagrat]

Well, try using normal Teamspeak to chat with people before starting the SIM/activating Aries, for example? Or call your friend by telephone and coordinate the use oof Aries by both. Now choose a "Squad frequency" (standard 251.0 UHF for example) and after you got power to the radios it works like the radio in the real world.

[Demo]

Today I had a problem with preset frequency holding.

When entering the cockpit everything worked just fine, but when I switch presets on the radio, and try to go back to a preset, the frequency of that preset was changed.

For example radio 1 preset 17 was set to Senaki, but I also had flightcomms on radio 1 (preset 11). After going airborne we switched to pr11, did our thing, and for landing we switched back to pr17, but no joy. Checking the freq, it was changed to 118.600?

Checked the ARIES DCS World configurator, and the freq of pr17 was still 132.000 (Senaki).

Any help much appreciated.

 

DCS World 1.2.8.27915

TS3 3.0.16

ARIES V1.940 with DLL (Paulrkii, terrain masking etc)

Edited August 17, 2014 by Demo

[towsim]

The preset configuration, especially on A10c box1 and 3, does not work reliable. This has two reasons. The first is, that there is no standardized way to configure a preset channel with a public lua function. Therefore I tried to simulate the switch sequence on box 1 to set a channel frequency. Unfortunately, DCS uses a switch delay while changing a channel. There is no possibility to determine when the channel is stable after the delay and ready to receive the channel frequency.

The second is an obvious DCS bug in box 1 and box3. After you have configured a preset channel with a new frequency via the cockpit box, the new frequency seems to be stable and usable. If you change the channel now and cross the channel 20 to 1 boundary, you will notice, that the freshly configured channel holds a strange frequency. More confusing, after some channel changes forward and backward, the configured frequency appears again suddenly. Since all models have different radios and different procedures to configure the presets, I decided to delete the function in Aries Radio to configure the presets out of the configuration program. Nevertheless, I will test another procedure in the next days to configure the presets. If that works, I will retain the function and implement the new procedure in the next bug fix.

Even the FW190 shows a curious bug. When I inspect the channel frequencies, I notice, that channel 1 does not hold the frequency specified in the mission editor. Channel 1 holds the same frequency as channel 2. Even here, after some channel changes, the correct frequency appears in channel 1 suddenly.

The next bug fix release will support even the FW190.You will have one radio with the channels 1 to 4. Even the frequency fine tuning is supported. You will hear the speakers voice fading away and the white noise will become dominant when you move the turn button. The propeller frequency will cause some vibration in the pilots voice. The AFN-2 is not supported up to now. I did not find a way to animate the two pointers and the glow lamp of the gauge.

[Home Fries]

Even the FW190 shows a curious bug. When I inspect the channel frequencies, I notice, that channel 1 does not hold the frequency specified in the mission editor. Channel 1 holds the same frequency as channel 2. Even here, after some channel changes, the correct frequency appears in channel 1 suddenly.

 

This might have something to do with it (from p78 the manual):

Because on the first frequency selector position (I) sending and receiving are conducted at different frequencies, it is not used in this simulation.

 

I imagine how the I channel is not implemented in the sim would determine the side effects with the export file (and Aries Radio).

[towsim]

@Home Fries

that could probably explain the result. But I would expect to find the preset frequency set in the mission editor. For the FW190, I do not use any DCS functionality but reading the preset frequency from the radio box. All other logic is handled in Aries Radio internally. It seems to be simply the reliable storage of the frequency value. I will make a note in the manual, not to use channel 'I' explicitly.

[Home Fries]

@towsim,

 

I got to thinking about this. Since channel I receives on that channel but transmits on II, just keeping the voice channel on II might be the best bet. I don't know if it's worth implementing a transmit-only feature, but since Aries is already half-duplex it might be a cool feature to have the lead using channel I to DF while broadcasting commands on II.

[towsim]

good idea, I will have a look whether the Aries logic supports This feature.

[towsim]

Version 1.9491

 

Dear Aries Radio user,

today we released the Aries Radio version 1.9491. It includes the support of the FW190D.

 

New features

The FW190D radio works on channel 2,3 and 4. Channel 1 is normally used for homing. The homing feature is not supported up to now. Therefore it is recommended to use only channels 2,3, and 4 for radio communication.

The frequency fine tuning wheel is supported too. If moved CW or CCW you will notice the voice fading away and the white noise becomes dominant.

 

The homing feature is not supported up to now. It works only conjunction with the in-build DCS radio stations.

 

Frequency setting in the Aries Radio Panel

The digit increment and decrement in manual mode was changed from absolute increment to wrap around increment.

 

Old functionality

shown 129.000 MHz. The third digit (9) was incremented which resulted in 130.000 MHz

 

New functionality

shown 129.000 MHz. The third digit (9) is incremented which results in 120.000 MHz

 

Side effects

Example:

In box 3 VHF FM of the A-10C, the highest possible frequency is 76.000 MHZ. If the last digit is decremented then the frequency 76.075 should appear. Since this value is out of range, no change will be observed. To set 75.075 MHz, the second digit must be decremented first to see 75.000 MHz. Now the last digit can be incremented 3 times to get 75.075 MHz. This limitation is observed only at the frequency band boundaries.

 

Known Bugs

The use of preset channels with the A-10C VHF AM and VHF FM is not reliable. After extensive tests we found the bug in DCS. The bug appears even with Aries Radio deactivated. Because of this bug and the missing possibility to configure the presets remotely, the feature to define the presets with the configurator was deleted. The presets can only be configured with the corresponding cockpit box during runtime. Box 2, UHF AM works normal as expected.

 

The new package can be found at:

http://www.ariescon.com/AriesWingsRadio1.9491.zip

Edited August 24, 2014 by towsim

[Gaanalma]

Great Work!

[Vespa]

Thanks for the great work Towsim.

[shagrat]

There is the issue of integrating it into the install, and who will host the Server for voice? A maximum of 32 players means about 5kb per player if using speex codec, just as an example. Now add that to multiplayer sync and you may not want it to run on your DCS Server in adddition.

A separate server as usual for Teamspeak needs to be hosted by somebody... ok, I know bohemia interactive has it in Arma, but I don't know how they do it, exactly. :D

 

Just my 2 cent, though. It could be much more simple nd I don't know it.

[CallsignFrosty]

There is the issue of integrating it into the install, and who will host the Server for voice? A maximum of 32 players means about 5kb per player if using speex codec, just as an example. Now add that to multiplayer sync and you may not want it to run on your DCS Server in adddition.

A separate server as usual for Teamspeak needs to be hosted by somebody... ok, I know bohemia interactive has it in Arma, but I don't know how they do it, exactly. :D

 

Just my 2 cent, though. It could be much more simple nd I don't know it.

 

I help admin a few arma servers, we run multiple dedi's on the same machine in addition to acre/TFR/acre2 (ive lost track to what we use currently for radios :p) and it runs no problem..

 

I believe it to be a similar situation to that you described, also frequently running with over 40 players

[Hansolo]

TS version needed

 

Hi Towsim,

 

Small stupid question. Which TS3 version is needed. In the manual (v. 1.949) it says >=3.0.9 and in the quick installation guide (v. 1.940) it says >=3.0.14.

 

Cheers

Hans

[Schleudi]

Hi Towsim,

 

Small stupid question. Which TS3 version is needed. In the manual (v. 1.949) it says >=3.0.9 and in the quick installation guide (v. 1.940) it says >=3.0.14.

 

Cheers

Hans

 

Hi HMA,

 

Versions 3.0.14 (64-bit!) and later should be compatible. We are currently using version 3.0.16.

 

Schleudi

Edited August 25, 2014 by Schleudi

[Snoopy]

Last test the 476th accomplished was with the latest TS version.

[Hansolo]

Excellent. Many thanks the swift answer, both of you. Much appreciated.

 

Cheers

Hans

[astiles]

Hi, do you know if an old version of the Team Speak server may limit Aries functionalities or coms quality? Do you recommend last version?

[doveman]

EDIT: Ignore me, I'm stupid!

Edited August 26, 2014 by doveman

[elchacal]

Great work! :thumbup:

[towsim]

@astiles and HMA,

the version of the server makes no difference. All functions used in Aries Radio are official API functions. Therefore they are compatible, even with older server versions. The only restriction is between the AriesRadio.dll and the TeamSpeak client version.TeamSpeak made a change in its internal API version. This change was done with version 3.0.14. Therefore, the current AriesRadio.dll is not compatible with TeamSpeak client version before 3.0.14. For the version 3.0.14 and higher, you need an Aries Radio Version of at least 1.931 or higher. But you should even take care of the Aries Radio version of the other players. You may get contact on a frequency with an older version. But you will miss some features.

[Hansolo]

@towsim.

Thanks a lot for the through explanation. :thumbup:

 

Cheers

Hans