towsim

Don't know whether this explains your case. The big change from 1.2.7 to 1.2.8 is the behavior of the window focus. As soon as you click another window than the DCS window, the DCS window looses the input focus an does not accept any input by joystick or keyboard. In 1.2.7, at least the joystick inputs remained active in DCS. This can be really confusing if you click something in the TeamSpeak window and the aircraft becomes uncontrollable...

Yes, it helps. Make sure that you really have the HOTAS Warthog throttle attached to your system. It seems, that your Windows cannot connect find the HOTAS Warthog throttle with Direct Input. As soon as it tries to connect a button to a radio function, an access violation is triggered. Check your configuration with ARD.exe and look for unusual button numbers. You should even redefine the device and button allocation with ARD. Since ARD uses the same interface software as Aries Radio does, the same error should appear in ARD if the error source is in the configuration. I parallel, send your \DCS World\AriesWings\ AriesAirborneRadio.ini file to support@ariescon.com.

I never got complains regarding Steam. One of my fellow sim pilots runs Aries Radio together with Steam without problems. It would be for interest to see your protocol files, if available, from the installation and from a session startup. It seems, that some important information are not available to the software.

The 'end click' bug is already in the bug fix queue.

Wenn dein Joystick Potentiometer verwendet dann ist das Wandern der Nullstellung höchstwahrscheinlich eine Verschleißerscheinung der Potentiometer. Mit der Zeit sammelt sich Dreck und Abrieb auf den Gleitflächen der Potentiometer, welche den Widerstand entlang der Gleitfläche verändern. Das führt zum Verlust der eingestellten Nullstellung und zu sporadischen Peaks bei denen sich vordergründig die Steuerflächen am Flugzeug verselbstständigen. Man kann durch minutenlanges hin und her bewegen des Joysticks mit Maximalausschlag versuchen die Gleitflächen zu reinigen. Das bringt für kurze Zeit einen Erfolg. Stellt sich das Problem nach einiger Zeit wieder ein dann ist wohl eine Neuanschaffung unumgänglich. Mann sollte dann darüber nachdenken, ob ein Joystick mit Hallsensoren nicht die bessere Wahl wäre. Hallsensoren arbeiten berührungslos und haben deshalb keine Verschleißerscheinungen.

As far as I know, it was not discussed in this way. The official VAD charts, created by Schleudi, a fellow sim pilot of mine, try to take care of the problem. But the main issue is, that the locations and orientations of the important map objects do not reflect the real world. Together with the north mark mix up, it is almost impossible to do a precise preflight planning. I was an air reconnaissance specialist and air traffic controller in another millennium. Together with the problems to align my GCI Radar project with the simulation environment, these issues came up.

A geographic system uses three different North Marks Magnetic north Almost not calculable, because it depends of the location of the magnetic North pole and the local tectonic environment like iron ore deposits and more. Therefore, every aviation map has reference lines for magnetic North determinations. True North This North direction is always along the meridians and can be taken for navigational planning. Grid North This is the most misunderstood direction. It is the result of the attempt to project the globe into a flat, two dimensional representation. Because there are a huge number of different methods used, the resulting representations are different.For position calculations in the simulation, a rectangular cartesian X/Y/Z system is necessary which is projected onto a map representation.Depending on the projection method used, the relation between the Y axis of the cartesian system to the meridians has a specific variation , called Grid Variation. In the DCS mission editor, Grid North is used for whatever reason. If you open the mission editor, you will see, that an exact vertical line (use the distance measuring ruler) has always the heading 360°. Regardless, what location you use. The vertical line is always parallel to the Y axis of the cartesian system (Grid North). You will even see, that the meridians are running into a different direction bound to the location you use. During a running scenario, two different north directions are used. The A10C follows magnetic North, indicated on the HSI while the F15C, as FC3 aircraft, shows grid North on the HSI. More confusion: magnetic north is calculated from Grid North + local magnetic variation, which is completely wrong. This is really confusing if someone wants to create an addon based on any navigational standard. Example: Measured RWY heading Sochi 62° G Grid variation Sochi measured from ME ~ 5° East True RWY heading measured from ME 62° G + 5° GV = 67° true Magnetic RWY heading from Cockpit HSI A10C 56° Magnetic Variation Sochi calculated from ME (56° - 67°) 11° East (instead of 6° East) Official reported Variation from http://worldaerodata.com/wad.cgi?id=RS08294&sch=Sochin is 6° East Conclusion Distances and directions cannot be taken from a map with mathematical precision. It is always distort by the projection method used. Only the use of geographical coordinates, based on WGS84 and a formula promises the right result (which is finally not compatible with DCS). DCS uses Grid North internally, which simplifies calculations, but delivers the most imprecise Results compared to the real world. Furthermore, two different North directions are used for different aircraft in the cockpit representation. The image below shows the rough relationship between the different North directions: Blue is the cartesinan system representing Grid North Black are the meridians (pointing to true North) and the parallels of latitude Brown is a magnetic North reference line

