towsim

@Dojo I am happy, that you brought the things to run.The problem I have to fight with is, that 5 applications are involved and an unknown environment on the target computer. Each can cause an error. Therefore the method you used ensures a clean setup in any case. But I think the normal user should use it as plan Z, if nothing else helps. In most of the cases it helps, if the user follows the installation guide carefully. But even here, it cannot be predicted what complicated environment resides on a target computer to ensure an automated installation. Nevertheless, thank you for your post.

@Boris, it is hard to determine the reason from a distance. Please send the log files from your crash session to support@ariescon.com You find the required files at: C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\AriesRadioLog_log.html and \DCS World\AriesWings\logs\AriesAirborneRadio_log.html I will answer as soon as possible.

There is no video available up to now. I think, it is not that tingling to produce a video, only to see a green and a yellow LED blinking. But we just prepare a video for the RADAR applications. It will show a complete radar approach in IMC with a final talk down controlled by real air traffic controllers. It even demonstrates the use of the airborne radio. As soon as it is available, I will post it here.

@Dojo It would be really important to send the log files from a crash session to my support account. Otherwise it is impossible to detect the reason for the bug. Please have a look again to the following folders: C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\AriesRadioLog_log.html and \DCS World\AriesWings\logs\AriesAirborneRadio_log.html Please send the files to support@ariescon.com.

@Dojo, after evaluating the different causes for the bug you experienced, I came to the following conclusion: The PTT release causes an ACCESS VIOLATION on the opposite side. This points to a protocol message, which stores the current values to calculate the receiver quality. This message is only for information and can be deleted, what I did for your repaired version. More interesting is the reason why the message causes the violation. The only critical thing is the TeamSpeak client name of the receiving client. It is the first argument in the message. All others are floats or integers, which cannot cause any error. As a result, I deleted the message completely. The protocol file, I mentioned in the last post, must be in the described folder. Otherwise, the entire radio system would not work. The repaired DLL can be loaded down from : http://ariescon.com/AriesRadio.zip Copy the extracted DLL to C:\Program Files\TeamSpeak 3 Client\plugins to replace the existing DLL of the same name. Please give me a shot note whether the new DLL omits the bug.

@Ramstein it is completely up to you. The currency is Euros. PayPal takes care, that it is converted to US Dollars internally. The amount may be 0.01 Euro up to 10,000,000 Euros (field length):D.There is a check mark, which has to be set explicitly, if you want to donate the amount monthly in a loop.If it is not set, it is a one- time donation.

@dojo I will prepare it for tomorrow...

@Dojo it seems, that a protocol message causes an access violation. You can confirm this by inspecting the log file C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\AriesRadioLog_log.html. You will find and entry like this: 0 (00:07:13.289) Program Execution Error in APPL_REPORT : Protocoll 000000006e71346e EXCEPTION_ACCESS_VIOLATION If this is the case, I can send you a repaired version where this protocol entry is suppressed.

@Snoopy found an uninitialized flag in the TeamSpeak DLL which suppresses the "beep" randomly. It will be repaired with the next release. Thanks for the report...

I made a short investigation regarding 'Aries Gossip Box was not installed correctly'. This message box is generated if the installation path in the registry cannot be determined.It is not a wrong path definition, it is simply not there or cannot be found at its standard location in the registry. Here the key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings\GBO\InstallationPath the standard entry there is:C:\Program Files\AriesWings\GossipBox If you inspect the registry, you should know, that there are two different registry editiors. One is used for the 32 Bit registry and can be found atC:\Windows\System32\regedt32.exe. The second,the registry you should use, is the 64 bit registry editor located at C:\Windows\SysWOW64\regedit.exe. The start with administrator rights is mandatory for all Aries applications.The access to the registry and to the Program Files folder are in dependence of the administrator rights. That is the Windows security paranoia. Regarding the TGP for single monitor installations. To get a snap shot from an MFD, a fixed location of the MFD is mandatory.With the cockpit view only, the MFDs move with every change of the viewpoint.Unfortunately, the published LUA functions for SharedTexture do not work for whatever reasons. Therefore I have to use a screen copy function for the desktop. This implies a fixed desktop area definition, which can only be done with an exported MFD on a second monitor.

Give me a short time for the Christmas tree. I will take care of it tomorrow...

@vespa and R34P3R I prepared a manual installation package for the Gossip Box. With the help of the attached documentation, you can compare the different directory and registry entries whether they match. If not, you can download the entire manual installation package from: http://ariescon.com/GBOmanualInstallation.zip Gossip Box Manual Installation.pdf

