towsim

@Reaper_Mav No sweat, you are welcome. The only way to find the reason is to inspect the log files. Look for the following files and send it to support@ariescon.com: In the folder, where you unzipped the downloaded package, there should be file named AirbornRadioInstaller_log.htm. C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio \ AriesRadioLog_log.html DCS World\AriesWings\logs\ AriesAirborneRadio_log.html If present, C:\Users\[your username]\Saved Games\DCS\Logs\DCS-xxxxxxxxxx.crash C:\Users\[your username]\Saved Games\DCS\Logs\dcs.log Make sure, that the files are produced by a crash session.

To underline the difference between engine idle and engine off, all fighter jets, practicing SFO (simulated flame out), use the speed brakes to simulate the drag of a cold engine. All aircraft have a 'best glide speed' measured under standard conditions (weight, external loads). All speeds higher and lower cause increasing drag. Higher speeds cause the exponential increase of body drag because of increasing speed. Lower speeds cause increasing drag because of increasing AOA.

Give me a day. I will check the things out.

I will test these situations and post the answer here. The coordinate of the Gossip Box Transmitter is evaluated. There are two facts which could be the reason. One is, that the GossipBox is an older version than the actual Airborne Radio. I do not know for the moment if that impacts the communication. The other is the terrain. If you have some mountains between transmitter and receiver, the field strength of the signal is reduced. Over flat terrain or open water you should have a good quality up to 100 NM distance at 2600 ft MSL. Below 2600 ft, at 100 NM, you are beyond the horizon. You should even take care, that the altitude of the GossipBox is well above the field elevation. Otherwise your transmitter/receiver is under the ground which causes even a reduced field strength. For the com issue at mission start, I would need a little more information if it is possible. As I said, I will test that.

@shagrat Have a look to the 'Impressum' page: http://ariescon.com/index6.html

