LeCuvier

This is true for the limited number of A-10C commands that are represented by switches/buttons on the Thrustmaster Warthog throttle and stick. For many other commands there are only the ON/OFF toggle bindings that don't work with maintained switches.. I have therefore created a lot of additional bindings and published them in this thread https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4691602_menu ED could just copy these and add them to "default.lua" but they don't seem to be interested. The disadvantage of adding these bindings oneself is that they disappear in the process of update or repair. So you have to use a mod manager like OvGME or manage the backup/restore manually.. The only module that has seen a large number of additions based on what the user community provided, is the AJS37 (Viggen).

You're absolutely right, it's a work-around. But it works for me, on the Hornet and most other aircraft, and without these work-arounds I wouldn't enjoy flying so much. The only aircraft module (to my knowledge) where all the user-suggested bindings were added is the Viggen. That one that has an extensive set of bindings, with slow and fast variants for many of them.

Oops, I forgot that I added these 2 lines to my "default.lua" file: {down = fuel_commands.DumpSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, name = _('Fuel Dump Switch ON'), category = {_('Left Console'), _('Fuel Control Panel')}}, {down = fuel_commands.DumpSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = -1.0, name = _('Fuel Dump Switch OFF'), category = {_('Left Console'), _('Fuel Control Panel')}}, I apologize for confusing you!

ED has given you that possibility quite a while ago. See my bindings in the screen shot. I use JOY_BTN19 on my throttle for Fuel Dump ON and JOY_BTN19_OFF for Fuel Dump OFF

1. The lines in that file do not change when you add/delete/change bindings. These actions are recorded in the related "....diff.lua" file under saved games. So, if you have deleted default bindings from the F16 MFD 2 for the A-10C II, you should see these recorded in the file "F16 MFD 2.diff.lua" under "C:\Users\xxxxx\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\joystick". 2. The file name relates to the hardware ID. Your MFD hardware is identified as "F16 MFD 1" and ... 2, and the file name relates to that hardware ID. 3. There is no reason why the Thrustmaster MFD's could not be used with the Hog. 4. Only ED can answer that. It certainly is a complex subject and I have made suggestions to streamline the functionality, but there was no response from ED. Note: for some aircraft modules default bindings are defined by "...diff.lua" files in the aircraft folder structure. Example: FA-18C has, among others. the file "F16 MFD 1.diff.lua" under "K:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick". This file has the same structure as the related file that records your changes under "\Saved Games...". I do not understand all the warnings you get and I cannot look into your setup. As you seem to be a relatively new user (guessing by the number of posts you've made), I still recommend you stay awy from things defined under UI Layer.

There are many commands that were duplicated across all aircraft modules. UI Layer was introduced later in order to reduce duplication. So these commands only need to be bound once under "UI Layer" and they will be effective across all modules. What's important: UI Layer bindings override whatever you have bound to a button in an aircraft module. The "General" category is older. It was based on a similar concept, but it does not override module bindings. I hope that ED will consolidate all common commands under UI Layer, but I'm not sure they will. The F16 MFD 1 and F16 MFD 2 have default bindings to the OSB buttons in the sim MFD, and frankly I don't think it's a good idea to bind them to PAUSE or something like that. These default bindings are defined in the files "F16 MFD 1.lua" and "F16 MFD 2.lua" under "K:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick". For example, the line below binds JOY_BTN19 on your F-16 MFD module to OSB19 of the right MFD in the sim. {combos = {{key = 'JOY_BTN19'}}, down = iCommandPlaneRightMFD_OSB19, up = iCommandPlaneRightMFD_OSB19_Off, name = _('Right MFCD OSB 19'), category = _('Right MFCD')}, However you can bind these buttons to something else. Why you got the warning although you had removed the bindings, I have no idea. I suppose you saved your changes before you tried to re-bind them?

