towsim

Check in the Options\Controls menu the line for rudder control. It often happens, that an additional input device is connected to the rudder accidently. It happens when a new device was connected to the computer or sometimes when an update was installed. Simply delete the entries which were not installed intentionally.

Die meisten Funktionen, die in der 'alten' Export.lua als Beispiel aufgeführt wurden, funktionieren leider nicht. Wenn man Cockpit-Daten auslesen will muss, man einen kleinen Umweg gehen. Dazu sind zwei LUA Scripts wichtig (hier beispielhaft für die A10-C): DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts\devices.lua und DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts\ clickabledata.lua In devices.lua findet man den Index für ein bestimmtes Aircraft Device. In clickabledata.lua findet man die Bedienelement für das Device. Um z.B. Das UHF Radio auszulesen geht man folgenden Weg: Aus Devices.lua erfährt man, dass das UHF Radio den Index 54 hat devices["UHF_RADIO"] = counter()--54 In ClickableData.lua findet man die Bedienelemente der Box. z.B. Der Funktionsschalter mit 4 Stellungen elements["PTR-ANARC164-FUNCTION"] = multiposition_switch(_("Function Dial") , devices.UHF_RADIO, device_commands.Button_8, 168, 4, 0.1) device_commands.Button_8 steht für den index 3008. Um den Schalter in die Position 3 zu schalten: UHFradio = GetDevice(54) UHFRadio:performClickableAction(3008, 0.2) Das Cockpit hat den Index null. Cockpit = GetDevice(0) Jede Anzeige oder Schalter hat innerhalb des Cockpits einen index. Um diese abzufragen benutzt man die Standardfunktion Device: get_argument_value(n) Man erhält eine Fließkommawert, der der augenblicklichen Situation entspricht. Der Wert ist in der Regel zwischen 0.0 und 1.0. Der Wert muss dann entsprechend skaliert werden um eine darstellbare Anzeige zu bekommen. Beispiel fur verschiedene Anzeigeelemente: Cockpit:get_argument_value(540), -- AOA index high Cockpit:get_argument_value(541), -- AOA index normal Cockpit:get_argument_value(542), -- AOA index low Cockpit:get_argument_value(662), -- Gun ready Cockpit:get_argument_value(663), -- Nosewheel steering Cockpit:get_argument_value(730), -- Refueling ready Cockpit:get_argument_value(731), -- Refueling latched Cockpit:get_argument_value(732), -- Refueling disconnect Cockpit:get_argument_value(664), -- Marker beacon Cockpit:get_argument_value(665), -- canopy unlocked Cockpit:get_argument_value(655), -- landing light switch Cockpit:get_argument_value(716), -- gear lever Cockpit:get_argument_value(654), -- anti skid Cockpit:get_argument_value(737), -- red gear lever light Cockpit:get_argument_value(404)) -- Master Caution So lässt sich im Prinzip alles im Cockpit abfragen. Die Index Werte sind allerdings schwierig zu ermitteln. Ich habe mir ein kleines Programm gebastelt, das alle Cockpit Elemente zwischen 0 und 4000 im Loop abfragt und in einem Array speichert. Wird im nächsten Loop an einem Index eine Veränderung erkannt, weil ich im Cockpit einen Schalter umgelegt habe, so wird der entsprechend Index ausgegeben. Bei aller cleveren LUA Schrauberei habe ich aber schnell erkannt, dass eine selbstgestrickte DLL ungleich effektiver ist. Hier habe ich alle Möglichkeiten von C/C++ und die mächtige Windows API zur Verfügung. Das Erste was ich gemacht habe, war die Netzverbindung in die DLL zu verlegen um von der String-Pfriemelei befreit zu sein. Aber DLL ist eine andere Geschichte.

Sorry, no IM account. My order is already on the way. BTW, this board is exellent. It would be perfect, if there would be an output device on board to control some LEDs. Regards Mike

Hi brydling, I got some troubles with B256A13 board today. The A0037 chip died probably. I can measure main power on the board but the device is not detected by any device driver. Even the loader application doesn't detect the board. I made the test on different USB Ports and had no success. Is it possible to buy a single chip for a repair? Regards, Mike