@Flagrum Yes, I do that for every frame.The invalidity of the device address appears even, if the player changes an aircraft in multiplayer oractivates a CA vehicle or would simply leave the game. The trap door is, if someone activates a CA vehicle, the situation does not change after the device 0 became invalid.DCS does not publish any information if CA is active. So the last active aircraft before would be taken as crashed as long as CA is active. The absence of position reports and the invalid device 0 address signals CA mode for Aries Radio. Therefore I cannot distinguish between crash or CA mode.

@astiles5470 in the real world,the airborne radios are off by nature because of a crash. There is only a so called air foil, a small transmitter, which transmits a wail on 243.0 MHz. This transmitter is activated automatically when the pilot ejects. With the help of the air foil, rescue helicopters can find a crash site easily.Beside the air foil, the pilot is equipped with a mobile radio to communicate with the rescue crew.Even here, 243.0 MHz is used. The problem is,I did not find any signal in DCS, which says unambiguously, that a pilot ejected from a plane or that an aircraft crashed. If someone here found a signal for this case, please let me know, I will build it in. The left and right earphones are set both active by default for all radios. So it is most likely, that the earphones were deactivated accidently during the configuration. But the important thing is, that you could help your colleague.

@Home Fries Just tested the switch behavior of the KA50 rotary switch. It seems to work normal. With the rotary switch I can select VHF1 out of VHF2 position and SW Position as well. The only confusing appearance is, that VHF2 is on top of the Aries panel while VHF1 is at the bottom. Vice versa, if I use the keys to select the radio, the rotary switch moves to the right position and the corresponding radio is selected. For the next big version change of the Radio it is planned to configure each supported type individually like DCS does. All PTT functions and Box select will then be different for each type if wanted. TF-51D is not supported up to now. I have to admit, I never started the trainer version up to now because of time available. But I am on a good way. Yesterday I got a intensive introduction for the P51 by one of my fellow pilots. So an integration is in the queue.

Ladies and Gentlemen, please do not start a competitive discussion about the radio products. It is up to the user what he prefers and nobody needs to be convinced. Headspace and me did it for the community. Not for money or for the hall of fame. Aries Radio came after TARS because of a missing standalone radio to be used for radar applications. The airborne radio was a derivative when I realized, that a self made stand alone radio would never be compatible with TARS as airborne radio. Aries focuses still on ATC and GCI which is still under construction. But, the spirits I've cited...

Ladies and Gentlemen, please do not start a competitive discussion about the radio products. It is up to the user what he prefers and nobody needs to be convinced. Headspace and me did it for the community. Not for money or for the hall of fame. Aries Radio came after TARS because of a missing standalone radio to be used for radar applications. The airborne radio was a derivative when I realized, that a self made stand alone radio would never be compatible with TARS as airborne radio. Aries focuses still on ATC and GCI which is still under construction. But, the spirits I've cited...

