towsim

Yes, this was one of the reasons.

Dear Aries Users, We are almost ready for the new release of Aries Radio supporting DCS V1.5xx and DCS V2.0xx. There is only one minor bug to be solved, which will be repaired in the next days. The following changes were made to the Aries Radio System: The registry entries for Aries Radio were moved from HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER. As a result, no administrator rights are needed anymore to use TeamSpeak or other Aries Software. All Aries files are now moved to C:\Users\[user]\Saved Games. They are valid for all different installations of DCS. It simplifies the configuration and upgrades since there is now only one folder to be maintained. With the L-39DC and L-39Za we have an additional intercom channel for onboard communication. It was a pretty hard work to construct the data links and switch logic to simulate a realistic behavior. It was necessary to include a special API for the additional data needed for the intercom. The terrain profile map for NEVADA is integrated. The correct map file for NEVADA or Black Sea will be loaded automatically. Future development Since we have a combination of four software modules from different vendors, it becomes hard to create a stable release because of unknown and undocumented behavior and side effects. Therefore, we have decided to test the possibility of a special developed voice communication system, that fulfills all requirements for radio communication and radar simulation. If the performance tests show a positive result then Aries can offer a build in communication system which even supports Radar, IFF/SIF air to ground, multiple transmitters for ATIS and/or music radio stations. A special advantage will be for public servers running the Aries software. If a DCS client connects to such a server, he is automatically connected to the communication group without any configuration needs. We do not want to replace TeamSpeak at all. TeamSpeak will still be needed for briefings and other communications beside a running simulation. Nevertheless, TeamSpeak does not support the needs for radio communication. The procedures we use to persuade TeamSpeak to simulate frequency separation is black magic and the behavior is sometimes not predictable. As stated, the final decision will be done after the positive performance tests.

To implement IFF/SIF is not that complicated. We use it already in our ground radar development. For the moment it works only with the A-10C, but is not limited to this type. The transponder answers on mode 1, 2,3A , C and even mode 4. IFF/SIF is not that secretly. Only the encryption codes for mode 4 are classified. The complicated situation is air to air identification. If an Aircraft has an interrogator device, it needs even any type of display to show the responses. This is normally the airborne radar display. To implement the response to be shown on the onboard radar display can only be done by DCS. If someone knows how to mod an onboard radar display, IFF/SIF could be implemented with a simple mod. If someone wants to know how our implementation works:

Aries Radio for DCS V2.x.x Hi Esac_mirmidon, I will send a PM with some details.

Development Status Dear Aries users, here a short information about the coming release: The in-house tests were finalized a couple of days ago and a beta version was released to some beta testers. We already got some results indicating, that the work is not done. Some problems were observed with the TS plugin DLL. I hope to solve the problem within the next days. If we get positive feedbacks for next week I plan a release for Tuesday, March 1st. So far I count on your patience. Regards, TOWSIM

We are on final already. We do not know 10NM or 0.5NM….

Hi Esac_mirmidon, version 2.0 is not supported officially up to now. But there is probably a temporary solution. I will contact you on the PM line.

Default Install Folders means, that TS and DCS reside in the folder, defined during their installation. Aries examines the registry to find the installation path of TS and DCS. If there is a difference between the path, defined in the registry and the actual location then Aries runs into troubles. To answer your special case: If TS was installed on drive E but not moved to that drive after the installation, then all is OK.

Dear Aries user, To keep you informed about what we are doing, here a short explanation for our unusual delay: With version DCS 2.0 we got access to some new API functions, which handle the use of dual cockpit aircraft. This required not only the integration of the API, even some parts of the core software needed a complete reorganization. We are working hard to assemble a stable release. Therefore I beg your patience.

We have a test session this night. We will see...

Working on an answer...

@Schmirco, Yes, the Connect/Disconnect Button manipulates the ‘dofile’ entry in the Export.lua file. If disconnected, the entry is commented out. In this case, the entire Aries radio software is disconnected from DCS. The Aries TS plugin is not disconnected and idles in the background. It becomes active only, if addressed by DCS via Aries Radio.

It seems to be an installation problem or wrong access rights. The message comes up when the program retrieves the path to the Gossip Box from the registry. Do the following: Open the registry editor and go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings\GBO There is a key named ‘InstallationPath’. Check, whether the path matches the location, where the Gossip Box executable resides. Under normal circumstances, there should be an entry like C:\Program Files\AriesWings\GossipBox. If the path is OK, and it does still not work, try to start the GossipBoxConfigurator.exe with explicit administrator rights. If you right click the link icon on the desktop you should see the ‘Shortcut’ tab. Push the ‘Advanced’ button and set the check mark for ‘Run as administrator’.

