towsim

Actually not. I focused on TeamSpeak because it seems to be „the” voice communication system for DCS. Nevertheless, I will have a look on it…

Unfortunately it is not that easy. You need any connection to DCS to evaluate cockpit switches, frequencies and last not least model positions. Since LUA is limited with its internal capabilities and a nightmare for serious programmers, you will find out very soon, that the only solution is a DLL.Up to this assembly, it is a standalone composition consisting of DCS, a LUA interface and a connected DLL.If I understand right, you suggest a standalone version which has no ‘dangerous’ connection to DCS. This can be already set up. If you use the Gossip Box, you have a standalone radio, but no quality degradation caused by distance and position, because the Gossip Box has a fixed position on ground. The second is the sampling of the voice and the transport over the internet. If that would be easy, then we would have more voice communication software on the market. TeamSpeak is not the best solution for radio communication but at least the TeamSpeak Server is rock solid. The reason why TeamSpeak seems to be unreliable is, that the API does not protect the client kernel against some crude ideas of a programmer (me included). TeamSpeak and DCS do not have the same process space. They are precisely separated. The data exchange is done with a shared memory construction, which ensures, that the one does not disturb the other. So all the functional lacks are not found in the architecture, it is caused by 99.9% anywhere between the earphones of the programmer. Edit: I forgot to mention. Your idea gave me the push to review some software modules. I probably found some enhancements which will increase the stability.

@Dojo and Ramstein Could it be, that the protocol function is enabled in your installation? If yes, please disable it. The protocol system has buffer error which can lead into a crash. The new version for beta testers will be available this week. It includes a new protocol system, completely separated from the simulation. It is an own process. In case of a crash, the simulation is unaffected.

I have to admit, that the terrain shadow map is not up to date. This could be the reason, that the terrain checker detects you under ground or in mountains at some locations.The new map is already measured out directly from the DCS simulation area. Unfortunately, I did not find the time to implement it in Aries Radio up to now. But it will come…

As NeilWillis explained, the quality is basically influenced by distance and line of sight. It is difficult to say, what is bad quality and what is real. We had our discussions in our community when we tried out the voice degradation. After comparing the quality in Aries Radio with real radio communications, we came to the conclusion, that Aries is on the right way. I can remember the situation when we had visitors in my tower cabin. Even when they were native English speakers, they did not understand what was spoken on the radio frequencies.By my experience, it takes about 4 – 6 month for an OJT to understand radio speech adequately. The other is a disadvantage in the model support. Only three models have a build in mask degradation. That is A-10-C, MIg21 and F86. Compared to all other aircraft, they have a poor quality. Nevertheless, all this attributes can be configured or completely switched of in the quality dialog.

That is the tricky thing of DCS, if the volume of the cockpit box is too low, you will neither hear any reception nor see any written text in the top left corner. DCS simulates this as pilot error. Do the following test without Aries: Go onto a frequency of a known station, from which you get voice answers and written answers. Start the communication via the menu. Now turn the volume turn button of the cockpit box slowly down while triggering voice answers from that station. From a certain level on, you do not receive voice or text any more. When you use the volume turn button you should know, that there is no stop mark at the zero position. When you pass the stop mark the volume is set to full level again. The obvious bug, caused by Aries, is a wrong initialization value, probably 0.0 for the volume, on mission start. To circumnavigate this bug, move the volume sliders of the Aries panel once a little bit. The slider value is given to the Cockpit box and the communication should work again.

Unfortunately, I have no experience with Steam. But I assume, that it is normal, that the DCS installation is in the Program Files (x86) folder, even while it is a 64 bit application.Aries expects DCS to have an active folder on start which points in your case to C:\Program Files (x86)\SteamApps\common\DCSWorld.The Aries folder is expected then at: C:\Program Files (x86)\SteamApps\common\DCSWorld\ AriesWings. But this seems not to be the cause of the troubles. If no log file is created in C:\Program Files (x86)\SteamApps\common\DCSWorld\ AriesWings\logs then C:\Program Files (x86)\SteamApps\common\DCSWorld\ AriesWings\ AriesAirborneRadio.dll Was never loaded. Since DCS.log does not complain, that a file was not found, in this case AriesRadio.luac and/or AriesAirborneRadio.dll then there are only two possibilities left: 1. DCS loads a complete different export.lua than expected. 2. DCS does not find an export.lua at its default location at all. In both cases there would be no notice, that something went wrong. If it would find the assigned export.lua then there would be complains in DCS.log if either AriesRadio.luac causes troubles (not found) or AriesAirborneRadio.dll was not found. Edit: The double backslash is not relevant for the moment. The path entry is a preparation for the coming radar applications.