For a 45 degrees dive bomb with a 90 degree roll in, the following formula could be used: Hight above Ground level in feet / 6080 + 0.5 = abeam distance to impact point. Example: 12000 ft AGL, space for the 90 deg roll in turn 0.5 NM (depends on TAS) abeam = 12000 / 6080 + 0.5 = 2.47 NM. for a 30 degrees dive: abeam = 12000 / 6080 / 0.557 + 0.5 = 4.04 NM. Where 0.557 is the tangent for 30 degrees. For 45 degrees, the tangent is 1.0. Therefore it is not included in the 45 degree formula.

Because of some requests on the support channel, I made a revised version of AriesRadio.luac. The following bug fixes are made: If a manual frequency is selected on the Aries radio panel, it is ensured, that it is the same frequency as stored in the corresponding radio box. You may see another value on the cockpit box display, but the valid frequency is that, seen on the Aries radio panel. This is a circumnavigation of the current frequency bug in DCS World. So if a tanker frequency is set with the Aries radio panel, it is ensured, that you are on the right frequency. In single player mode you can be sure, that you are on the right frequency to contact ATC. The KA50 SPU-9 radio selector dial button was fixed so as to handle the right radio selected in the Aries radio panel or with the SPU-9 dial button. To install the fixed version, simply copy the attached AriesRadio.luac (in AriesRadio.zip) to the DCS World\AriesWings folder. It replaces the existing file there. I will delete the internal frequency monitor as soon as DCS has fixed the frequency bug. Regards, Mike AriesRadio.zip

Probier mal die Frequenz um 10 MHz nach oben oder unten zu verstellen. Im Augenblick existiert ein Frequenzproblem in der aktuellen Version.

@flankerOne At the moment we have to accept a known bug in DCS World. The frequency selection shifts the frequency by 10 MHz. If you hear the terrible sound then the resulting frequency set is outside the admissible range for Amplitude Modulation (AM) or Frequency Modulation (FM) , which causes the sound. I just made the check for the radio selector and the PTT + select. The behavior is as intended in my DCS World version which is the latest published. @OttoPus I apologize, if I speak even about the simple thing, because I don't know your actual configuration. Open the Airborne Radio configuration program (ARD icon) The behavior of the PTT + select in the setup program depends of the definition of Common PTT. It is not possible to use 'Common PTT' and' PTT + select' together. If you want the PTT function together with the' box select', make sure, that Common PTT is not defined. Means, that there is no definition in the 'Button/Key' column for Common PTT. If there is one, press the 'arm' button of Common PTT. You will notice, that the definition disappears from the edit field. Unpress the 'arm' button to take over the deletion. To be sure , that there is no misunderstanding, the select + PTT means, that you have to push and hold the selected device button as long as you speak. If you still have troubles, please send the file DCS World\AriesWings\AriesAirborneRadio.ini to support@ariescon.com. I will check if there is a mismatch in there (even for FlankerOne). Regards Mike

Accidently, I came behind a possibility to configure ON/OFF switches so as to be synchronized on simulation startup. It implies, that 'Synchronize Cockpit Controls with HOTAS Controls at Mission Start' is set in the Options/Misc menu. The entire procedure bases on modifications of a specific device LUA file found in C:\Users\[user nasm]\Saved Games\DCS\Config\Input\A-10C. In my case, I used the Joy1 A0037 {D3A1DC80-25DC-11e3-8002-444553540000}.lua for the B256A13 Joystick controller board. DCS obviously makes a difference if a procedure is named for an up or down command or if a key ID is set instead. Do not ask for the logic behind it, I have no idea. The example shows a definition for the AHCP HUD mode , Day/Night. In its original definition the corresponding entry is: {combos = {{key = "JOY_BTN21"}, }, down = iCommandPlaneAHCPHUDModeDayNight, name = "HUD Mode switch Day/Night", category = "Armament HUD Control Panel"}, This definition works like a bell button. Every time you move your JOY_BTN21 hardware switch to the ON position, it sends a push signal to DCS, causing the cockpit switch to toggle. The OFF position sends no signal. Therefore no action is observed with the OFF position. In the previous post I described the possibility to get a signal in any case, for OFF and ON. But the initial state at mission start was not synchronized. If not manually set in the correct position, the switch worked in reversed mode. The following modification let DCS check the hardware switch position at startup: {combos = {{key = "JOY_BTN21"}, }, down = 3006, up = 3006, cockpit_device_id = 7, value_down = 0, value_up = 1, name = "HUD Mode switch Day/Night", category = "Armament HUD Control Panel"}, The key ID 3006 is taken from clickabledata.lua , AHCP section, and the device ID for the AHCP panel (7) from devices.lua. The key words 'value_down' and 'value_up' define the number to be send to the software switch in DCS. A little trap door is the signal evaluation by DCS . 'ON' does not mean an active signal in all cases. I found some switches which needed an active signal for the OFF position. So it has to be tested for every single switch which position needs which signal. The ON/OFF/ON switches can be defined in a similar way. But the mid (OFF) position is not recognized at startup, only the two possible ON positions give a signal. The advantage of this mod is simply the possibility to have all ON/OFF switches in the same position like set with the hardware switches. It does not work with spring loaded switches. Because this types have an additional logic for ON and OFF internally. Regards, Mike