As promised, the new version 1.955 is available on the Aries Wings download page. The only change in this version is the repaired AriesAirborneRadio.dll. Users who have already installed the repaired DLL (see post #522 of this thread) need not to install version 1.955. Version 1.955 is available on the download page: http://ariescon.com/index10.html

As stated some posts before, the reason could be, that you have to start TeamSpeak with administrator rights. However, if you want to define the path manually, you have to modify an registry entry. The attached picture shows the location. The path shown under DCSsavedGames represents the path where Aries starts to search for export.lua. Be sure, that you use the 64 bit registry. If you use the 32 bit registry you will find the Aries section under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings

BTW It is not sufficient to login as administrator. Right click the SetUp.exe icon and select 'Run as Administrator'.

@Vespa, The current package does not contain the new DLL. I will wait until Monday, if there are more complains which need immediate repair. The package with the newDLL will be assembled on Monday.

My FTP tool tells me 78 655 368 bytes. My file manager tells me 76 812 000 bytes. So different file manager have different methods to measure a file length. The important thing should be, that the file is named AriesWingsRadio1.954.zipand the file date is 26-Oct-14. The fact, that you do not see any installed files, points to the internal Microsoft installer. The reason could be access rights to the programs folder or to the registry. Therefore, Setup.exe should always be started with administrator rights. If you cannot run the installation successfully, I would recommend to download the manual installation package.It needs a bit file copying and a registry modification. The description how to execute the manual installation is part of the Quick Installation Guide.

@Shane45 OK, it seems we are a little closer to reason. First check, if AriesRadio.dll can be found at C:\Program Files\TeamSpeak 3 Client\plugins. If it is not there, then your installation was already wrong. If it is there: Does TeamSpeak have a 'Plugins' entry in the menu line and, if yes, can you open the Aries Radio pulldown? If the menu is not there, open the 'Settings ' menu and select 'Plugins'. Aries Radio should have an entry in the left list window and should have a check mark. If AriesRadio.dll appear as red entry, then it is most likely, that you must start TeamSpeak with Administrator rights. Late entry: Just inspected your last post a little more precise. It seems, that the installation failed already. If the AriesRadio subfolder is not there then you have an installation problem. It would be important to send your installation protocol 'AirbornRadioInstaller_log.htm'. It resides in the folder, where you started 'SetUp.exe'.

@Shane45 We would need a little more description. Some questions: Did you experience the trouble already during the installation ? Did Aries start (you would see the Aries radio panel) together with the mission ? Does DCS crash or is the Aries radio panel simply not visible? Did you configure Aries to support your input devices? If you don't see the Aries radio panel, can you use PTT to illuminate the blue LED in TS3 ? If you can start DCS, look for the following files and send it to support@ariescon.com: In the folder, where you unzipped the downloaded package. there should be file named AirbornRadioInstaller_log.htm. C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio \ AriesRadioLog_log.html DCS World\AriesWings\logs\ AriesAirborneRadio_log.html

ATIS or simply a radio station transmitter is alrady in the queue. It will be available together with the first radar application.

@vespa Stuka is right. The label in the dialog is misleading. Remove the 'plugins' from the path string, then it should work. I will correct the label in the dialog. Sorry...

@nicutapa It is hard to say what the reason could be. The first test should be if DCS crashes even with Aries deactivated. You can test it if you select the TeamSpeak menu Plugins/Aries Radio/Expot.lua Entry on/off. Unpush the 'Connect' button. If the error comes up again during a session, then the error is not caused by Aries.Vice versa, if the error comes up only with Aries connected, please send the following files from the crash session to support@ariescon.com: DCS World \AriesWings\logs\AriesAirborneRadio_log.html C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\AriesRadioLog_log.html C:\Users\[your user name]\Saved Games\DCS\Logs\DCS-nnnnn.crash C:\Users\[your user name]\Saved Games\DCS\Logs\ dcs.log

version >= 3.0.14. TS changed the API with this version. Earlier versions will not work.

That looks impressive. I like this assembly.

@nicutapa Make a simple check if Aries Radio works. You can do that while observing TeamSpeak. If you press PTT for a radio box, a blue LED in the TeamSpeak window tree should light up. If that is observed, than it is likely, that the position of the additional radio window is outside the visible screen.We had situations where the lower left corner of the entire window desktop is in the minus area .Check the file DCS World\AriesWings\AriesAirborneRadio.ini. Open it with a simple text editor like Notepad++. There in you find a section [window]. The first line in this section named 'WindowRect' contains the desktop coordinates of the upper left corner of the Aries Wings Radio Panel. The first two numbers define the desktop coordinate where the window shall appear and the next two define the dimension of the window. Check the numbers and try to modify the desktop coordinate so as to be sure that it is a position in the visible desktop area. If that does not work, contact me again under support@ariescon.com.

@Vespa Simply unzip the downloaded file and copy the extracted AriesAirborneRadio.dll over the old one in DCS World\AriesWings or DCS World OpenBeta\AriesWings.

On the report of AMVI_Jay we have reworked AriesAirborneRadio.dll. The attachment contains a repaired AriesAirborneRadio.dll as ZIP file. The content must be extracted from the ZIP file and be copied to DCS World\AriesWings or to the corresponding open beta folder. The bug (1.) , reported by AMVI_Jay in post #470 is solved with that so far. Leaving a paused game does not crash the simulator anymore. The second bug could not be located in Aries Radio. But I know, that there is a DCS issue with VHF AM Box1 frequency setting. The frequency values set can be controlled in theAriesAirborneRadio_log.html file. Every time a frequency is set in Aries Panel Box1, a red entry in the log file is written. Example: 22 [00:02:59.195] VHF 1 frequency set into Box 1 125025000.000000 Hz :: internal 125026440.000000 Hz The first value in Hz is that written to the box and the second is the result what the box contains afterwards. In the example above, there is a deviation of 1440 Hz, which is acceptable. A deviation below the set frequency of 125025000 Hz or a deviation of >= 25000 Hz would be a real error. The new DLL: http://ariescon.com/AriesAirborneRadio.zip

The block out noise is generated internally. I will change it to a so called half side filter. This should come closer to the reality. The radio issue will be checked. I keep you informed.

No sweat, you are welcome.

I got the feedbacks from our wing community and we have the following results: The game master function will be retained. As soon as the button is pressed, no inputs from clients are accepted. With this function the situation can be controlled, if all participants shall work with the same configuration. If the game master is not occupied, everybody can set his own configuration which will be even stored locally. However, only the receiver configuration will be noticeable by nature. The transmitter functions are set, but will be noticeable only by the external participants. The sliders for the band path filters will be enhanced so as to have values between 1000 Hz and 48000 Hz, to be set smoothly without steps. The geometrical range of the sliders will be extended for more precise setting The small edit fields to the left will accept inputs, if the slider positioning is not precise enough. The button for standard values will be replaced by 5 profile buttons. The content will be free editable and individually named. The button row with the switchable options will be reorganized. One set will be marked as transmitter options, another as receiver options. This shall be for better understanding which options impact the local sound and which not. An additional test button will play a WAV sound file which will be modified with the current configuration. So it is possible to test locally the current transmitter and receiver options. There will be a INI file entry for each supported aircraft with a definition, how strong the mask modification will be audible. I hope, with the more precise set options, everybody can set his own voice communication configuration and I am out of the discussion.

I have just assembled my report. I give our wing members this day for additional suggestions. The report will then be published tomorrow in this thread.

That is correct.