LeCuvier

Yes, and as I wrote in my post above you should make the same changes in both "default.lua" files to avoid duplicated orange lines.

@Funflite: I suspect you copied & pasted the last 2 lines of code from my post. I just see that I lost some characters when I copied & pasted from my file to the forum. And if you pasted that into your file that would have corrupted it. Here are the full lines: { pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.1, name = _('PITCH TRIM Wheel - NOSE UP'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, { pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.1, name = _('PITCH TRIM Wheel - NOSE DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, Anyway, as I said, you should simply overwrite the values in the original lines. If you prefer to copy & paste the modified lines, you must previously either delete the original lines, or inactivate them by inserting two hyphens ("--") at the beginning of the lines. Also, don't use something like Word. Use Notepad++ or equivalent! And, I apologize for my negligence.

The management of key bindings is certainly not a discipline where ED excels. I would go as far as calling it a mess. I would gladly spend some unpaid time to help them clean it up. But ED is not even good at picking up the many improvements some of us have posted. I have added bindings to every module I own, and I have optimized many settings like trim values etc that change too fast. I therefore have to use OvGME to back my changes out before, and back in after an update. With OvGME the task becomes quite manageable for me. But for the newbies that's an additional complexity most of them would rather avoid.

I don't know what you did. If you had simply overwritten the original values with smaller values, this kind of problem would never happen.

This kind of mods passes IC. No need to re-bind anything except the commands you have just modded.

In the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" , look for these lines below "-- Manual Trim Panel": {pressed = control_commands.RollTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.3, name = _('ROLL TRIM Wheel - L WING DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.RollTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.3, name = _('ROLL TRIM Wheel - R WING DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.3, name = _('PITCH TRIM Wheel - NOSE UP'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.3, name = _('PITCH TRIM Wheel - NOSE DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.YawTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.3, name = _('YAW TRIM Knob - L/CCW'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.YawTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.3, name = _('YAW TRIM Knob - R/CW'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, The original lines have lots of tabs after the "{" which I removed as they have no function and take too much space. You can reduce the "value_pressed" parameters and that will make the trim value change more slowly. I only changed the pitch trim: {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.1, name = _('PITCH TRIM Wheel - NOSE UP'), category = {_('Left Console'), _('MANUAL TRIM Panel')}},-- modified value_pressed from 0.3 to 0.1 {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.1, name = _('PITCH TRIM Wheel - NOSE DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}},-- modified value_pressed from 0.3 to 0.1 You obviously have to bind your POV hat to the modified commands. Personally, I use the "normal" trim commands for aileron and rudder (like "TRIM Button - LEFT WING DOWN") as we have the luxury of two sets of trim commands (not counting the axis commands). Notes: 1. you need to make a backup copy of the modified file as updates and restores will restore the original file. 2. you should make the same change to the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard" in order to avoid getting duplicated orange lines in Options/Controls.

Yes, there is - if you are willing to do a little edit of the "default.lua". In my experience it was mostly the pitch trim that was too "fast" and I adjusted that down.

@FlyingTaco21: No , this is not related to the mixup in the control names, and I can bind all 3 trims to my POV hat. If you cannot see any joystick bindings, that looks as if your "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\MosquitoFBMkVI\Input\MosquitoFBMkVI\joystick" were missing or corrupt. If so, you should execute the Repair.

This is reported. See this post: https://forums.eagle.ru/topic/287395-control-binding-localization-broken-in-most-wwii-aircraft-278-open-beta/#elControls_4830147_menu

The bug is acknowledged by the ED team. Concerns all WW II aircraft except the Mustang, plus the Yak52. Note: it does not make you lose existing bindings, but obviously makes it hard to find the right lines for new bindings.

Several WW II aircraft that use localization files show the internal "names" from "default.lua" instead of the localized names users are accustomed to. In many cases the user will be unable to find the command he wants to bind, especially since many of the internal names seem to refer to other aircraft. This is extremely confusing and creates the impression that the functionality is completely broken (which is not true). I would consider the issue as severe as it makes it nearly impossible to find the right bindings. Existing bindings seem unaffected though. I found the issue in the following moules (all Sim; I did not check "Easy"): Bf-109K-4 FW-190 A-8 FW-190 D-9 Mosquito FB Mk.VI P-47D Spitfire LF Mk IX The Mustang seems unaffected. I would appreciate moderator acknowledgement!

The command names you see in Options/Controls are the internal "names" from the file "default.lua". The Mosquito and some other aircrafts have dictionary tables for the different localization languages and these tables "translate" the internal name to what you normally see in Options/Controls. Something in this localization mechanism is broken. I see the same issue on my installation. The fact that the internal names show "Spitfire", Yak-52" etc. is probably due to sharing code with other modules and thus nothing unusual This is clearly a bug that should have high priority!

Nice discussion, but I would still like to see the VSI. Hopefully some good soul will create a gauge in Helios. I could also do with a bomb panel without the reflections on its cover. I cannot see anything on that panel.

I updated to 2.7.8 yesterday, and the takeoff assistance for the Bf-109 is still at 0, as it was before the update..

Yesterday's update concerned only Open Beta. Open Beta is what the name says: a Beta version which is by definition for user testing of new or changed functionality, and therefore has a probability that these kinds of glitches will happen. You reported it and that's good. It would be even better without statements like "STOP MUCKING ..." which are generally not helpful.

This is a sim, not an arcade game. And the gunsight did block the view of the VSI in reality. The cockpit of this aircraft was totally totally un-ergonomic and the sim replicates that. I hate it too, but I accept its realism. After a few missions in this monster I love to fly a FW-190 though. The request of the OP might make sense for game view; but certainly not for the sim.

confirm, that's the one. One of many examples of inconsistent use of vocabulary. In the cockpit it shows as "Jettison Fuselage Store" but in the control bindings you have to look for "Bomb Emergency Release". It could be so easy if ED established a dictionary that lists the terms to be used by developers (and localizers). But that's probably not a recognized problem.

For most aircrafts I use my TM WH grip in a VRP Base, plus the MfG pedals/wheelbrakes. For the Mosquito, Spit and MiG-21 however, steering on the ground is totally different and quite difficult with these controls. So when I fly any of these birds I use the VRP grip which has an analog lever for use with the Wheelbrake axis. That's the only one that works for me.

I find the "Gunsight Base..." commands too fast as well. Note This is for use with pushbuttons. If somebody uses a rotary encoder it's probably good. Unfortunately I have only 2 of those. This applies to other settings as well. It would probably be a good idea to have two pairs for these kinds of commands: One for "normal" pushbuttons plus on for rotary encoders.

There is a tutorial document. I'm not smart enough to teach LUA editing by video

This link points to a thread which contains a "how to" document for editing the related .lua files, plus commands for 2- and 3-position switches for the Hornet (incl. Fuel Dump switch) and other aircraft: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

Unfortunately, a method that works in one module doesn't necessarily work in another. Different developers have different handwriting, and that's especially true when the developer is from another organization as in this case. I have some old F-14 files from the trial pase, but could not find the object in "clickabledata.lua" that relates to this command. If you can find it, try to find the "Gain" paramter and reduce it. If the command is too "fast" for pushbuttons it might be just right for a rotary encoder which generates sequences of very short pulses.

Rotary encoders produce very short-duration contact closures and therefore produce very slow movement if you use them with commands intended for pushbuttons. In some cases I have been able to change the response "speed" by increasing or decreasing the gain of the related object in "clickabledata.lua", but that did not work in this case because the command in "default.lua" uses a different button number, so there is no related object.

What @MAXsenna describes works with a 3-position switch ON1-OFF-ON2 with 3 stable positions. You bind ON1 to "Toggle Flaps Up" and ON2 to "Toggle Flaps Dn". When the switch is in the middle position the flaps move to take-off position. So in essence you get 3 commands with only 2 inputs. That method is used quite frequently in DCS World. @ex81 describes the use of 2 momentary pushbuttons bound to "Flaps Up" and "Flaps Down". Both methods make efficient use of our pushbuttons and switches. One could easily modify the "default.lua" to create bindings for 3 pushbuttons, each driving the flaps to one of the 3 positions "Up", "MVR" and "Dn" respectively. But that would find little use since very few of us have spare switches, especially for more modern aircrafts.

I confirm the bug reported by @Slice313. It's easy to fix and in the interim (which might be long) we can easily fix it ourselves. Here is the culprit: In the file "default.lua", these are the 4 lines for the absolute positions of the valve selector: {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.0, name = _('Fuel Selector Valve OFF'), category = _('Fuel Control')}, {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.1, name = _('Fuel Selector Valve AFT Tank Closed'), category = _('Fuel Control')}, {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.3, name = _('Fuel Selector Valve FWD Tank Closed'), category = _('Fuel Control')}, {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.2, name = _('Fuel Selector Valve Open'), category = _('Fuel Control')}, It's almost obvious when you look at the "value_down" parameter values, that the values for "Forward Tank Closed" and "Open" are swapped. When we look at the same lines in the file "Throttle - HOTAS Warthog.lua" we see the correct sequence: {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.0, name = _('Fuel Selector Valve OFF'), category = _('Fuel Control')}, {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.1, name = _('Fuel Selector Valve AFT Tank Closed'), category = _('Fuel Control')}, {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.2, name = _('Fuel Selector Valve FWD Tank Closed'), category = _('Fuel Control')}, {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.3, name = _('Fuel Selector Valve Open'), category = _('Fuel Control')}, And in fact, the bindings in that file work correctly. We can easily fix the file "default.lua" by correcting the values in the 3rd and 4th line so they look like this: {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.2, name = _('Fuel Selector Valve FWD Tank Closed'), category = _('Fuel Control')}, {down = device_commands.Button_1, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 0.3, name = _('Fuel Selector Valve Open'), category = _('Fuel Control')}, @BIGNEWY: I endorse the request by @Slice313 to report this as a bug. I see an additional issue here: The 3rd and 4th line in "default.lua" and "Throttle - HOTAS Warthog.lua" resp. have identical names but different values. They should be displayed (in Options/Controls) as duplicated orange lines. Why is this integrity checking not working here?