Here my results, found out for my A10-C desktop panel: Interface, Joystick Controller B256A13 This USB board is very comfortable because it does not need any additional driver software. It is recognized by DCS and appears two times as 'Joy 1 A0037' in the options menu. Since it has two joysticks on board, up to 254 switches can be connected to the board. Options Menu Before any modification to LUA scripts are made, all desired switches should be set up in the options menu. This is necessary, because DCS writes the later modified scripts every time the options menu is invoked. ON/OFF switches Unfortunately, some DCS switches are supported only as toggle switches like bell buttons, but are actually ON/OFF switches in the cockpit. If your external hardware uses a ON/OFF switch, a small modification in a LUA script is necessary. First you have to identify your device. DCS maintains a specific LUA script for each external device which is HID compatible. For Joysticks and similar devices go to C:\Users\[username]\Saved Games\DCS\Config\Input\A-10C\joystick You find there all LUA scripts of the supported devices. In my case, for the B256A13 board, I found two scripts, Joy1 A0037 {D3A18E60-25DC-11e3-8001-444553540000}.lua Joy1 A0037 {D3A1DC80-25DC-11e3-8002-444553540000}.lua As an example, I take the TGP switch from the AHCP panel. For all modification of LUA scripts Notepad++ should be used. Open the LUA script of the device of your choice. Search for 'TGP' in the file you will find the line {down = iCommandPlaneAHCPTGPOnOff, name = "TGP switch ON/OFF", category = "Armament HUD Control Panel"}, Modify the line so as to have {down = iCommandPlaneAHCPTGPOnOff, up = iCommandPlaneAHCPTGPOnOff, name = "TGP switch ON/OFF", category = "Armament HUD Control Panel"}, This causes an action every time the switch lever is moved, regardless of the direction. The disadvantage of this solution is, that the hardware switch position must be correct on startup. Otherwise you have a reversed logic with this switch. ON/OFF/ON switches These type of switches have 3 positions. The up and down position cause a signal while the mid position (OFF) has no connection. The Land/Taxi light switch has 3 defined positions in the LUA script. But the OFF position cannot be used because the switch gives no signal. The modification is as Follows. search for ' iCommandPlaneLGPLandLight' You will fin the line {combos = {{key = "JOY_BTN15"}, }, down = iCommandPlaneLGPLandLight, name = "Landing Lights On", category = "Landing gear panel"}, Insert an 'up' command so as to have {combos = {{key = "JOY_BTN15"}, }, down = iCommandPlaneLGPLandLight, up = iCommandPlaneLGPLightsOff, name = "Landing Lights On", category = "Landing gear panel"}, ' iCommandPlaneLGPLightsOff' is lend from another line in the file, which would normally be used for the mid position of the switch. The same modification must be done for the 'taxi lights' line: {combos = {{key = "JOY_BTN16"}, }, down = iCommandPlaneLGPTaxiLight, up = iCommandPlaneLGPLightsOff, name = "Taxi Lights On", category = "Landing gear panel"}, Now the logic calls iCommandPlaneLGPLightsOff every time you leave the most up position and the most down position. Even here, the correct switch position must be set on startup. But the position can be corrected after startup which is not possible with ON/OFF switches. The attached image shows my desktop panel for which the modifications were made. The panel does not reflect the original layout of the A10-C panel. It was made for desktop use, because there is not enough space in my office for a complete pit. All other rooms are under the sovereignty of my wife. My desk is even used for software development, therefore a comfortable compromise was necessary. Regards, Mike

