towsim

I am working on this issue and we localized the module which causes the bug. I beg your patience for a couple of days. We need to test the version before we release it. The bug release will fix the login issue and the problem with different devices used for PTT. We will even publish the Gossip Box and the airborne radio in one Package to avoid version issues. Please take note, the next release experienced some changes in the internet message format. Versions before 1.96 will not work together with the next release.

I will have a look to SLMOD to find out possible interferences.

@Dojo I think I was too fast with my bug hunting. In the yesterday test, my fellow pilots used the official 1.955 version while I used the modified LUAC. The surprise was, that all pilots could get in contact with the tanker and that with the older LUAC. So what I did today was to repeat the test with your Mission and the old LUAC. And it was successful. The only remarkable situation was, that I had to call the tanker twice for initial contact. Now I am a bit lost, because I cannot produce the error anymore. We have another session this night and we will discuss how to come together.

@LowLee Sorry, I didn't read your posting that exact. The key is, the Open Beta configurator takes the path from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings\DCSWorldPathOB Have a look to this registry entry and check if the path matches the real open beta location. If not, you should enter the right path and try it again.You can even send me the log file of the Open Beta Configurator to support@ariescon.com. It should be found at: \DCS World OpenBeta\AriesWings\AriesConfiguratorOB_log.html

VHF could be another issue. I have a frequency mix up in the mission editor. That is the reason for the one day delay.

Ok, I got it to run even on UHF. I will publish a new LUAC file tomorrow which should solve the issue. Thanks to all for your help TOWSIM

I tried the mission Dojo sent. I can confirm the issue. But it seems to be an UHF issue. VHF AM frequencies work normal. I have a rough direction now...

I just tested this out.If the tanker is available on VHF AM and you speak to other players onbox 2 or box 3, the keyboard command for "ready precontact"is not sent to the tanker. If you switch back to box 1 with mic forward, the command is passed through and all works normal. The wrong logic of the rotary switch does not prevent the message relay. With mic forward it is switched to VHF AM again. In so far it matches the different descriptions of the issue. Some can contact the tanker initially but get no response on 'ready pre contact'. They obviously talked to other players on the other boxes after the initial contact. If Aries is deactivated , I assume they do not change to another box if the players talk to each other. Therefore it seems, that Aries is the cause, because it suddenly works. A visual feedback is the color of the menu entries. If they appear in black then the wrong box was selected. So the solution should be to push mic to activate the corresponding box before you send the keyboard command. But keep an eye on the menu, Mic is a toggle switch for DCS. It let the menu appear on the first switch and disapper on the second.

