towsim

The Open Beta as only installation was not intended and tested. However, If you set the checkmark for Open Beta and the normal DCS World is not present, you will experience a couple of message boxes: A path for DCS World must be specified! DCS World path does not exist! This should not kick you out of the installation so far. If you acknowledge the message boxes, the installation will continue for the Open Beta Installation. As I mentioned, it was never tested. If this does not work, please contact me on support@ariescon.com . I will prepare a Setup.exe for this special case.

Preliminary DCS V2.0 support Dear Aries Radio users, we are working on the next release of Aries Radio. Because of DCS V2.0 another challenge came up which requires a new terrain file. The new build takes a little time. Therefore here a method to use the current Aries Radio with DCS Version 2.0. The following changes have to be made: copy the entire folder C:\Program Files\Eagle Dynamics\DCS World\AriesWings to C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha If you do have already an Export.lua file in C:\Users\mike\Saved Games\DCS.openalpha\Scripts, take care, that the entry dofile("./AriesWings/AriesRadio.luac") is present in the last line of the file. If the folder C:\Users\mike\Saved Games\DCS.openalpha\Scripts does not exist, please create the folder and copy Export.lua from C:\Users\mike\Saved Games\DCS\Scripts to the newly created folder. The terrain masking is disabled internally because the westerly coordinates are outside of the Black Sea terrain file. This is noticed by the terrain checker and it returns always best reception. Nevertheless, distance and horizon are checked as usual. For those, who use the Gossip Box, it is important to define a westerly coordinate for the radio location. Open the Gossip Box Configurator and enter the required coordinate in the ‘Unit Location’ Group. Example for CreechAFB: Latitude 36 34.8666 Longitude -115 40.6833 Altitude 3140 You should notice, that westerly longitudes are entered as negative values. Known Bug: If you start a second mission in a DCS session, it is most likely, that DCS crashes. This bug is under investigation. Thank you for your patience

The crash at mission end is a continuous problem and in our focus. Whereby, we did not observes it for a long time in our internal versions. We meanwhile working on version 1.980. Nevertheless, after the light speed fast download of the Nevada Map, I start the adjustment to DCS version 2.0 today and will have look to the mission end issue again.

Thanks for the info. I am just doing the download. Tomorrow morning I can ticker the terrain.

Yes, it works with the latest TS version if Aries Radio version > 1.6.

What beta are you looking for?

Yes, I can confirm the procedure Esac_mirmidon used. BTW, I cannot provide support for the next three days because of a short vacation with bacon, cheese and wine…

I am just working on it. The release depends on how fast I can pass through the DCS variables jungle. The first test version was planned for Monday. But today I found out, that the L-39C software does not support some important functions. So I am working in circumnavigations.

That’s not the only issue. You can download the L-39C only if you own a valid key. The key must be bound to your name and can be obtained in two ways: If you buy the L-39C then the corresponding key is bound to your name automatically. The download is started the next time you open the module manager. Or another person bought a L-39C for you and binds the key to your name. The latter procedure can be done if the owner logs in into his account. To go to the required page page is a bit tricky . On the profile page there is an edit field for License check. Put in the serial number. DCS shows then the entire data for the given model and a button to unbind the model and bind it again afterwards to a different account.

@Jeepyb This probably depends on the version you installed. I had a short look to the file package and the repaired configurator is part of the current package. It may be, that the package was not released officially. But the configurator V 1.977 was published as single repair and is available at: http://www.ariescon.com/GossipBoxConfigurator.zip @shagrat You are right, it is a pain to edit any file in the program folder. On the other hand, the INI files are not meant to be modified manually. It is a nightmare if you do configuration support with unknown contents of the INI files. The plans for V2.0 contain a migration of the entire Aries folder from DCS World to Saved Games. So DCS World will be left untouched for the future.Even the Audio Test possibility was already discussed with Snoopy and promised for V 2.0. But only small steps are possible for the moment. I am working on four projects for the moment which keeps me more than busy.

I am afraid, this issue is up to the developers. This effect comes up, if a texture was stored without mip mapping. Mip mapping takes care, that a texture is duplicated with differnt resolutions. The low resolution textures are taken if an object is in a far distance. If only the original texture is available then this flickering is seen. The flickering disappears if the observer is close to the object.

I already use TeamSpeak 3.0.18.1 without any problem. Even the older versions, including Aries 1.976 are working without problems. The migration to HKEY_LOCAL_USER will come with version 2.0 and is already under development. Thanks for the tip

I can confirm, that it is still in development but not perfect. The installation and login procedure seems to be too complicated. As soon as we get a positive feedback from the beta testers we will publish a first version. If you like, you can get a first impression with: http://www.ariescon.com/GCA_V30.wmv (for Windows10 users: media player needed)