Hi Milli, thank you for answering. I studied the link and found it very useful. If I take it as described, I can save at least one input line per switch. The only missing color in my rainbow is, that the initial state of the hardware switches cannot be synchronized with the cockpit display. But it is a step forward. I will post my test results here as soon as my panel is ready. Thanks, Mike

I am just playing around with some hardware switches for the A10-C and run into a problem. As an example, I take the TGP On/Off switch from the AHCP panel. In the options menu, the TGP switch is handled as a toggle switch. So one pulse switches it on, the next pulse switches it off. It is obviously not foreseen to follow the logic of a hardware switch with two positions, on and off. Here my question: Is it possible to modify any LUA script so as to use the TGP switch as On/off instead as a toggle switch? For the moment I fake the function by defining two input devices for the TGP switch. That works reliable but costs one more input line and there is no possibility to synchronize the cockpit switch with the hardware switch on startup. I think, with all the pit builders here in the community, I am not the first who had this problem. Regards Mike

Some new findings: If I double the size of the page file, the error comes up after the double download amount. If I move the page file to another disk than the install disk, the error comes up short after the download starts. With a page file of 12 Gbyte, I can download about 200 Mbyte. A page file of 20 Gbyte allows roughly 400 Mbyte. Necessary size for the page file would be 90 Gbyte for the entire download, which is not left on my install drive (SSD). It seems, if the page file capacity is used up, the installer tries to store intermediate files in the user folder, which causes the crash. Since I start the update as administrator, I would not believe in an access rights failure. What I know , the size of the download file ( 1.8 Gbyte)is exceptional high compared to the download of other users. So might be that I catch a very seldom situation which is not covered by the DCS updater.

Hi, after several unsuccessful trials to download the latest DCS Version, I need help by the experts: After 200 Mb of download the process stops with an error window, telling me, that the system cannot find a path to a folder in "C:\Users\mike\AppData\Local\Temp\... Up to now I tried the following procedures, all with the same result: Update out of the DCS World start window Out of C:\Program Files\Eagle Dynamics\DCS World\bin with: DCS_updater.exe update. Out of C:\Program Files\Eagle Dynamics\DCS World\bin with: DCS_updater.exe repair The attached file shows the content of the error window. I even took care, that no other process is running in parallel, which could impact the download process. My internet access is running with about 5 Mbit, which should be sufficient for such a download. Any help would be welcome. Regards, Mike Autoupdate.log: 00000.000 INFO : === MiniLog opened UTC 2013-10-03 08:53:57 00000.090 INFO : Current version: 1.2.6.17746.255 00000.090 INFO : Arch: x86_64 00000.090 INFO : Lang: EN 00000.090 INFO : Installed modules: MI-8MTV2,A-10C,WORLD,KA-50,P-51D,CA,FC3,UH-1H 00000.090 INFO : Checking for updates... 00000.355 INFO : Repair is available. 00000.355 INFO : Update is available. Latest version is 1.2.6.18651.276 00003.812 INFO : Actualizing local cache... 00010.601 INFO : Downloading update: version=1.2.6.18651.276, timestamp=20130927-211720, database_id=e17143b01f76e82bc20c6a55b4c723624d0fa0f7f7f4c45be3a72cfea2c2723a, database_size=1760797 00021.251 INFO : Updating the updater... 00021.251 INFO : Downloading 1776432 bytes in 2 objects 00021.251 INFO : Cached 0 bytes in 0 objects 00029.559 INFO : Applying updates... 00029.636 INFO : === MiniLog closed. 00000.000 INFO : === MiniLog opened UTC 2013-10-03 08:54:27 00000.085 INFO : Current version: 1.2.6.17746.255 00000.085 INFO : Arch: x86_64 00000.085 INFO : Lang: EN 00000.085 INFO : Installed modules: MI-8MTV2,A-10C,WORLD,KA-50,P-51D,CA,FC3,UH-1H 00000.800 INFO : Actualizing local cache... 00007.551 INFO : Downloading update: version=1.2.6.18651.276, timestamp=20130927-211720, database_id=e17143b01f76e82bc20c6a55b4c723624d0fa0f7f7f4c45be3a72cfea2c2723a, database_size=1760797 00007.886 INFO : Downloading 1809463805 bytes in 718 objects 00007.886 INFO : Cached 3537229 bytes in 3 objects 00910.965 ERROR : Can't download object [url]http://update2.eagle.ru/dcs/objects//80/80ebb33ac6453b33c7cc99f3b20e8b0add0fd02be81d2a43afcf7d7ade7f89ed[/url]: create("C:\Users\mike\AppData\Local\Temp\DCS\update\80\80ebb33ac6453b33c7cc99f3b20e8b0add0fd02be81d2a43afcf7d7ade7f89ed"): (3) The system cannot find the path specified. 00911.040 ERROR : Caught an exception: Can't download object [url]http://update2.eagle.ru/dcs/objects//80/80ebb33ac6453b33c7cc99f3b20e8b0add0fd02be81d2a43afcf7d7ade7f89ed[/url]: create("C:\Users\mike\AppData\Local\Temp\DCS\update\80\80ebb33ac6453b33c7cc99f3b20e8b0add0fd02be81d2a43afcf7d7ade7f89ed"): (3) The system cannot find the path specified. 01177.595 INFO : === MiniLog closed.

