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.

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

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

@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.

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.

The handling of the KY-58 is explained in DCS World\Mods\aircrafts\A-10C\Doc\DCS A-10C Flight Manual EN.pdf on page 145. It is not that complicated but confusing. If you try it out with some other players on frequency, you run into troubles with spoken explanations, because you are encrypted and not longer available to the others, if the configuration does not match. So it would be a good idea to use the Eavesdropper while acting as lecturer.

Dear Aries user, regarding paulrkiii's test of frequency interference and terrain masking, I can confirm, that there was a bug. Unfortunately, I commented the functions out for test purposes. We repaired the bugs immediately and have a new DLL as download available at: http://www.ariescon.com/AriesRadio.zip The ZIP file contains ariesRadio.dll. it must be copied to C:\Program Files\TeamSpeak 3 Client\plugins and replaces the old DLL in that folder. Terrain masking and frequency interference now works as expected. The KY-58 basically works, but has some logic errors while evaluating the power switch. The repair of the switch logic takes a little more time. So a bug release with a working KY-58 can be expected next week. I am sorry for these troubles...

@paulrkriii The frequency interference is audible only for a third listener. The two actors, who transmit at the same time have the receiver switched off (disconnected) as long as PTT is depressed. Nevertheless, we will test this, terrain masking and the KY58 again this night. I will keep you informed.

Very nice. I will include the Admin thing in the installation guide.

@Vespa: You find the the file in: C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\ AriesRadioLog_log.html BTW, I inspected your installer log. It seems to be all ok... Pleas check your e-mails. I sent you a special DLL for error inspection.

@Vespa The message ' Export.lua could not be located!' is generated at the moment, when the dialog function tries to locate the Export.lua with the help of the registry entry. The following errors could initiate the message: Export.lua path not found in the registry The attempt to open Export.lua as file (wrong path or file does not exist) File size is zero (empty file) No sufficient memory (very unlikely) The more important question is, does DCS find Export.lua, means, do you see the Aries Radio Panel coming up during a simulation session? If yes, then the TS3 plugin DLL seems to have a problem with access rights. In the latter case, only the function to enable and disable the Aries Radio Mod is impacted. All others should work normal. The Eavesdropper is available only, if you are connected to a TS server. The Radio Communication Quality dialog is available only during a running simulation session. If the folder still exists where you unzipped the installation package, you should find the file AirbornRadioInstaller_log.html please, send this file together with C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\ AriesRadioLog_log.html to support@ariescon.com.

Your poll is correct and should work. I even use it in Aries Radio. The only trap door is the validity of the model.There are phases, when your model is not available. This can be during mission start or a model change.I test the validity before each frame . UH1H_GetStorageLocation = function() storageValid = 0 MainPanel = GetDevice(0) or 0 if MainPanel ~= 0 then storageValid = storageValid + 1 end BoxOneRadio = GetDevice(20) or 0 if BoxOneRadio ~= 0 then storageValid = storageValid + 1 end BoxTwoRadio= GetDevice(22) or 0 if BoxTwoRadio ~= 0 then storageValid = storageValid + 1 end BoxThreeRadio = GetDevice(23) or 0 if BoxThreeRadio ~= 0 then storageValid = storageValid + 1 end Intercom = GetDevice(21) or 0 if Intercom ~= 0 then storageValid = storageValid + 1 end end storageValid must have the value 5 to indicate a valid Huey.

@ Vespa At the begin of the installation procedure, a dialog opens to specify the important folder paths for DCS World and Open Beta. If your SavedGames path is not standard, then you can change that in the dialog. You can check the path after the installation in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\AriesWings\DCSsavedGames and HKEY_LOCAL_MACHINE\SOFTWARE\AriesWings\DCSsavedGamesOB If the paths in the registry do not match the real paths, you may change the registry data to the real values. If you open the registry, please use the programC:\Windows\SysWOW64\regedit.exe. There are differences between the 32 Bit Registry and the 64 Bit Registry. Please let me know, if you could solve the problem. Edit: You should even check the plugin version number in TS3. It should be V1.940. You can find it in TS3 menu/Settings/Plugins.

Aries Radio 1.940 released Dear Aries User, Version 1.940 is available for download at: http://www.ariescon.com/AriesWingsRadio1.940.zip Start setup.exe from the installation package and follow the instructions in the dialog. Your configuration settings are saved automatically. The new version works with DCS version 1.2.10 and TeamSpeak version 3.0.16. Connecting Aries Radio 1.940 to Player with older versions should not be a problem. Nevertheless, the radio com quality information is not fully supported by older versions. After unzipping the installation package, please read the QuickInstallationGuide.pdf carefully. New features and solved bugs: · F-86F is fully integrated. When you change the channel in the radio box, you will hear a tone. The tone remains until the frequency is ready. The reason comes from a F-86F build-in delay while changing the channel. If you start talking too early, the entire transmission will be send on the old frequency. · Disconnecting the export.lua from the TS3 plugins menu now disconnects the open beta (if installed) in parallel. · The strength of the background noise can now be controlled online from the Quality dialog. · The Game Master is now indicated correctly in the Quality dialog. · The KA50 frequency filter bug is solved. All vehicles now use the same function for the radio initialization. · The KA50 frequencies and box select can now be controlled via keyboard. · The mission end test crash is solved. The crash came up on computers, where the cleanup of the keyboard handler took more than 20 ms. Known Bugs: If any frequency is incremented or decremented in the Aries Radio Panel, it can happen, that the result is the highest or lowest value of the given frequency band. The bug will be fixed with the next release. Manual Installation For those, who need to do a manual installation, download http://www.ariescon.com/AriesRadioManualInstallation1940.zip If you experience troubles with version 1.940, please report it to support@ariescon.com. Next: Integration of FW 190 D-9 (after a short period of vacation) At this point I have to say 'Thank You' to my fellow pilots of the 10th Gunfighters Wing, for standing endless, boring test sessions and guiding me back on track during the development.