If the function out of the plugins menu does not work, you probably have a corrupt installation. You can solve the problem manually: Open the registry and go to: HKEY_LOCAL_MACHINE\SOFTWARE\AriesWings If you do not find AriesWings at the given location use: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings You will see two keys: DCSWorldPathOB and DCSsavedGamesOB DCSWorldPathOB should have a full path to your Open Beta installation it looks normally like this: C:\Program Files\Eagle Dynamics\DCS World OpenBeta If the entry is empty or points not to your Open Beta installation then enter the correct path here. DCSsavedGamesOB should have a full path to your Open Beta saved games location it looks normally like this: C:\Users\[your username]\Saved Games\DCS.openbeta If the entry is empty or points not to your Open Beta saved games then enter the correct path here. Let me know if you could solve your problem…

It does not work in either way. The download of the L-39 is deactivated for whatever reason. I made a crosscheck with other models without any problem. In addition, there is no possibility to input a serial number (license key) in the module manager. I have got two models as a gift from fellow pilots to support Aries Radio development. There is no way to activate them. Is that intended by DCS?

@Gambo The normal way to deactivate Aries is to use the TeamSpeak menu Plugins/Aries Radio/Export.lua entry on/off It deactivates the ‘dofile’ entry in export.lua. After that, no Aries Software is started in DCS anymore and the frequency panel does not come up. It normally works for the Open Beta Installation too. But this depends on the version of Aries. If you simply copied the Aries files to DCS version 1.5.0 as instructed in post #1095 then you need to modify export.lua manually. Because some registry entries are missing to find the Open Beta.

DCS Open Beta Dear Aries users, after a couple of tests with OpenBeta version 1.5.0 and Aries Radio I can report, that the current version of Aries Radio is compatible to DCS OpenBeta version 1.5.0. For those who installed the Open Beta for the first time and want to use Aries Radio, simply copy the entire folder: C:\Program Files\Eagle Dynamics\DCS World\AriesWings To C:\Program Files\Eagle Dynamics\DCS World OpenBeta Furthermore copy: C:\Users\[your username]\Saved Games\DCS\Scripts To C:\Users\[your username]\Saved Games\DCS.openbeta I do not want to conceal, that I experienced some crashes with the Open Beta version. But every time after a restart it worked successfully. It is hard to say for the moment, what the reason is, DCS or Aries Radio. Because I experienced even a lot of crashes with Aries deactivated. There is another small problem with the radio panel. Once you click a frequency in the Aries Panel, the keyboard focus stays with Aries Radio. DCS does not accept any joystick or keyboard input unless the DCS window was explicitly clicked again. This bug is already solved in our internal development version. Nevertheless, have fun with OpenBeta version 1.5.0….

Nevertheless, awesome…

I am thinking on it for a while. If it shall work like in the real world, it becomes complicated. ATIS or even a music radio station would be a TeamSpeak transmitter. A single user (transmitter) may speak on more than one frequency at a time. But this is not possible for two different transmitter. The only solution would be to move an ATIS program on a separate computer then it would work. Since you have not only one aerodrome, you would need one computer per aerodrome. I made a suggestion to the TeamSpeak developer to extend their API to earmark transmitted voice packages. This would solve 90% of all these problems for a radio solution. They don’t even answered on my mail. So we have to live with black magic and TeamSpeak as it is.

I just tested the latest TeamSpeak version 3.0.18 together with Aries Radio. It all works normal. Upgrading to TeamSpeak version 3.0.18 is no problem.

Did not know about the new version. I will test it immediately and publish the result. thanks...

You can test it out easily. Place a MIG21 aligned on the runway 24 of Sochi. The heading you read on the compass gauge is about 242°. If you consult the approach charts of Sochi, you will find the mag runway heading as 236°. Now change to the F10 map view and measure the runway heading with the ruler. The result is the same as seen on the compass gauge. Since the ruler is grid heading orientated, the MIG21 is assumed to use grid north.

Headings measured on the F10 map view are always grid headings. Means, it references grid north which is bound to the projection method used in DCS. It cannot be used for navigational purposes. The black grid represents the geo grid and points upwards to true north. You need to find out what reference is used for a specific aircraft. A10C uses mag north while the MIG21 uses grid north. I did not check out the Mig15 but it seems, that it uses mag north as compass indication while the F10 map heading uses grid north.

The most complicated procedure is to coordinate all the different threads and processes running at the same time. Especially at the end of a session it can happen, that DCS, TeamSpeak or an Aries thread ends, while another process uses it. This depends mostly on the specific computer and its configuration. Once you have caught such an unreliable piece of code then you experience the next surprise with a new version of DCS or TeamSpeak. It never ends… The main change we had with 1.977 was the reactivation of the protocol system. But even here we found already some trap doors which are solved in our internal version 1.978. The main change in 1.978 is the integration of the C101 with its radio equipment and its IFF/SIF. Furthermore, the terrain profile database was changed to a DCS conform terrain profile.

The current development level is not that stable as expected. Our plan was to create a centralized configuration management to simplify a session startup. Unfortunately, the internet causes troubles if more than 5 clients are involved in the startup process. Beside that, we have two members in our community, who have troubles with Aries Radio. One cannot start TeamSpeak with Aries active and the other has troubles with Aries on Windows 10. As long as these bugs are not handled, I cannot deliver any piece of software. Since the radar applications are tightly bound to Aries Radio, they are effected by these bugs too. Therefore I beg your patience for further developments. Sorry…