@R34P3R Up to now, the installer needed not to access the Program Files folder. Version 1.70 adds the Gossip Box and some additional Folders to C:\Program Files\AriesWings. The access rights depend on ,your user account control settings. I would recommend to set the user account control settings to the lowest level and try the installation again. You find the user account control settings in the control panel / action center. There, select 'change User Account Control settings' . Move the slider down, towards 'never notify'. If this procedure does not work, please contact me on support@ariescon.com again. I will then assemble a small manual installation package for the Gossip Box.

Version 1.970 beta This new version is a internally reworked Aries Radio,based on user bug reports.The internal changes imply, that all users in a session have to have this new version installed. With other words, version 1.970 cannotconnect to users with older versions installed. We decided to release a beta version because we have still an uncertain condition if more than 16 users are in a session at a time. It was not possible to get always that number of people together for a test session. If you experience troubles in a session with more than 16 participants, please report it to support@aries con.com. Since we spent a lot of time for urgent bug repairs, it was not possible to finalize the support of Bf-109K-4 and the MI8 right in time. It will be supported with the next release. The Gossip Box was delivered as separate package in former times. Since the gossip Box uses the same environment with TeamSpeak as the Airborne Radio does,it was likely, that troubles come up with different DLL versions.Now we deliver the Gossip Box together with the Airborne Radio. This ensures a consistent version management. The installation of the Gossip Box is not a must. It can be selected in the installer program. The new year will bring us the first radar applications. To simplify the beta test phase, the configuration data and the BlackSea map data are installed precautionary.This is even done in regard to the coming Nevada Map and WW2 environment. You find these additional data in C:\Program Files\AriesWings\RadarEnvironment\BlackSea Download The new version 1.970 can be downloaded from the Ares Wings download page: http://ariescon.com/index10.html New features in 1.970 Version 1.970contains the following new features: The rotary selector of the A10C intercom panel determines, which radio box will be used for transmission if the MICforward button is pushed. The device installation during mission startup is repaired.The PTT buttons now work without any error. The information window in the TeamSpeak client was reworked.The client configuration is now visible even if the localclient is Off Game. The internal internet messaging was reworked. Therefore thisversion (1.970) does not communicate with older versions anymore. All members of a session have to have version 1.970 installed. The client management was reworked to differentiate between the client ID, client computer and game server.This repairs some effects while calculating the voice degradation based on distance and terrain. The folder structure was changed to prepare the coming radarapplications. The shadow map file is moved to C:\Program Files\AriesWings\RadarEnvironment\BlackSea and renamed to BlackSeaShaddow.map Known Bugs The internal target and client management was reworked. In the older versions we experienced some memory bugs if more than 16 clients were connected at a time. This bug should be repaired. However, we could not test the situation with more than 16 clients extensively . Conclusion We are at the end of the year 2014. It was a year with a lot ups and downs and endless work on the radio applications.Thanks of the support of my fellow pilots from the 10th Gunfighters and other virtual wings as testers, most of the announcements could be realized right in time.Therefore I say 'Thank you' to all Aries users because of their patience and support. A peaceful and contemplative holiday season and a happy new year to all DCS enthusiasts from: Aries Wings Consulting Owner:-------------------------Friedhelm Michel CEO:-----------------------------Friedhelm Michel CTO:-----------------------------Friedhelm Michel Software development:----Friedhelm Michel Consultant:--------------------Friedhelm Michel Marketing:---------------------Friedhelm Michel Controlling:--------------------Friedhelm Michel Test Staff:----------------------10th Gunfighters Quality Management:-------10th Gunfighters Documentation:--------------Friedhelm Michel Accounts department:------Friedhelm Michel Cleaning Staff:----------------Friedhelm Michel Notorious grumbler:--------Schleudi

Dear Aries user, unfortunately wie found a small bug in our final test. The release has to be postponed to Dec. 23rd.(this year). I am sorry for the delay...

@shamandgg It's hard to say what the reason could be. Could you send the following log files from your latest session to support@ariescon.com: \DCS World\AriesWings\logs\AriesAirborneRadio_log.html C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio\AriesRadioLog_log.html. I will inspect the logs and keep you informed about the results. If you use a version > 1.955, it is necessary, that all participants use the same version. From version 1.956 on we changed the internet message format. BTW, we will release version 1.970 as beta tomorrow night. It includes an installer. The manual installation becomes more complicated because of a modified directory structure and additional entries in the registry. It will even include the Gossip Box. The manual installation guide will take another week to be completed.

The only values which may be modified manually are the TGP coordinates. All other values should be set with the configuration program. There are some traps caused by format and value range, which probably crashes the simulation. But it is interesting. You seem to be only user who uses the TGP snap shot...

Thank you Astiles, this is a good advice. I forgot to mention it. Meanwhile it becomes too much for a single brain with two cells.

