LeCuvier

@jackd I don't see any track in your posts. Please post a track so we can see what you are actually doing! Also, the "gun bars" are just ammo counters. Even after setting them alll down to zero I can still fire all guns. They have nothing to do with your ability to fire the guns.

What are you talking about? There is nothing wrong with the weapons. If you need help with something, be specific!

They are under "DRIVE:\Eagle Dynamics\DCS World\CoreMods\aircraft\FA-18C\UnitPayloads". Unfortunately there are two and I don't know which one you'd need to edit. But if you delete payloads from the file, they will pop up again after an update I suspect. So you need to backup your modified file (or use OvGME). PS: The payloads created by the user are under "C:\Users\USERNAME\Saved Games\DCS\MissionEditor\UnitPayloads". There is no equivalent in the game folder structure.

@MarcT-NL I experimented with such a setting when I started flying the Mossie. Early on, when the mission started in the air, the trim axes were badly off and I had to spend too much time trimming before I could engage in action. I came up with a custom command (with a bit of LUA editing) that set all 3 trim axes to reasonable values (not neutral) with a single button depress. The starting trim settings are now improved so this issue went away. Now that solution could be used to set all 3 trim axes' values = 0 (= neutral). I just tried that, and when I push the button the Mossie quickly goes into a steep climb. Not good! The following LUA line (added into the "default.lua") creates a new command "Trim Preset Airborne". It sets the 3 trim axes to reasonable in-flight values for a loadout without bombs: {cockpit_device_id = devices.CONTROLS, pressed = device_commands.Button_17, down = device_commands.Button_54, up = device_commands.Button_52, value_pressed = 0.33, value_down = 0.18, value_up = -0.1, name = _("Trim Preset Airborne"), category = _("Flight Control")}, The line contains 3 value statements. If value = 0 Then axis = Neutral. Value > 0 --> Turn clockwise. Value < 0 --> turn counter-clockwise. value_pressed sets the Tail Trim (elevator); Value > 0 --> Turn clockwise value_down sets Rudder Trim ; Value > 0 --> Turn clockwise value_up sets Aileron Trim ; Value > 0 --> Turn counter-clockwise In my opinion, such a command is more helpful then setting all to Neutral.

I confirm, the undercarriage does not "drop" when you activate the "Notzug" lever. I tried both with a bound pushbutton and by mouse-clicking in the sim cockpit. But I think you will have to provide a track for the bug to be considered.

The engine is just fine here. When I engage into a turning fight, it runs at full power with MW-50 for long periods of time and it does not die on me.

When I replay your track I see the rudder flapping. But when I take control, the rudder is steady and controllable. Therefore, it's not a problem of the Bf-109 module. My conclusion is that your rudder somehow gets erratic control inputs. You say that the rudder works fine in all other modules, therefore there must be a problem in your control settings for the Bf-109. If you have any mod related to the Bf-109, I recommend you verify that it's not causing the problem, by disabling it.

ED, unlike Heatblur, has rarely ever reacted to this kind of requests. That's my experience since I bought the Dora license in 2014. I then learned to edit the "default.lua" files. That was cumbersome early on as I had to restore my additions after every update. Then I installed JvGME and then OvGME, and that made the handling much easier. But it required using "frozen" files which over time started to miss updates. Finally now (some time ago actually), @Quaggles developed the command injector which I have adopted after some hesitation. Now, the added LUA lines go into "default.lua" files under the "Saved Games\" folder structure and they are no longer affected by updates. Now, only one LUA file ("Data.lua" under "DRIVE:\Eagle Dynamics\DCS World\Scripts\Input") is modified in the Games folder structure, and that's easily managed with OvGME. I have lots of modules with their LUA additions and it does not look like a "workaround" for me. I wouldn't want to fly DCS World without these adds. And I'm grateful that the software is open for making such additions. Because no software will ever make everybody happy. My only request to ED would be to make the Command Injector part of the stock software.