@ApoNOOB DCS.log does not report any troubles while loading the different Aries modules. It takes Aries simply as non existing. It seems, that the required export.lua is never loaded. It is hard to determine from a distance, how your environment was configured. DCS.log says it uses C:\Users\Apo\Saved Games. This implies, that export.lua should reside in C:\Users\Apo\Saved Games\DCS\Scripts. And Export.lua should have the described entries. Compare this path with the registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings\DCSsavedGames. The path found there is that what Aries used during the installation. The paths should be the same down to ‘Saved Games’ You should even have a look in theTeamSpeak menu: Plugins\Aries Radio\Export.lua entry on/off. The dialog should show ‘Aries Wings is connected to DCS World via Export.lua’. But this information bases on the path found in the registry.

No, logs are produced automatically. But the absence of the log file points to a basic problem. The AriesAirborneRadio.dll was not loaded. The load chain is as follows: Export.lua must be at its standard location. Normally C:\Users\[user name]\Saved Games\DCS\Scripts. Export.lua must have the entry: dofile("./AriesWings/AriesRadio.luac"). If there are two minus signs in front (--), please remove them. If AriesRadio.luac was loaded correctly by DCS then AriesAirborneRadio.dll can be loaded, which produces the log file. A good information could be found in C:\Users\{user name]\Saved Games\DCS\Logs\dcs.log. If there are any troubles within the load chain then the file should have an entry, describing the troubles. If possible, send the dcs.log to support@ariiescon.com.

@ApoNOOB I assume you use the version 1.973 beta? If yes, send the following two files to support@ariescon.com : DCS World\AriesWings\logs\AriesAirborneRadio_log.html C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\AriesRadioLog_log.html It should tell me the reason why.

@NailWillis and ApoNOOB Did the advice you got from Neck and HMA solve your problem ?

@Ramstein Sorry for answering late. I was out yesterday the entire day by order of my wife. What I can see from your logs, you are using version 1.970 beta. This version had indeed some memory leaks causing troubles on some installations. I recommend to completely uninstall version 1.970 out of the control Panel/Programs and Features. Then download version 1.973beta from: http://ariescon.com/index10.html The memory leaks are solved in this version. Please keep me informed if this procedure solved your problem.

@NailWillis I assume you get the message: ‘Aries Gossip Box was not installed correctly!’ In this case, it cannot find its INI file. There are two places to be checked: Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings\GBO\InstallationPath Should contain the path: C:\Program Files\AriesWings\GossipBox On the disk: C:\Program Files\AriesWings\GossipBox\ApplicationData should contain the file AriesGossipBox.ini

Aries offers a function in the TeamSpeak Plugins menu called ‘Eavesdropper’. It allows a distress communication across all frequencies between players in game and to gamers off game and vice versa. The only requirement is to be in the same channel.

Release of Version 1.973 Beta Dear Aries user, after series of stress tests with more than 10 users at a time connected, we have now a stable version, which can be delivered to the community. One reason for instability was the internal protocol system. The first measure was to disable the protocol system by default. Nevertheless, the entire protocol system is reworked meanwhile and placed in an own, separate application. The new protocol system will be delivered with the next official release. We recommend to leave the current protocol system switched off, unless it is urgently needed for bug hunting. Before you start the installation, please read the ReadMe1973.pdf carefully. You find the file when you unzip the installer package. The new version 1.973 beta can be loaded down from: http://ariescon.com/index10.html Download 'Aries Airborne Radio for DCS World V1.973 Beta' The beta testers, who received already the version with the radar demo included, need not to upgrade to this official version.

Alle VRS (Voice recognition System) programme unter Windows setzen auf dem Windows-eigenen VRS auf. Das funktioniert eigentlich ganz gut, wenn man midestens einmal die Trainings Session durchgearbeitet hat. Ich tippe auf die Mikrofonqualität. Das VRS reagiert extrem empfindlich auf Umgebungsgeräusche.Ein gutes Mikrofon mit angepasster Richtcharakteristik und eventuell einem Noise Canceling System, kann da Wunder wirken. Es gibt aber auch Personen, deren Stimmlage nicht erkannt werden kann. Das Erkennen der mittleren Stimmlage ist wichtig für die Frequenzzerlegung mit Hilfe einer Fourier Analyse. Dabei werden in der Regel drei Frequenzbänder gewonnen, deren relativer Abstand zueinander ein wiederekennbares Muster ergeben. Die Messung kann bei schwankender oder nicht erkennbarer Stimmlage nur bedingt durchgeführt werden. Heisere, piepsige und tonlose (geflüsterte) Stimmen werden in der Regel kaum erkannt. Die Lautstärke spielt bei der Erkennung eine untergeordnete Rolle solange diese nicht ständig schwankt. Beim Training sollte man darauf achten, dass ganz normal gesprochen wird. Ohne künstliche Pausen oder besondere Intonation. Eben ganz normal. Das Windows VRS ist mit Hilfe eines freien SDKs programmierbar. Allerdings ist diese Möglichkeit nur mit Programmierkenntnissen ausschöpfbar. Das Zuordnen von Stimmbefehlen ist für den normalen Anwender auf Windows-Steuerbefehle begrenzt.

