LeCuvier

That's weird! I do not see this behaviour at all. And I don't understand what "Rescan Devices" would do in this case. When I enter 'LCtrl' + 'D', my Phantom veers to the left. So it works as expected here. 1. I suppose you changed the diff.lua via the Options/Controls screen, correct? 2. can you show the Options/Controls with the wheelbrake lines? 3. Does the diff.lua still look like the screen copy in your post above? Note: changing the "default.lua" is not a lasting solution. It will be restored to the stock file content with every update or repair. Making a backup copy doesn't help as this module is in very early early access, and there will be changes + additions to this file which you will miss when you restore from your backup copy.

You are right indeed. But that's easy to fix. The expression "combo('D', 'LAlt')" is only a default binding. You can clear the default binding in Options/Controls and replace it with a unique one. I changed Wheel Brake (Left) to "[LCtrl] + D". This override is stored in the file "Keyboard.diff.lua" under "Saved Games" and it will be "respected" by the game software when you do an update or repair. Here is what the entry in "Keyboard.diff.lua" looks like: local diff = { ["keyDiffs"] = { ["dnilp2112u2112cdnilvdnilvp-1vu1"] = { ["added"] = { [1] = { ["key"] = "D", ["reformers"] = { [1] = "LCtrl", }, }, }, ["name"] = "Wheel Brake (Left)", ["removed"] = { [1] = { ["key"] = "D", ["reformers"] = { [1] = "LShift", }, }, }, }, }, } return diff It's the only keyboard binding I changed, that's why there is only this entry in the file.

I've bound the CCW and CW commands for the switch today (11-JUN-2024) and that seems to work. As of current version 2.9.5.55918 Edit: I searched for the Shrike Band Switch in "clickabledata.lua" and found this line: elements["Pilot_oil_press_switch02_help"] = default_2_position_tumb(_("Change Shrike Band"), devices.TODO, device_commands.BAND_SWITCH, cockpit_args.PILOT_TGT_MSL_BAND, pilot_only) -- TODO Not simulated Looks like this item is on the TO-Do list.

The wheel brake commands have been fixed in the last update, version 2.9.5.55918. The LUA lines for left and right wheel brakes are now { name = _('Wheel Brake (Left)'), combos = combo('D', 'LShift'), pressed = iCommandLeftWheelBrake, up = iCommandLeftWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } }, { name = _('Wheel Brake (Right)'), combos = combo('D', 'LAlt'), pressed = iCommandRightWheelBrake, up = iCommandRightWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } },

So far I have not found a way to customize command bindings in the F-4. It seems that Heatblur does things differently, so we need to rely on Heatblur to make changes.

gern geschehen!

I was surprised to find that there is a problem indeed when you use the SC250 bomb. You can only get the "Zünder 25C" fuse in ME, and you cannot obtain a short delay in ME that would prevent your fighter from being shredded in a low-level bombing attack. This same problem exists with the FW-190A8. When you use the SC500 bomb you can get a short delay that's ok tactically and keeps you safe. Again, that's true for the 3 German fighters. The best short delay is with the SC50, but that's not available with the Bf-109. The problem with the SC250 seems to be recent. I'm sure it was working ok in the past.

It's very easy to produce the desired bind by adding this line of code to "default.lua" under "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\F-15E\Input\F-15E\joystick" : {down = extlt_commands.anticoll_lt_sw, up = extlt_commands.anticoll_lt_sw, cockpit_device_id = devices.EXTLT, value_down = 1.0, value_up = 0.0, name = _('Anti-collision Lights 2-Pos. ON/OFF'), category = {_('Left Console'), _('Lights: Exterior')}}, Problem is, this file will be overwritten with original content if you do a repair or update. Best way to avoid that is to use the "Command Injector" developed by @Quaggles and put all additions into a "default.lua" file under "Saved Games".