Thanks for enriching my English vocabulary! (I'm German) And good luck!

What does this mean: "but I neednulled to change the values "? In the video I see the switch flipping around, but I never see the cover moving. You have bound switches to two different versions of "coolant close". Why? You are apparently using a 2-position switch for coolent OPEN/CLOSE, and using the _OFF event which is not reliable. I would have thought that you used a 3-position switch for Open/Auto/Close. Actually, in order to understand what's going on I would need to know what kind of switches you use. Anyway the whole thing is tricky. In the real-life cockpit the switch and cover are obviously electro/mechanically connected to force the switch to Auto when the cover is closed. If you don't have the same interlocks in your sim cockpit, the view of the virtual cockpit might sometimes not match what your sim cockpit shows. It might therefore be easier to set "Automatic" before closing the cover.

Can you try these lines for the Coolant switch? If that works we can create the same function for the Oil switch. It works here. {down = device_commands.Button_1, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 0.1, name = _('Radiator Coolant Switch CLOSE'), category = _('Radiator Air Controls')}, {down = device_commands.Button_1, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 0.3, name = _('Radiator Coolant Switch OPEN'), category = _('Radiator Air Controls')}, Good luck!

Try these 2-position commands for the two radiator switch covers! {down = device_commands.Button_3, up = device_commands.Button_3, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 1.0, value_up = 0.0, name = _('Radiator Coolant Cover 2-Pos OPEN/CLOSE'), category = _('Radiator Air Controls')}, {down = device_commands.Button_4, up = device_commands.Button_4, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 1.0, value_up = 0.0, name = _('Radiator Oil Cover 2-Pos OPEN/CLOSE'), category = _('Radiator Air Controls')}, Try this for the supercharger switch cover: {down = device_commands.Button_2, up = device_commands.Button_2, cockpit_device_id = devices.ENGINE_CONTROL_PANEL, value_down = 1.0, value_up = 0.0, name = _('Supercharger Switch Cover 2-Pos OPEN/CLOSE'), category = _('Engine Control Panel')},

You find them in the file "clickable_data.lua" under \Cockpit\Scripts\ in the game folder structure. You should really read the reference document!

@Munkwolf has created a community project at this site: https://github.com/Munkwolf/dcs-community-keybinds I would expect that most everything you need is in the P-51 file. Note: these files are designed for use with the "Command Injector" by @Quaggles. See this site: https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-v109-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/#comment-4651461 These files go into a new folder under "Saved Games". Here are a few LUA lines I created myself: {down = device_commands.Button_11, up = device_commands.Button_11, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 0.0, value_up = 0.1, name = _('Mixture 2-Pos RUN/CUT-OFF'), category = _('Flight Control')}, {down = device_commands.Button_12, up = device_commands.Button_12, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, value_up = 0.0, name = _('Battery 2-Pos ON/OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_13, up = device_commands.Button_13, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, value_up = 0.0, name = _('Generator 2-Pos ON/OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_14, up = device_commands.Button_14, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, value_up = 0.0, name = _('Pitot heat 2-Pos ON/OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_12, up = device_commands.Button_12, cockpit_device_id = devices.ENGINE_CONTROL_PANEL, value_down = 1.0, value_up = 0.0, name = _('Fuel Booster 2-Pos ON/OFF'), category = _('Engine Control Panel')}, {down = device_commands.Button_2, up = device_commands.Button_2, cockpit_device_id = devices.FRONT_SWITCH_BOX, value_down = 0.3, value_up = 0.0, name = _('Ignition switch 2-Pos. BOTH/OFF'), category = _('Front Switch Box')}, {down = device_commands.Button_5, up = device_commands.Button_5, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 1.0, value_up = 0.0, name = _('Fuel shut-off valve 2-Pos ON/OFF'), category = _('Fuel Control')}, {down = device_commands.Button_26, up = device_commands.Button_26, cockpit_device_id = devices.RIGHT_SWITCH_PANEL, value_down = 1.0, value_up = 0.0, name = _('Gun heat 2-Pos ON/OFF'), category = _('Right Switch Panel')}, {down = device_commands.Button_15, up = device_commands.Button_15, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 1.0,value_up = 0.0, name = _('Gunsight gyromotor power 2-Pos ON/OFF'), category = _('K-14 gunsight')}, {down = device_commands.Button_6, up = device_commands.Button_6, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 1.0,value_up = 0.0, name = _('Gunsight Reticle Mask 2-Pos ON/OFF'), category = _('K-14 gunsight')}, {down = device_commands.Button_3, up = device_commands.Button_3, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0,value_up = 0.0, name = _('Landing Gear 2-Pos UP/DOWN'), category = _('Systems')}, {down = device_commands.Button_1, up = device_commands.Button_1, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, value_up = 0.8, name = _('Flaps FLIGHT/10° OUT'), category = _('Flight Control')}, {down = device_commands.Button_1, up = device_commands.Button_1, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 0.0, value_up = 0.6, name = _('Flaps LAND/20° OUT'), category = _('Flight Control')},

you are out of luck here, because the Hornet's antenna elevation axis does not set an elevation value. Instead, it sets the speed at which the antenna will go up or down. There has been quite a bit of discontent about this, but apparently that's how the real thing works.

Yes, if you are willing to add this line to the file "default.lua": {down = hotas_commands.THROTTLE_ANT_ELEV_AXIS, value_down = 0.0, cockpit_device_id = devices.HOTAS, name = _('ANT ELEV Knob - Center'), category = {_('Throttle Grip'), _('HOTAS')}}, The zero value centers the axis vertically. I simply copied the line for the axis, replaced the "action" with a "down" expression and added the "value_down" expression. You can do this with all axis commands in all modules I have tried. You have to find the right value by trial and error as the axis range definitions vary.

In the file "K:\Eagle Dynamics\DCS World\Mods\aircraft\F-4E\Input\F-4E-Pilot\keyboard\default.lua", local function "binds". Through some magic which I cannot figure out, the commands defined in "...\keyboard\default.lua" are made available to all game controllers. This module is really different!

F-4E Phantom issue: I was trying to make WSO commands (e.g. Radar Mode) available for the pilot. So I added "...\Saved Games\DCS\InputCommands\F-4E-Pilot\joystick" to the "InputCommands" folder with files "default.lua" and "Throttle - HOTAS Warthog.lua", and added this line of code into the skeleton structure of both: knob('Radar Mode', { 'BST', 'Radar', 'Map', 'Air-Ground', 'Beacon', 'TV' }, nil, device_commands.RADAR_Mode_Knob_RIO, device_commands.RADAR_Mode_Knob_RIO_INC_DEC, device_commands.RADAR_Mode_Knob_RIO_NEXT, device_commands.RADAR_Mode_Knob_RIO_AXIS, bind_templates.radar_panel()), Unfortunately, the command "Radar Mode" is still not available for the pilot. When I added the LUA line directly into the files in the game folder structure, the command became available for the pilot. So there is nothing wrong with the LUA line. I tried to find inspiration in @Munkwolf's community project, but did not see anything for the F-4E. Is there a structural problem with that aircraft module? Edit: I corrected the folder structure under "InputCommands" to "...\Saved Games\DCS\InputCommands\F-4E\F-4E-Pilot\joystick" but that did not solve the issue.

I belong to the people who want to get rid of all reflections for myself . That's because... 1. I'm almost 80 and my eyes are not what they used to be. So everything that reduces visibility puts extra strain on my eyes and brain, and reduces the fun. 2. These effects require processing power, and I'm not willing to pay for ever more hardware performance and the questionable benefit of seeing less clearly. I'm happy if I can eliminate these disturbances for myself via some setting, and let other people enjoy the realism of reflections.

There is no point trying to manage the custom Input files with OvGME because they are under "Saved Games" and updates don't affect them. The only file that needs to be managed with OvGME is the "Data.lua".

I have checked this on my rig, and the "invert" setting certainly works. You had already posted the same subject under a different tile on 27-May. Have you verified that no other game controller is bound to the rudder axis? DCS World unfortunately creates a lot of duplicated bindings when you add a game controller. You need to remove all unwanted bindings.

I suspect that you might be mistaken. FOLD/HOLD combined with SPREAD/HOLD are defined for a maintained 3-position switch. The sequence Pull/Fold you describe like the opposite Spread/Stow was not originally available from ED (and I doubt that ED ever added it). I therefore provide two mods: "Wing Fold Control PULL/FOLD" and "Wing Fold Control SPREAD/STOW" via thwo lines of LUA code: {down = ctrl_commands.WingFoldPull, pressed = ctrl_commands.WingFoldSelect, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_pressed = -1.0, name = _('Wing Fold Control PULL-FOLD'), category = {_('Right Vertical Panel')}}, {down = ctrl_commands.WingFoldSelect, up = ctrl_commands.WingFoldPull, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Wing Fold Control SPREAD-STOW'), category = {_('Right Vertical Panel')}}, Could it be that you had been using this mod (or an equivalent from Munkwolf), and that you lost it in one of the updates?

You don't need to understand. But with a computer screen trying to show "the world" in a 2-dimensional display it's hard enough for most of us without these eyesores. .

I'll be happy to tune the reflections all the way off. I certainly don't want to buy a new computer just to get reflections that make it more difficult to spot my targets.

I tested and found that it worked.