The current Aries Radio was successfully tested with TeamSpeak 3.0.13. Even a mix of older versions and the latest TeamSpeak Version work without problems. Nevertheless, a small limitation with TeamSpeak 3.0.13 seems to be an increase in package latency over the internet. It takes about 0.5 seconds until a voice package arrives at the receiver. This is a subjective observation. If someone experiences the same, please post your observations. Regards Mike

Check the ILS dials. Seems to be the same problem. After an accidental left click, they are not controlable anymore.

The bug is well known since DCS World version 1.2.6.17746. There is a increment / decrement problem in DCS. A lot of gamers reported this bug even without an installed Aries Radio. They complained, that the tanker frequencies cannot be dialed. They have to go 10 Mhz higher than the published frequency. Aries Radio does not evaluate the single digits. It takes the complete frequency from the box, which is delivered in Hz and calculates the 100, 10, 1 and the fraction digits from that number. Vice versa, to set a frequency, the entire value in Hz is given to the radio box. The DCS internal logic then sets the single digits. What I checked out by protocol: VHF Box 1 is set to 129.000 The second turn button at the box is set from 9 to 0 (129.000 to 120.000) The Box shows 120.000 which seems to be the expected value But DCS internally sets the frequency to 130001568.0, which corresponds to 130.000 MHz, which is shown on the Aries Radio. If I set the frequencies by the Aries Radio Panel : Decrement the third digit from 0 to 9 (130.000 to 129.000) Aries Radio sends 129000000.0 Hz to DCS VHF Box1 DCS internally sets the frequency to 130001320.0 Hz There is even no logic behind the DCS frequency evaluation. So I am not able to compensate this bug. I would expect DCS to repair the logic with the next update. Regards Mike

http://forums.eagle.ru/showthread.php?p=1880239#post1880239 Chapeau! Mr. Wags

The crash at the end of a mission should be solved in version 1.234. DCS has shorten the time for cleaning up resources in a mod DLL. It could even be, that they never took care of mod DLLs. Nevertheless, if the time exceeds 30 ms, DCS will crash. So I decided to kill all my threads instead to end it controlled. For some installations this time seems still to be too long. I keep an eye on it. Mike

New Radio Version 1.234 Dear Aries Radio user, Version 1.234 of Aries Airborne Radio is available as free download at http://ariescon.com/index10.html. The following changes and enhancements were made: The shutdown sequence was reworked one more time to ensure a stable mission end. The versions between LUAC and the Airborne Radio DLL is tested. If the versions do not match, a protocol file entry is initiated. The new version is tested with the latest releases of DCS World and TeamSpeak. TeamSpeak may be restarted during a running session. This avoids to restart the multiplayer session in case of a TeamSpeak crash. It is now possible to change the TeamSpeak channel or server during a running mission. The new version may be installed over the existing version in case of an upgrade. The existing configuration settings for the radio will be saved. Before installing the new version, please consult the quick installation guide for details. For users, who had troubles with the windows installer, a new manual installer is available in parallel. Have fun Mike