DCS made a change (bug fix ?) for full screen mode with version 1.2.8. It accepts DLL based windows without crashing the game. Nevertheless, there are two disadvantages for Aries Radio in full screen mode. The windows Z-order is controlled by DCS. Means, if the radio panel resides in the DCS view window, it will be hidden after each frame. It cannot be switched to foreground. If the panel is moved to a second monitor, then the DCS view window will disappear if you do a click in the Aries Radio panel. So the only solution in full screen mode would be to configure the radios in the cockpit as usual and leave the Aries Radio Panel disappeared. But as Leto stated, I could not measure a decrease in frame rate when I use windowed mode. For confirmation, I just measured it again and had, for one and the same scenery, 54 Frames/sec in windowed and full screen mode, covering the entire monitor with 1980x1200 pixels.

@Robin Hood Your modifications are OK. Normally you modify the background sound only for the given type. The A10 is an exception. The values for the A10 are also used as defaults for non supported types , FC3 and CA. The A10 modifications have no effect if you fly the P51 or UH1.... And yes, only the other players hear the modified background sound. For a better understanding: Background noise and voice degradation as well as voice vibration are done in the transmitter radio. The values are taken from the local INI file. Horizon, range and terrain masking, which cause increase of white noise and interruptions, are calculated in the receiver radio. The values are calculated interactively based on distance and positions.

@chromium this was a valuable information in your post # 272. Now I can compare the difference in the initialization sequence of the two situations. I keep you informed about the result. Thank you

@Home Fries On startup, Aries Radio assumes three radios per model. The key definition in the configuration bases on this assumption. Once the model is loaded, all non existing radios are deleted internally. If you take the P51, two radios are deleted and only box 1 remains in place. Therefore the configuration for box 1 applies. In case of the KA50 with two radios, the configuration for box 1 and box 2 apply. For non supported models like MI8 (will be supported if an English labeled cockpit is released) or FC3 or CA, all three radios remain in the game and the corresponding configuration for the boxes apply. Once you decide to use common PTT, then it is used for all models. It is not possible to have different buttons for box select with each model. Edit: You can even configure the different rotary switches for Box select directly in the DCS options. Chromium obviously used this clever solution. Only the PTT signal is mandatory to be in the Aries Configuration

@Robin Hood The main flight models have their own definitions. All the rest defaults to a standard background sound you should find the following sections: [uH1H_mod] FILTER=8 VOICE_MOD=1 HULL=10 70 PRIMARY_BUFFER=99 BKGND_ENGINE=UH1engine.snd 10 BKGND_COCKPIT=UH1CockpitNoise.snd 5 BKGND_SILENCE=UH1preStart.snd 0 [A10C_mod] VOICE_MOD=1 FILTER=8 HULL=0 0 PRIMARY_BUFFER=99 BKGND_ENGINE=jet1.snd 10 BKGND_COCKPIT=UH1CockpitNoise.snd 5 BKGND_SILENCE=A10preStart.snd 0 [KA50_mod] FILTER=8 VOICE_MOD=1 HULL=20 70 PRIMARY_BUFFER=99 BKGND_ENGINE=heli2.snd 3 BKGND_COCKPIT=UH1CockpitNoise.snd 5 BKGND_SILENCE=UH1preStart.snd 0 [P51D_mod] FILTER=8 VOICE_MOD=1 HULL=80 70 PRIMARY_BUFFER=99 BKGND_ENGINE=Prop1.snd 4 BKGND_COCKPIT=UH1CockpitNoise.snd 4 BKGND_SILENCE=UH1preStart.snd 0

@Home Fries The use of PTT is completely up to the user and independent of TeamSpeak.The following rules apply: As soon as you are in the game, the TeamSpeak PTT has no function anymore. Radio Box select for a single radio box works even as PTT. Common PTT, if defined, can be used, regardless of what box is selected for the moment. Even this key is completely independent of TeamSpeak. Voice activation, if used, it must be configured in Teamspeak and in Aries Radio. FC3 radios and CA radios cannot be configured with different keys. The key definitions for box select and PTT applies to all models. Modifiers can be defined only for keyboard use. If you use a device like joystick or throttle, only single buttons are evaluated. Configuring buttons or keys for Aries Radio should always be observed with the DCS configuration. If you configure Joystick button 2 as PTT in Aries Radio and as Toggle Gear in DCS, you will move the gear every time you use PTT. But PTT works as well as toggle gear. I will have a look to the P51. It is a good idea to enable the box automatically if only one radio is available. The Export.lua activation/deactivation has a confirmed bug. It will be solved for the next bug fix release. @Robin Hood You may open \DCS World\AriesWings\ AriesAirborneRadio.ini with a text editor. At the end of the file you find some sections like [A10C_mod]. The numbers you find in PRIMARY_BUFFER and after the BKGND_nnn keys are intensity definitions.If you lower the number for any BKGND_nnn definition, the volume for this sound will be decreased. I promise to install a slider in the configuration program for this case. You need to make the changes for each player in your community. If it is done only in your INI file, only your voice will change in radio communications.

