towsim

Geheimtip! Das private Museum von Josef Voggenreiter in Niederalteich. Dort steht die F-104 im Mittelpunkt, neben unzähligen anderen Exponaten. Ein Schmankerl ist ein Test Mock-up eines Deutschen Stealth Jets, der stark an die F-117 erinnert. Das Kaktus-Geschwader (Vereinigung ehemaliger F-104 Piloten) hält dort regelmäßig seine Treffen ab. Das Museum ist eine neu gebaute, moderne Halle. Es werden Gruppenführungen nach telefonischer Vereinbarung durchgeführt.

Going along a physical model is a huge challenge. In ATC tower simulations we made the experience, that a physical model has two disadvantages. The first is, that the number of variables, interacting each other, makes it almost impossible to predict a result. It requires a deep understanding in meteorological physics to create a specific weather situation at a given time. The second is, that in a serious simulation, a situation must be reproducible. The latter is difficult, if too much variables have to be considered. A standard situation in a military environment is a takeoff in pretty VMC, executing a mission, while ceiling and visibility decreases on return. The pilot has to recover in IMC and to change over to an IFR flight plan. We found a solution to create weather management files, which can be bound to any exercise (mission). It gives the possibility to use a specific mission in different weather situations. Even this has a disadvantage. Such a system can be configured with completely illogical parameters, like defining heavy snow precipitation with an air temperature of +35°C. Even here, a basic knowledge of meteorology is needed. The current version of static weather in DCS gives the possibility to define some parameters to create a situation. It would be a big advantage, if the parameter could change over the time and this in different geographical areas. The attached image shows a weather management editor which is used with a professional ATC tower simulator (TOWSIM). It lets the user change the variables by moving the points in the diagrams directly. The result can be stored in a weather management file and later bound to any mission. I do not expect ED to change their simulation model, but it can demonstrate a rough direction for further developments.

@AstroEma To find the reason for the crash, I would need the following log files from a crash session: C:\Users\[user]\Saved Games\[DCSversion]\Logs\dcs.log, If available, C:\Users\[user]\Saved Games\[DCSversion]\Logs\ DCS.openbeta-xxxxxxxx-yyyyyy.crash C:\Program Files\AriesWings\PRCL\ApplicationData\Aries_Session_Protocol.html. Please send the files to support@ariescon.com.

An estimate cannot be stated. We are still in the definition phase.

@f4l0 It is planned for version 2.0. There will be a completely revised configurator.

@Scooternutz , You configured your operating system obviously with some complicated path directives and drive definitions. The log file reports a drive H:\AriesWingsSystem which should normally be C:\Program Files\AriesWings. The same seems to be for the Saved Games folder. The installer consults some standard API functions to find the correct path to Saved Games. While Setup.exe (= Aries developed) works on the correct Saved Games path, does DCSW_ABRadio (Windows installer) not find the correct path. The only recommendation I can give is to revert your path and drive definitions at least for the installation of Aries Radio. Additionally, before you start a new installation, uninstall any Aries Radio from your system. You should even have a look to the registry: HKEY_CURRENT_USER\SOFTWARE\AriesWings Delete the entire “AriesWings” branch (not HKEY_CURRENT_USER\SOFTWARE). With a standard file system and a clean registry, the installation should work.

Yes, it depends on the volume. You will not get text answers if the volume at the boxes is too low...

@KansasCS This is a feature of DCS. If the volume of the radio boxes are too low, DCS suppresses the reception of radio transmissions. In this case, the reports from AI objects. Set the volume to a normal level. This should solve your problem.

@Scooternutz I assume, the installation could not be finalized? In this case, a little more information would be helpful. Please send the installation log file to support@ariescon.com. The XML file can be found in the folder, where setup.exe was started.

@Dutch Baron Thank you for the log file. Unfortunately, it shows the version 1.986 instead the latest version 1.987. Since the GameGUI.dll is involved in the protocol, which was not the case in version 1.986, I assume a version mix up in your Aries Radio installation. I would recommend to uninstall your current Aries Radio and do a clean install of the latest version 1.987. It is even wired, that you have a protocol file at all. Because you started a single player mission without TeamSpeak. TeamSpeak is responsible to start the protocol software. It seems, that you started the protocol application manually (very smart). Let me know whether it worked with a new installation.

The Aries log file would be for interest. You find it at C:\Program Files\AriesWings\PRCL\ApplicationData. Have a look to the time to find the right log file. Send the file to support@ariescon.com. On the first sight it seems to be an initialization issue if a second mission was started out of the same session. The Aries log file will hopefully show the moment when the crash occurred.

I assumed, that you use a mouse input. With this device even another reason should be checked. The device driver software allows normally to recognize the rising and the falling edge of a signal or only a pulse. In the first case you would receive two signals. The latter case produces only one signal. You are using a foil keypad. This points most likely to hardware bouncing.