@void68: I have looked at your two files. Findings: 1. I expected to look at "germanized" versions of "default.lua", but they are not. So apparently the localization is defined in a separate file. 2. Your keyboard file is the same as mine. 3. Your joystick file is very different. You (or someone else) have made additions to it, which probably do not cause your issue. But you are also missing a good number of lines which have probably been added to the stock files after you made the additions. It seems that you are using an older version of the file with your additions. Not good. There is also an invalid binding in the category "Special for joystick". My flie has this line: {down = gear_commands.ParkingSw_SPEC, up = gear_commands.ParkingSw_SPEC, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('ANTI-SKID Switch (special) - PARKING BRAKE/ANTI-SKID'), category = {_('Special For Joystick'), _('Left Auxiliary Console')}}, In your file, this line shows: Padding removed in both to facilitate reading. Both lines have the same name "ANTI-SKID Switch (special) - PARKING BRAKE/ANTI-SKID", but in your file they have the wrong command ID, which overlaps with a command in the other Anti-Sid switch bindings. While this seems related I cannot tell with certainty that this is causing your problem, but you could try what happens if you correct your line. At any rate, this violates the rule that you cannot have two different command definitions sharing the same name. Conclusion: The issue I noted under 3. is certainly suspicious but I'm not sure it causes your problem. The situation of an outdated file with additions and an invalid line of code makes it difficult to understand what's going on. While I cannot rule out that the issue comes from localization, that would not my primary suspect. Recommendations: 1. Take your additions out of the "default.lua" in the game folder and use them with the "Command Injector" by @Quaggles. There, the additions will be in a "default.lua" under "Saved Games", and you can let DCS World update all your game files. 2. As a first step, make a backup copy of your "default.lua" under "joystick" and let DCS World run a repair. Then check if your binding work fine. 3. If you don't want to go to the Command Injector, copy all your added lines into a holding file. Then, after a successful repair (or update), copy them "en bloc" into your "default.lua". This will make it easier to restore your additions after an update.

I'm sorry, you are right of course. Shame on me!

Should be no problem. He can re-name your .diff.lua file to match his device names. If he hasn't got a file for his device(s) he just needs to create one bind (could be a dummy) per device. That was nonsense.

ED have taken my money and they made a commitment to deliver the F-15E. As an early access version first, but evolving to the complete version. Any problem between ED and Razbam should not be my problem. If ED cannot resolve the problem in an acceptable way, then they should give me credit for the full amount I paid. With that credit I should be able to buy any one of the ED modules. I would probably use it to buy the F-4. Also, ED should communicate to their customer base. They are totally failing in that area, and they are doing a huge disservice to themselves. They are destroying customer confidence, and that can be deadly for any business. For the time being, I'm holding back on any futher purchases.

It certainly looks the same at the surface. You are using a "germanized" version, and so I cannot use the "compare" function in NotePad++. But I can take a look the hard way. If you post your two "default.lua" I will look at them.

@Nezih: I compared your files with mine. Results: Your "joystick" file is exactly the same as mine. Your "keyboard" file differs in 3 lines. The first 2 are added lines for the ejection seat safety lever bindings. They should be o.k., I suppose you added these? The 3rd one has an altered line for the parking brake which is apparently causing the issue. Here is your line: {down = gear_commands.AntiSkidSw_EXT, up = gear_commands.AntiSkidSw_EXT, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('ANTI-SKID Switch - PARKING BRAKE'), category = {_('Left Auxiliary Console')}}, Here is my corresponding line: {down = gear_commands.ParkingSw_EXT, up = gear_commands.ParkingSw_EXT, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('ANTI-SKID Switch - PARKING BRAKE'), category = {_('Left Auxiliary Console')}}, I removed the huge space in the beginning of both lines to make them more readable. I attach the "repaired" keyboard file. default - Keyboard.lua

I would rather suggest that you post your two "default.lua" files under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard" and "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" respectively. I would then be able to see which of the two files causes the problem.

I've seen this issue on several ED-developed modules.

I do not see this effect, but I didn't fly with a very low sun. Might also be a question of graphics settings. Anyway, I would much prefer if the mod could be put into "Saved Games". That would exclude IC risks, and it would be less or not at all affected by version changes.

As far as I can see these bindings are correct now. I bound buttons to the 4 bindings, and they all worked as expected. My "default.lua" is not modified.

There is a keyboard bind for "Warning Tone Silence Button". It has no default binding, so you need to find an unused key or key comination. Edit: "Q" and "J" seem to be unused, so you could bind the command to either one.

And which base?

@motoadve: You do not tell us which one of the VIRPIL sticks you have. Some of their sticks have a paddle/lever with an axis (plus a button), and some them have a paddle/lever with button only. As long as you don't share which model you have we really have no idea what the problem might be and how we can help you. Be specific please!

1. I have disabled the deadzone on my VRP stick, and I have no deadzone in the axis tuning for the FA-18C 2. I have no problem with AP/BALT. I adjust my flight path to level flight, which is easy on the Hornet, and engage AP/BALT. That does it. 3. However, I confirm the problem with AP/HDG. I had set the heading to 20 ° and engaged AP/HDG. The UFC shows HDG engaged, but the Hornet continues flying straight ahead. Only after I wiggled the stick a little bit, it turned to the 20 ° heading. I attach a track demonstrating the issue. @NineLine: Please report! FA-18C AP HDG Bug.trk

A "Global" curve definition, if it were possible, might not do you any good, because the response to stick inputs varies between airplanes.

If you don't have analog brake pedals that might be a totally different ballgame. I have no experience with that.

That's your subjective assessment. I find it much easier to taxi than the Spit or the Mosquito with their strange combined pedal & brake method. If I flew those aircraft frequently, I would probable find them just as easy to taxi.