What I found out so far in regard to the refueling procedure: DCS obviously changed the configuration procedure to simplify the contact to the tanker. If the key sequence (# - show menu) ,(F6), (F1) is used, the correct tanker frequency is set and the corresponding box is selected automatically. All succeeding steps work as usual. In case of an existing mission, the Mission editor (at least in my case) does not store a changed tanker frequency. It defaults all the time to the old frequency. But the contact procedure is always successful. I tested different situations with automatic frequency setting and explicit box selection and even with a UHF tanker frequency. Only if I select the UHF box for contact, the tanker does not respond. In all the tests, Aries Radio was active. And, as soon as Box 1 was selected, I got contact, regardless what frequency was set. Aries shows only the actual frequency in the corresponding box. It is not involved in the tanker procedure at all. But to stay honest, error free software does not exist on this world. If someone has more helpful information, please post it and attach the MIZ file which was used.

@Reaper73 According to your log file, the section [PTT_box1] was never found in AriesAirborneRadio.ini. It could be, that the section was deleted or changed accidently.You should open the file \DCS World\AriesWings\ AriesAirborneRadio.ini with a text editor. The first line should contain the section [PTT_box1] followed by the device name in the third line. Check, if the section is present and the required device name matches the spelling of that in the section[PTT_box2]. You can even send me your \DCS World\AriesWings\ AriesAirborneRadio.ini. I would check if the entries are correct.

@Eddie I think we both mean the same. If you have three different PTTs, I said, a specific radio is selected for transmission. You see the device from the technical point of view where it would be more correct to say, the microphone input is feed to a specific radio. Is that OK?

Ok, got it...

@Snoopy it is a bit confusing for me. Please correct me if I am wrong. The upper row turn buttons are used for volume control and may cut off the reception on the given device, if pushed. The main rotary switch selects the device, which receives my voice for transmission, if PTT is activated. Beside the mechanical selection of the transmission device (main rotary switch), the pilot can select VHF FM, UHF or VHF FM with the coolie at the throttle. The next PTT then directs the output to the selected transmitter, regardless of the rotary switch position. Only one device can be selected as transmitter at a time while reception on all three boxes is possible in parallel. Is that correct ?

@HMA it was the unfortunate attempt to connect the rotary switch to the radio selection, like in the Huey. I think it is only one way in real life. Means, if you set the rotary switch, a specific radio or intercom is selected for transmission. If you select a radio with HOTAS throttle coolie, the rotary switch should be unaffected. I will change it with the next release. The behavior after reconnect is strange because all variables in the DLL are set to initial values. The rotary switch should be in the empty position (no label) and no radio is selected in the Aries Radio panel. Nevertheless, I will test it out.

@Eddie Yes, it is a known bug.It is in the List. @kaiza If you have a .crash file from such a session, it would be helpful if you could send it to support@ariescon.com. The Gossip Box for version 1.955 is almost done. It should have been released on Nov. 11th. But we experienced a receiver trouble with uncontrolled white noise.The reason was not found up to now.

@LowLee Could you check even HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings. The protocol entry seem not to be right. If you say standalone folder, do you mean the regular DCS folder or the Aries Radio standalone version?

@LowLee just tested this out. The open beta configurator does it's work. Probably you mixed up the icons? The open beta configurator is named AOB while the standalone radio configurator is named ARO. I have to admit, the naming is not that smart. Even the presets with FC3 seem to work normal. I tested the F15. Changing to preset and incrementing and decrementing channels works normal. If there is really a bug, please send a more detailed description to support@ariescon.com.

@Home Fries Fullscreen would be possible meanwhile, even in the current version. Whereby, it is not fully tested. Former versions simply crashed DCS while the current version remains at least active. If you run DCS on one monitor in fullscreen mode and the Aries panel resides on a second monitor , there would be no difference in usage. The only disadvantage is, that it is impossible to have the Aries Panel on top of the DCS window. It will disappear in the background immediately. So fullscreen with a visible Aries Radio Panel requires an additional monitor which is not integrated in the DCS desktop area. Another case is FC3. FC3 has no controllable cockpit radio boxes. If the external radio panel is not visible, there would be no visual feedback unless you use the small LCD of the G13 or a similar device to display the frequencies. The latter is an interesting idea. I will have a look to it. Mission scripting, integrated in Aries, to display the frequencies in the screen is not an option because it would be too much for a normal user.

@Chromium I am working on it. Will contact you as soon as possible.

@random, could you describe how you solved the issues? It could probably be for interest in the documentation.

If you do not have the DCS open beta version installed, all open beta entries may be deleted. The entry is used by the TeamSpeak plugin DLL to find the open Beta export.lua and by the open beta configurator.

No exact date for the Moment. I will start the upgrade with the next DCS model release.

@Shane45 I just found the other thread you started with this problem. Therefore some more questions. Is your Saitek device listed in the Aries Configurator ? Does the registry entry at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AriesWings\DCSWorldPath show the correct path to the DCS world installation? If you open the Log file DCS World\AriesWings\AriesConfigurator_log.html, you should find as first line the DCS world installation path. The Configuration results from ARD are stored in the subfolder 'AriesWings' as AriesAirborneRadio.ini. If the path is not correct you have a problem with the registry entries.

@Shane45 It seems, that the results of the configurator (ARD) cannot be written to the right folder or it does not have the access rights. Try the following: Start ARD with administrator rights. It is not sufficient to be logged in as administrator. Do a right click on the ARD icon and select 'Compatibility' . Activate the check mark for 'Run this program as an administrator' Set up your devices in ARD and save it. If this procedure fails, please start up a short mission. It is not necessary to test the radio. I need only to see what files are loaded and their folders. After Mission end send the following files to support@ariescon.com: \DCS World\AriesWings\logs\AriesAirborneRadio_log.html \DCS World\AriesWings\AriesAirborneRadio.ini

A question to CH users: Does anybody use the CH pro fighter stick together with Aries? If yes, it would be for interest how the joystick has to be configured so, that it can be used with Aries Radio. The troubles are, that the buttons cannot be recognized in Aries Radio in spite of a correct configuration in the Aries Configurator.