Here an example for A10C UHF Box 2 (not for other models!) first you need the device ID of the radio: UHFRadio = GetDevice(54) --The returned value should be tested on validity. If the model was changed on the fly,UHFradio is not longer valid. Now you have the following functions available: UHFRadio:is_on() -- returns 0 if the radio cannot be used . UHFRadio: set_frequency(freq) --freq is the desired frequency in Hz. The dial buttons are set automatically freq = UHFRadio:get_frequency() -- returns the current frequency in Hz set in box 2 UHFRadio:performClickableAction(3007, 0.0) -- sets the mode dial to MANUAL UHFRadio:performClickableAction(3007, 0.1) -- sets the mode dial to PRESET UHFRadio:performClickableAction(3007, 0.2) -- sets the mode dial to GUARD The returned frequencies are not exact the expected Hz values. There is always an unreliable fraction of about 1000 Hz or more. You need to find a good rounding function to get a clean value. To get the positions of the mode dial, you first need the device ID of the cockpit panels: MainPanel = GetDevice(0) --The returned value should be tested on validity. If the model was changed the ID is not longer valid. UHFlbTB = MainPanel:get_argument_value(168) -- returns the position of the master dial (left dial). (the smiley is a 8. The editor prevents a correction) UHFrbTB = MainPanel:get_argument_value(167) -- returns the position of the mode dial (right dial) The channel selector for the PRESET case is a bit tricky and different for the VHF and UHF box. If you need that too, please post. The two other boxes work in the same way with different iDs. You find the IDs in: \DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts\clickabledata.lua \DCS World\Mods\aircrafts\A-10C\Cockpit\Scripts\devices.lua Regards, Mike

Yes, it is definitely a bug. It can be seen if someone uses Aries radio. As soon as you set a frequency on box 1 with a full tenth, the box shows the intended frequency and the Aries Radio panel shows the internal set frequency which is different by 10 mHz. It seems to be an rounding problem for the digits. I can even see for example 139.000 on the box, while the Aries Radio panel shows 140.0. The problem is, that DCS stores the frequency internally in Hz but as floating point value. So you do not have a clean value in Hz. There is always a fraction in the rage of 1000 Hz (sometimes more) which have to be rounded carefully to the closest 25000 Hz border. It seems, that this logic was changed.

Please ensure, that AriesConfigurator.exe is started out of: C:\Program Files\Eagle Dynamics\DCS World\AriesWings or wherever the AriesWings folder was created by the installer. The program checks the local directory to find the corresponding .INI files. If started from a different folder it would show this message. But you should check first the registry for the DCS entries. It could be: HKEY_CURRENT_USER\SOFTWARE\Eagle Dynamics\DCS World or HKEY_LOCAL_MACHINE\SOFTWARE\Eagle Dynamics\DCS World there should be a 'path' variable which shows the path to DCS World. If the path found does not match the actual path or the key was not found then the program checks the local directory with the name 'AriesWings'. If all that fails, the described message comes up. The attached ZIP file contains a configurator, which has an extended log file output. Please copy the ' AriesConfigurator.exe' to theAriesWings folder in DCS World. If you experience the error with the special configurator, please send the log file 'AriesConfigurator_log.html' to support@ariescon.com. You find the log file in the AriesWings folder. When inspecting the registry, use extreme caution. Every manual change may impact your system stability. Regards Mike PS Make sure, that you use the 64 Bit RegEdit.exe for the registry. AriesConfigurator.zip

I am sorry for that. The upgrade to version 2.0 will have a configuration spread over a couple of pages. So the size of the window can be held small. But don't expect version 2.0 soon. The next will be 1.233 with some stability enhancements. Regards Mike

Would be nice if you could save the log files next time you experience a crash. It is planned to release a new version this week. So if you could wait, the problem should be solved. Regarsds Mike