The sound output from DCS and that of TS3 is completely different. Aries Radio uses TS3 for the sound output. This can only be influenced with the sound properties in the TS3 options dialog or with the volume sliders in the Aries Radio panel.The sound output of TS3 can be fed into any device independent of DCS. So it is possible to hear the Aries Radio communication in the head phones and the DCS radio calls, DCS cockpit noise and engine sound may come from external speakers. It is even possible to feed TS3 output and DCS output in one and the same device. To hear the DCS radio calls you have to adjust the volume control of the widows output device, the volume control in the DCS options menu and last not least the volume control of the cockpit boxes . The latter may suppress all receptions if the box volume was below a certain level. This can happen because of an Aries bug on mission start. You need to move the volume slider of the Aries Radio panel once to raise the output volume.

The crash at the begin is a startup timing bug, which effects only some computers. It was never observed in our development environment but was reported by beta testers. The bug is fixed meanwhile for the next release. You can activate/deactivate the Export.lua entry out of the TeamSpeak menu: Plugins/Aries Radio/Export.lua entry on/off If you want to do it manually, you should use two minus chars (--) to comment the entry out.

What I can read between the lines, you get this message at the end of a mission after a DCS crash? I would recommend to wait on the next release which should be expected on Friday, Jan 30th. A lot of startup and mission end issues are solved there in.

Schau doch mal an den Lautstärkereglern der einzelnen Radios nach. Wir hatten den Effekt,dass bei runtergeregelter Lautstärke an der Cockpit Box (nicht in Windows) DCS keinen Empfang mehr durchlässt. Es werden dabei auch die Schrifteinblendungen unterdrückt. Die einfachen Dinge hast Du ja wahrscheinlich schon geprüft, Radio eingeschaltet, richtiger Modus, richtige Frequenz...

@Shamandgg I just had a look to the channel distribution. In theory it could be possible, that the 5.1 setting could have a strange channel configuration. On the other hand, we have users with 5.7 setting, without any problem. I will try to setup 5.1 in my environment. Then I will see.

Dear Aries user, tonight we delivered the version 1.973 to some selected beta testers. What we saw in or internal test and even tonight with the beta testers, the most annoying bugs are repaired.We will observe this version for another week before we publish it to the normal users. The following bugs were repaired: The rotary selector of the A10C intercom panel is repaired. An internal mutex bug is repaired. It caused repeatedly entries in the log file. The reason for the TeamSpeak kick off was found in a wrong message string for the protocol file. Protocols are deactivated by default from this version on. In case of trouble, if a protocol output is needed, it can be activated with the configurator program. The information window in the TeamSpeak accepts 128 chars for the client information only. To avoid crashes, the assembled string is cut so to have a maximum length of 128. This situation comes up only, if a GossipBox user activates more than 6 frequencies at a time. The Eavesdropper was repaired. It caused a crash sometimes at mission end. Thank you for your patience.

We are aware of the reported problems and most of them is solved meanwhile. The repaired version will be published as soon as the coming stress test is passed. Sorry...

Dear Aries users, we found a bug in the handling of the A10 intercom panel. The current version crashes if the rotary switch is set to INT. We solved the bug already internally, but cannot publish a bug release for the moment. To avoid the crash, please do not set the rotary switch to INT with Aries Radio active. Sorry…

@Case The need for msvcr100.dll comes up only if you do not update to the latest .NET framework. You can even install the Microsoft Visual C++ 2010 or 2012 (x64) redistributables (free download from Microsoft) to solve the problem. For the TeamSpeak problem check the following: · Check for the latest TeamSpeak Client version3.0.14 or newer. Versions below have another internal API. They would reject the Aries DLL. · Make sure, that no other radio plugin is active in TeamSpeak · The AriesRadio.DLL must be activated. See: Menu Settings/plugins (check mark for Aries Radio set) · TeamSpeak must be the 64 Bit version. · TeamSpeak must always be started with administrator rights (the same applies for the installer) If it does not work, contact me on support@ariescon.com. I will try to solve your problem.