@astiles5470 The bug is confirmed. It will be solved with the next release. Thank you. P.S. The bug is solved. The entire switch logic is reworked. It is possible now to dial other position than 1,2 or 3. The rotary switch selects now 1 = VHF AM (was 3 before) 2 = UHF 3 = VHF FM (was 1 before) The receiver switches are now integrated. It is now possible to switch a single receiver on or off.

@Esac_mirmidon according to your statement: you should load the Rhino as the last. After thinking a bit about the sequence it seems, that it is vice versa to that what I explained in Post #258. If you load Rhino first, it will be the first in the chain and sends its messed data to succeeding applications. But I think you should first test, if you can set your configuration inside DCS without the Rhino Software. I do the same for my ThrustMaster Hotas. I do not use the Target Software. All applications get the data directly from the device. It is a bit tricky if you deal with 3 position switches. But it is possible.

@Esac_mirmidon It is hard to predict any working solution. You should first check your Rhino profile if the buttons a configured to produce pulse, repetitions or any others. Most applications and even Aries Radio and DCS, expect simply a push and a release signal. My first question would be, if your troubles appear even with Aries Radio deactivated. The only logic I see, comes from the loading sequence.Any device like joysticks or throttles can be interrogated by any running software via Direct Input. The program calls an initialization function and will be inserted in a data delivery chain for the device. And this could be the point. The last loaded software is the first in the chain. Every application in the chain may modify the data. What I assume in your case is, if loading the Rhino driver as the last, it will be the first in the chain. All modifications made by Rhino are given to the subsequent applications like TS3 and Aries as well as DCS. The modifications made by Rhino are that what the other programs expect. Vice versa, if Rhino is the last in the chain (loaded first), all applications get the raw data from your X55 which could be unreadable for most of the programs. This is only an assumption. I would ask any X55 specialist here in the forum , if they experience the same situation and have probably a solution. Regarding the crash at the end, please send the session's log files from Users\[username]\Saved Games\DCS\Logs (.log and .crash) and DCS World\AriesWings\logs\AriesAirborneRadio_log.html to support@ariescon.com

As promised, the bug fix version 1.931 is available at http://www.ariescon.com/index10.html The Version 1.931 does not include any new function. It is a simple bug fix. If you are happy with version 1.930, you need not to upgrade. It is important to uninstall any older version of Aries Radio before you install the bug fix (even version 1.930). Your configuration will be saved automatically. The manual installation package is upgraded to version 1.931 as well. Bugs fixed in version 1.931: Radio DLL The 'Pop/Hide Radio GUI'function can now be used with the keyboard The evaluation of keystrokes is reworked. Now it is for sure, that modifier + key is well separated from key only. The bug, that DCS crashes if you start with a Combined Arms Vehicle is solved. Installer The edit fields for the Open Beta path definition works normal now. Quick installation Guide Some typos solved Added some explanations for the use of keystrokes for frequency dialing.

@astiles5470 If it helps, you may continue with 3.0.14. The versions before 3.0.14 do have an older internal API level define by TeamSpeak. This prevents using the current radio version with TeamSpeak < 3.0.14. But I am afraid, that the DirectX issue (if it exists) came up before 3.0.14.

http://forums.eagle.ru/showthread.php?t=104800&page=21 Post 206

It is a standard feature in Aries Radio. With the push of a button, you geht the current view from your A10 TGP automaticly saved as BMP.