Hi, greetings to Orlando. I worked there a couple of times for Rockwell Collins. You can use any TeamSpeak server without problems. The plugin functions become active as soon as a DCS mission is started. Outside a mission it behaves like every other TS client. Aries Radio can be enabled and disabled in a TS pulldown menu. If disabled, you can talk to other clients not using Aries during an active mission. I would appreciate any help if offered. Regards, TOWSIM

Don't rush me. We are working on it....

I will post a link for a download here in. It will be explicitly a beta version because we have in house test only up to now.

After intensive testing we have found the reason for our troubles. The new DCS process structure caused an initialization error in our TS plugin. This bug can be solved since we know the reason for it. Nevertheless, it takes a couple of days to reorganize our code. I hope, your patience is not stressed too much. For today I have to close down. I am expected under the Christmas tree. A merry Christmas and a happy new year to all Aries users and a ‘thank you’ to our patient testers…

The 1.97n version is not explicitly developed for DCS version 2.0. The TS crash is mostly caused by missing administrator rights. TS needs to be started with administrator rights. It is not sufficient to be logged in as administrator. The desktop icon has a check mark to be set at properties/shortcut/advanced. If this does not help then please wait on the beta release 1.982. We have minor problems with the L-39C, which will be solved today. The version will be given to those users who reported troubles with version 1.97n.

We have a final in house test this night. Still working in coal-mine...

These are the main improvements in version 1.982: L-39 integrated with one transceiver. L-39 intercom possible with a special, configurable PTT button. The intercom has an own indication in the Aries Radio Panel. L-39 radio communication possible only from the front cockpit. This will be reworked if the switch logic between the cockpits is finalized by DCS. Terrain profile map for Nevada is integrated. The correct terrain file is loaded automatically (Black Sea or Nevada) All registry entries are moved to HKEY_CURRENT_USER. The applications do not need administrator rights any longer. The radio configuration application handles all three versions. Therefore, only one configuration file (AriesAirborneRadio.ini) exist in C:\Program Files\AriesWings\ARD\ApplicationData.

We are on the way. It seems to be a timing problem at the begin of a mission. The best option I can offer is the Beta 1.982. It will be available on next Tuesday. Sorry...

I am sorry for answering late. I was out of office yesterday. @tifafan If you record your communication, you should use a second computer on which TS and the Gossip Box are running. Otherwise your own speech would be recorded without distance and terrain degradation if the recording is done on the same computer. If the recording is done on the second computer with the Gossip Box and TS active, make sure that the geographical location of the Gossip Box is in a suitable range to all participants. The degradation you hear depends on the distance between the Gossip Box and the talking participant. The frequency for recording must be set at least to listening watch in the Gossip Box. @VJS161_FIRE The main difference between DCS V 1.5 and V2.0 is, that every part of the software runs now in one single program. For Aries it does harm anything as long as you do not start a second mission out of a running DCS sim. It would be for interest what Aries version is running and whether all participants run the same version. You should even make sure, that all applications involved are started with administrator rights. A change of the Server has no impact on Aries. It does not deal with the internet addresses of the TS server. There could probably be an issue with the security configuration of the server. Aries uses a hidden channel for data exchange beside the voice channel. In some cases, it was subject of spam issues based on the amount of messages sent per second. But this never led into a TS crash. We even tested the functionality of the Aries 1.97n under DCS version 2.0 and found no issues beside the mission restart. The next version will be 1.982 with some improvements with the security rights. The registry entries are migrated to HKEY_CURRENT_USER so no issues with administrator rights should be observed anymore. Even the Nevada terrain profile is done meanwhile. If the above suggestions do not help, I can only beg your patience. I would give you an access to our latest beta version as soon as the in house tests are completed.

The Germans are not the only members who read this thread.

What did you try ? What did not work ?

Mask Mod is the simulation of voice degradation if a pilot uses an oxygen mask. The result is a voice frequency cut off of high frequencies and low frequencies. In the real world it is caused by the small amount of air inside an oxygen mask. The modification is bound to some jet aircraft in the simulation. It can be switched on and off in the Communication Quality Dialog. The dialog can be activated only if you are active in a game.