@WoAyumi This message comes up in the very early phase of the installation. The path entry in the dialog is tested, whether the path really exists. It is no black magic. The string is taken from the edit field and then it tries to check the existence of directory with it. The defaults you see, when the dialog opens, is taken from the registry. The user can do a visual check to ensure , that the path is correct. If not, he can enter a path manually or with the help of a search button to the right. The only explanations for the bug you experience area simple typo in the path string or you left the default path untouched but TeamSpeak resides at another location.

http://forums.eagle.ru/showthread.php?t=127847 It seems, that you receive another beacon on the same frequency.

Dear Aries user, this night, we made the prerelease test for the airborne radio. The good news are, that all the functions work like expected and the F-86F is fully integrated. A lot of other bugs are solved and the software is stable enough to be released. Nevertheless, I have to assemble the installer package which will take another 3 days. As soon as the package is available, I will post it here. Thank you for your patience

It seems to be a DCS bug. The same effect is experienced with the Huey. But there is another annoying Bug: The beacon range is not checked and even the terrain profile has no influence on the range. DCS simply runs through a list of beacons and selects the first with the a matching frequency. But there may be other beacons closed by with the same frequency. DCS brakes off the search if the first beacon is found. As an example: You are parked on ramp 1 at Sochi. Type can be Huey or F86F. Dial in 920.0 kHz. You receive Primorsko NDB which is 172 NM NNE of Sochi. In reality, this NDB would be far out of range. The closed by NDB of Picunda, 920.0 kHz, 24 NM SW of Sochi, is never heard. This makes a serious instrument navigation impossible. I hope, DCS hears me weeping and fixes this bug next time.

Dear Aries Radio users, the radio test today could not be finalized successfully. I found a serious bug between my earphones. Therefore I have to shift the bug fix release to Aug 5th, because the next final test session will be on Aug 4th with the team. Nevertheless, I have prepared a preliminary description, how Aries Radio handles the ARC-27 of the F86F. The document is attached and will be integrated in the documentation with the next release. sorry... F86Channels.pdf

There are two possibilities: if the TS3 plugin is still active, from the menu line in TS3 open Plugins\Aries Radio\Export.lua entry on/off. You will see a dialog, which offers to connect or disconnect Aries Radio. If disconnect is selected, the export.lua entry 'dofile("./AriesWings/AriesRadio.luac")' is commented out. This works like uninstalling Aries Radio. The second possibility is to do the procedure manually. Go to C:\Users\[your username]\Saved Games\DCS\Scripts and open the file export.lua with a text editor. At the end of the file you find an entry dofile("./AriesWings/AriesRadio.luac"). Simlpy put two minus signs in front so that it looks like --dofile("./AriesWings/AriesRadio.luac"). If you want Aries being permanently disabled, you may delete the entire line with the dofile entry. Keep in mind, if you use the open beta version, the path would be C:\Users\[your username]\Saved Games\DCS.openbeta\Scripts . Both actions disable Aries Radio completely. If you experience the crash after it, you have another problem.

We just made some first tests with the F86. It caused some troubles with radio boxes an box selection. I will publish a Bug Fix Release on next week with the F86 fully integrated...

@Random It seems, that your configuration is not correct. To find the reason, please send the following file to: support@ariescon.com. DCS World\AriesWings\AriesAirborneRadio.ini I will have a look to it. In addition, please state the type of devices (joystick, throttle...) you use for DCS and have attached to your computer.

I can confirm what Schleudi said. In addition, could it be that you started DCSABRDO.EXE instead of Setup.exe? In any case, if the problem remains, please send the log file from the installer to setup@ariescon.com

What I forgot to mention: In the TeamSpeak 'Plugins' menu, there is an item 'Aries Radio/Export.lua entry on/off'. This can be used to disconnect Aries Radio from DCS completely. It deletes (comments out) the 'dofile' entry in export.lua. Once disconnected, DCS acts like Aries Radio not installed.

This error is most likely caused by the 'dofile' entries sequence in export.lua. Make sure, that the line dofile("./AriesWings/AriesRadio.luac") is the first before the TacView entries. It should then look like this: dofile("./AriesWings/AriesRadio.luac") local Tacviewlfs=require('lfs'); dofile(Tacviewlfs.writedir()..'Scripts/TacviewExportDCS.lua') If the problem could not be solved with this modification, please send me a note.