@Ski1106 At the moment, the dialog opens (Export.lua on/off), it is tested whether Export.lua is available. It bases on an information from the registry.My advice would be to check the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings There should be an entry 'DCSsavedGames'.The standard path you find there could be: C:\Users\[user name]\Saved Games\DCS If you complete the path with '\Scripts\export.lua' you get the path: C:\Users\[user name]\Saved Games\DCS\Scripts\export.lua. Check, whether export.lua really resides at this location. If not then you have the reason. In the latter case, please contact me on support@ariescon.com. I will check your installation to find a solution.

@dojo On the first look (DCS-20141219-004740.crash) it seem to be an Open GL issue. It could be, that your new monitor has a different pixel resolution than the old one. This is a new situation for Open GL. I am not sure, whether all older Open GL driver support all the new pixel formats. DCS runs with DirectX while Aries Radio creates a Open GL graphics window. This would underline the situation, that DCS runs perfect without Aries Radio (without Open GL). The only advice for the moment would be to look for the latest graphics driver for your graphics adapter. A new driver usually could contain a better Open GL support. If another cause is the reason, I would recommend to wait to Dec. 22nd. We will publish a new version at this date, which has a lot of bugs repaired.

As Leto stated in a post before, we found a serious mismatch in the client management because of a misinterpretation of the internal DCS target IDs. This is solved meanwhile and we need a short beta phase to be sure about the results. Furthermore , we prepare the communication and data management for the radar applications. We planned initially to deliver the next version with the radar interface ready.This is postponed to January as version 1.970.Version 1.960 is planned forDec. 22. as long as no troubles come up. The version has the following bugs repaired: Stable radio client connection if more than 10 clients are up in a session. Joystick and other devices are safely recognized. Client information in the TeamSpeak window now shows the gamer information even for 'off game' clients.

@spokejocky The name of the snapshot file is used only to give a rough orientation and to avoid overwriting older air pictures. So the name, in principle, can be any what. But some considerations: The only available coordinate is always the coordinate of the plane. The coordinate of the location the TGP shows, is unfortunately not available. Unless anybody knows how to suck it from DCS. If you are 20 NM away from the object, the use of this coordinate makes no sense. If the object coordinates would be available, I could only use Lat/Long. The conversion to UTM would require a query from the DLL back to DCS. This becomes complicated under runtime conditions. Date and time is already in the name. But I have to admit it is in time_t format, the seconds since 1/1/70.This is not that readable for normal users. On the other hand, the file time can be read with every file browser. A change to the naming could be done, since it is not so much work and it is Christmas soon. But I would ask for a consistent conceptwhich is accepted commonly. In any case, I am open for suggestions.

At the moment, the signal 'Radio powered' or 'Radio off' is received from the simulator, the selected frequencies of the radios are published to all other TeamSpeak clients. If the situation comes up, that the radio experiences fluctuating power then a message is generated with every power change. The only solution I see is, that this type of message is controlled in a way, that only every 3 secondsa power on is accepted. The player would notice a power downimmediately. A power up would be effective after 3 second s only.This reduces the published messages to an acceptable amount. I will integrate this function for the next release. Thank you for the report

There are several combinations possible: TS with PTT + Aries with PTT Select PTT in TS. In the Aries configurator (ARD) select the buttons, you want to use as PTT and/or box select. The TS-PTT button is ignored by Aries. Aries uses only the buttons from its internal configuration. TS with VAC + Aries with VAC Activate VAC in TS and select 'Voice Activation' in the ARD. The defined PTT buttons are used then as box select only. TS with VAC + Aries with PTT Activate VAC in TS and deactivate'Voice Activation' in the ARD. Select the buttons, you want to use as PTT and/or box select. This configuration uses VAC in TS if you are off game and normal PTT and/or box select in Aries during a game. As far as I know, the TS PTT configuration is completely independent of the TS server. The entire logic is generated in the TS clients.

Tanker Contact Issue Dear Aries users, during one of our test sessions we could exactly determine the tanker contact issue and the contact to other DCS controlled stations. The reason is the volume control of the radio box involved. Since the volume slider of the Aries Radio Panel is connected to the volume control of the respective box, it can happen, that the volume is set to NULL on startup. In this case, even if you are on the right frequency and box, the tanker's answer is not audible and no text line appears with the answer. Nevertheless, the tanker got the request and switches on the lights. In addition, DCS evaluates the buttons on the intercom panel. If the volume of the box and/or the common volume control is close to zero, the same issue comes up. The latter case is not that dangerous because the intercom panel volume defaults to maximum on startup. If the tanker does not respond, check the sliders of the Aries Radio Panel and move them close to the most right position.