I have a very modest hardware config with i 4790 processor, 16 GB of RAM and a GTX-1080 GPU with 8 GB RAM. I tried a free flight mission over Syria flying towards Aleppo in OB MT preview. At cruising altitude (above 4000 ft) my frame rate was around 70 FPS, with or without A-A radar. Also overflying Aleppo at 3000 ft or more, frame rate was fine, I could not see any impact from A-A radar. But when I overflew Aleppo at around 500 ft above ground, the A-A radar had a big impact. With A-A mode Off I was around 48 fps. But with A-A ON and AIM-120 selected the framerate dropped to 11fps. I cyced several times between A-A radar ON and OFF and the pattern repeated.

1. Only the AMPCD has controls for Gain and Symbology. You are showing the bindings for one of the MDI's. Those don't have controls for Gain and Symbology. 2. I suppose you have deleted the default bindings and the commands are still there. You can cancel all changes to keyboard bindings by deleting the file "Keyboard.diff.lua" in the folder "C:\Users\mark\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\keyboard" before starting DCS World. You will then have to re-enter all keyboard bindings that are not default.

@lonnie604: You need to give more detail. Does this issue occur only when you do a cold start or also when the mission starts with a running engine, i.e. Hot Start or Airborne Start?

I did a little more research, and I find that by default, with RWS mode selected, I'm actually in Latent TWS mode. This becomes visible when you click on the DATA button in the Radar MFD. You can disable the Latent TWS mode now to put the radar in RWS Attack mode, and now the undesignate button does what you expect.

I'm not a Hornet expert, but it seems to me that the function has changed. I tested in RWS mode and there were several enemy aircraft in the radar's field of view. I designated one target and got a lock. When I pushed the undesignate/NWS button it designated another one of the available targets. Pushing the undesignate button actually cycles between the available targets. Not a bad functionality, but different from what I expected.

The problem is was back. I was able to update OB to the latest version yesterday, and this morning I played online, Trying to play tonight and it was nightmare time again. Login failed and I could only fly Tf-51D and Su-25T. DCS World OB version: Multithread Preview 2.8.6.41066 Trying to launch the OB Single-Thread: Oops there is a new update. So I update to 2.8.6.41066.1 and oh joy, OB loads ok, and the MT also. Hopefully it will stay this way!

In my view, there are 2 issues: 1. The authorization server(s) broke down 2. The offline mode is not working correctly. We should be able to play offline for a reasonable period of time. And that period of time should be generous. Because, as we see, sh...t happens!

I have completed the OB update, but the authorization issue is still there. This is a real mess. I tried the stable version, but it has the same problem. ED, please communicate with us. We have a right to know what's happening!

I experienced the same when I tried to launch Open Beta MT. Authorization failed, and all my purchased modules were disabled. I could only fly the Tf-51 and the Su-25. A horror scenario. I suspect the failed authorization was related to the massive download activity for the new OB update. But there is no excuse for failure to allow off-line use of the software.

Why is that function not appropriate? It's exactly the way it should be. You could add the commands for ARM and OFF to the file "Throttle - HOTAS Warthog.lua" and use Button 24 and Button 24 OFF. It would then do exactly the same thing as the existing command "EAC 2-pos Switch : ARM<>OFF". Seems pointless.

The command "EAC 2-pos Switch : ARM<>OFF" is available for the Warthog throttle, and when you double-click that binding field I'm sure the assignment window will open. Cany ou confirm? The command is not available for the keyboard for a good reason: It's a command that works only with a maintained ON/OFF switch, just like the EAC on the Warthog throttle. Keyboards and the Warthog joystick don't have such switches. For the same reason it's not available with the CH-Pro pedals. The commands "EAC Arm" and "EAC Off" are not available for the Warthog throttle because that device has the maintained ON/OFF switch for the EAC function. Which command is available for which device is controlled by the files like "default.lua", "Throttle - HOTAS Warthog.lua", "Joystick - HOTAS Warthog.lua". The Warthog throttle and joystick are defined by their dedicated "....LUA" files. Game controllers that don't have a dedicated .LUA file can use all commands defined in the "default-lua" under "...\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick". The keyboard can only use the commands defined in the "defaultlua" under "...\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard".