The software evaluates one mouse click for one number change. Could it be, that your mouse hardware bounces on your left mouse button? To be sure, you should try another mouse device to test the button reaction. If the behavior remains, let me know.

Normally it will work. But we observed sometimes an erratic behavior of Aries Radio. It seems to be an initialization problem. With the “manual” setting you are on the save side…

@Fury_007 and Dutch_Baron: Beside that, what Schleudi recommended, if the bug remains, I would need the log files from a crash session: C:\Program Files\AriesWings\PRCL\ApplicationData\Aries_Session_Protocol.html Please send it to support@ariescon.com. Even the file AirborneRadioInstaller_log.html would be needed. You find it in the folder where setup.exe was started.

Not yet. I want to breath a bit.

Dear Aries users, the latest official version 1.978 is available for download at: http://www.ariescon.com/AriesWingsRadio1.987R.zip Before you install the new version, please read the included document Version1987_ReadMe.pdf carefully. It contains a description of all new functions and a guide, how to install the new version. The new version supports Nevada and Black Sea. If any trouble comes up, please send a short description to support@ariescon.com. Have fun…

@castor now

Beside Leap Motion, it would be a real advantage for all, if DCS would implement a new mouse mode. I think, everybody dislikes the situation if you aim with TrackIR to a specific cockpit switch and tries to catch the switch with the mouse symbol. As soon as the head is moved the mouse symbol leaves the switch position. In a stress situation it is sometimes a real fiddling. I would suggest a mode (Leap Mode) in which the mouse symbol is locked on a position in the cockpit, independent from the head movement, as long as the physical mouse device is not moved. This would give a chance to have your virtual finger locked on a switch while you observe anything else. The normal mouse move, I call it the relative mode, could be left as it is. In Leap Mode, the mouse would be moved to absolute positions in the cockpit. Leap Mode/Relative Mode could be bound to the right mouse key as a toggle switch. Locked mode could be displayed with a different color of the mouse symbol.

Dear Aries user, After an agonizing and long time of testing we could catch a bug, which prevented the release of the new Aries Version for DCS 2.xx up to now. At this point a special “thanks” from the 10th Gunfighters to Sierra99 and his sim fellow Guido, who were the beta tester for this bug. We are now assembling the release package and are reviewing the installer software. Another project is the new radar background map for Nevada. The aerodromes are precisely measured out of the DCS map system and will be used as background map to observe taxi operations on an aerodrome radar. The attached pictures show the results up to now. We hope you like the flavour…

There is not so much to explain. We want to come to a situation in which you are in radio contact as soon as you are logged in on any game server. The only requirement shall be, that the server and the requesting clients have Aries Radio installed. No configuration, no IP address/port fiddling. The appearance will not change that much. Some additional client functions will be implemented in the Aries Radio Panel like IFF/SIF, the eavesdropper and external frequency usage, which was bound to TeamSpeak before. The real advantage will be, that the radio communication capabilities will be strictly developed for radio frequency management and radar support. All the things, which TeamSpeak does not support. From the developer’s point of view, the advantage is the total control of the data transport and the avoidance of external modules being always a potential source of bugs. As explained in a post before, TeamSpeak may be used in parallel for meetings, chats and briefings. But it is not required for Aries Radio anymore. If the things are running as planned, it will be Ares Radio V 2.0.

The first shoot will be a build-in radio com in DCS. If a DCS independent party wants take part in the communication, they can use the GossipBox. It depends on the amount of trouble we have to expect whether we venture the next step to create a com management module, covering chat rooms and similar features.

It is planned, that TS will not any longer be connected to Aries. The additional use of TeamSpeak is up to the user, whatever he wants to do with it. What I am thinking on is, that TS occupies a certain PTT device system wide. Even if another window like DCS has the focus, TS always recognize its specific PTT. If you have the same PTT button defined for Aries and TS and you want transmit only on an Aries channel you would transmit on TS too. The same situation comes up with the loudspeakers. If Aries and TS have the same output device, TS and Aries would be audible in parallel and it could not be suppressed.

Hi Looney, I will keep that in mind for the first test phase. Thank you… @Hijack, You are even welcome for testing. Since the new module will be completely independent from TS, you can run it I parallel and be on the TS server of your choice. The only tricky thing is the device management. It could be possible, that the mic input and speaker output is given to TS and the new module in parallel. Even PTT settings could be mixed. Therefore, the setup has to be managed carefully.

No, it bases on an older development of mine. This module was developed for radio communication and voice recognition for a military flight simulator. It worked well in a LAN and used the DIS protocol. It needs to be tested in a WAN environment. The performance tests shall find out the latency, package lost and transport fluctuation we have to expect. It is a big difference to a LAN. If the results show, that we can manage these problems, we will change over.