File path is "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Ka-50_3\Input\ka-50_3\joystick"

I have added these lines to "default.lua": {action = device_commands.Button_1, cockpit_device_id = devices.HUD, name = _('HUD Brightness Axis')}, {action = device_commands.Button_1, cockpit_device_id = devices.HELMET, name = _('Helmet Device Brightness Axis')}, {action = device_commands.Button_2, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Brightness Axis')}, {action = device_commands.Button_3, cockpit_device_id = devices.SHKVAL, name = _('IT-23 Display Contrast Axis')}, {action = device_commands.Button_8, cockpit_device_id = devices.ABRIS, name = _('ABRIS Brightness Axis')}, {action = device_commands.Button_6, cockpit_device_id = devices.ABRIS, name = _('ABRIS Cursor Axis')}, Results: HUD Brightness: Works but uses only upper 50% of input range; set to INVERT HMD Brightness: Works fine; set to INVERT IT-23 Brightness: Works but uses only upper 50% of input range; set to INVERT IT-23 Contrast: Works fine ABRIS Brightness: Works but uses only upper 50% of input range; set to INVERT ABRIS Cursor Control : Seems to rotate the knob (Set to INVERT!), you have to test as I'm not familiar with that functionality As you see, some of the knobs use only 50% of the slider signal range. There is nothing I can do about that. The lines of code must be inserted near the end of the file, after this line: axisCommands = { but before these lines: }, }

That's definitively the wrong insert point. It must be inserted after these lines (beginning of the file) local cockpit = folder.."../../../Cockpit/Scripts/" dofile(cockpit.."devices.lua") dofile(cockpit.."command_defs.lua") local res = external_profile("Config/Input/Aircrafts/common_joystick_binding.lua") join(res.keyCommands,{ and before these lines (near the end of file): }) -- joystick axes join(res.axisCommands,{ I recommend to insert near the beginning of the file.

I just tried, and I do not see any change. It works for me, even though not always the first time. I use a VRP stick (Mongoos T-50) and I have no dead zone at all.

I didn't realize Game Avionics Mode was removed. I understand some people will not like that, but I belong to those who always considered it a nuisance. I see that the related "Easy" command bindings are gone as well, and that's really good news in my opinion because they caused confusion. Yes, learning DCS world is a big task and can seem overwhelming for beginners. But you don't need to understand everything immediately. Go step by step, with one aircraft, exercise the things you understand and make sure you have some fun. I'm flying in DCS World (starting with Lock On) since many years and I cannot pretend I know everything about it. So I'm still learning new things and that's wonderful. And I use the forum when I'm stuck with something. The forum is very helpful.

I have just tested, and it works fine. I tried with two kinds of bindings and both work. In order to understand what your problem is, you need to provide more detail. 1. What kind of throttle do you use? 2. if it's not the TM Warthog throttle, does it have a built-in switch that makes or breaks contact when you move to STOP? 3. Which bindings did you use? Note: depending on which bindings you use, you may have to move the throttle to the STOP position at mission start before it can "see" the move to IDLE. Edit: I went through a complete cold start to confirm that the throttle works as expected. I use the TM Warthog throttle, and I have bound the command "Throttle - Idle/Stop (hold)" to the detent switch of the right throttle lever which is JOY_BTN29.

You may want to go through the flight manual. You'll probably find the answer there.

Anton and Dora have the same commands for flaps. If you have a Thrustmaster Warthog throttle you should see the commands "Toggle Flaps Up" and "Toggle Flaps Dn", and you should bind them to the "Up" and "Dn" positions of the 3-position flap switch. These commands are defined in the file "Throttle - HOTAS Warthog.lua". If you have a Thrustmaster Warthog throttle and you don't see these two commands then that file is probably corrupted and you should run a Repair. If you don't have a Thrustmaster Warthog throttle you will only have the commands "Flaps Up", "Flaps Take Off" and "Flaps Landing" which must be bound to 3 buttons. Alternatively, you could add the two commands "Toggle Flaps Up" and "Toggle Flaps Dn" to the file "default.lua".