LeCuvier

@impalor 1. your files seem ok. 2. The red dots don't tell you where the conflict is, only that there is one. Did you look into UI Layer? 3. I'm getting desperate, and since I cannot look into your PC my possibilities are extremely limited. I would try this: Since the issue happens when the 3 default assignments come back, I would get rid of the defaults. This can be done by removing the "combos..." bit from the code. Here are the 3 original related lines from "common_keyboard_binding.lua": {combos = {{key = ']'}}, down = 3001, cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard Next Page'), category = _('Kneeboard')}, {combos = {{key = '['}}, down = 3002, cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard Previous Page'), category = _('Kneeboard')}, {combos = {{key = 'K', reformers = {'RCtrl'}}}, down = 3003, cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard current position mark point'), category = _('Kneeboard')}, After removing the "combos" part they look like this: {down = 3001, cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard Next Page'), category = _('Kneeboard')}, {down = 3002, cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard Previous Page'), category = _('Kneeboard')}, {down = 3003, cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard current position mark point'), category = _('Kneeboard')}, This simple surgery removes the defaults so the game cannot revert to them. Do you want to try? If you don't feel confident with lua editing I can edit the file for you. I don't know what else could be done to fix it. The problem doesn't occur here, but I don't have VR so it's not the same environment.

@impalor: 1. You have caused some of the confusion by saying that you use custom bindings. That led people including myself to believe that you had modified the "default.lua". You are not using custom bindings. You are using stock bindings, and you have bound them to non-default key combinations. 2. You have not indicated which version you are using. I see orange duplicated lines too, but a significantly different set. I'm using Open beta latest update. From what I see on your initial screen copy I suspect that you might be using stable release. I loaded stable, and that looks more similar to your picture. But not the same. 3. Your initial screen copy shows 3 red dots with "!" in them. These indicate unmistakably that you have binding conflicts. From my experience, these conflicts are with line in "UI Layer". You need to find and resolve these conflicts or you will get nowhere. UI Layer bindings override bindings anywhere else. In Controls/Options, select "UI Layer" instead of M-2000 to check! @Rudel_chw I have made sure I have current files for the Mirage and tried the Options/Controls, and YES I see the duplicated orange lines with all the "Kneeboard Jump To Shortcut..." commands. I'm amazed they don't show duplicated on your screen. I have never bound these so it's nothing to do with old bindings. So I went to the source of the issue. The kneeboard bindings are all defined in the files "common_joystick_binding.lua" and "common_keyboard_binding.lua" in the folder "...\DCS World OpenBeta\Config\Input\Aircrafts". And when I open and compare these two files with Notepad++ I see immediately what causes the duplicated orange lines: The lines in "common_joystick_binding.lua" look like this, {down = 3006, cockpit_device_id = kneeboard_id, value_down = 0, name = _('Kneeboard Jump To Shortcut 1'), category = _('Kneeboard')}, and the ones in "common_keyboard_binding.lua" look like this: {down = iCommandPlaneKneeboardJumpBookmark, value_down = 0, name = _('Kneeboard Jump To Shortcut 1'), category = _('Kneeboard')}, I've taken the padding out to make them more readable. The two sets of lines have identical names but different (albeit probably equivalent) code, and that causes them to be displayed in separate lines and in orange. I show what it looks like in the attachment. I'm puzzled why you don't see this.

This module shows two sets of duplicated lines in orange font as visible in the attached screen capture. They are caused by lines of code with same "names" having different content between "Throttle - HOTAS Warthog.lua" and "default.lua". Lines in "Throttle - HOTAS Warthog.lua": {pressed = device_commands.Button_16, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 0.7, name = _('EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CW/Increase'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_16, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -0.7, name = _('EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CCW/Decrease'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_18, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 1.0, name = _('EZ42 Gunsight Altitude Aiming Correction Adjusting Knob I - CW/Increase'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_18, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -1.0, name = _('EZ42 Gunsight Altitude Aiming Correction Adjusting Knob I - CCW/Decrease'), category = _('EZ42 Gunsight')}, Lines in "default.lua": {pressed = device_commands.Button_16, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 0.14, name = _('EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CW/Increase'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_16, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -0.14, name = _('EZ42 Gunsight Target Distance Control (Throttle Twist Grip) - CCW/Decrease'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_18, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = 0.2, name = _('EZ42 Gunsight Altitude Aiming Correction Adjusting Knob I - CW/Increase'), category = _('EZ42 Gunsight')}, {pressed = device_commands.Button_18, cockpit_device_id = devices.EZ42_GUNSIGHT, value_pressed = -0.2, name = _('EZ42 Gunsight Altitude Aiming Correction Adjusting Knob I - CCW/Decrease'), category = _('EZ42 Gunsight')}, The values in "value_pressed are 5 times higher when you bind the commands to buttons on the TM WH throttle and that makes them too "sensitive". The values for the throttle bindings should be the same as for all other controllers and the keyboard.

In the A-10C II I see only two command bindings duplicated/orange: "Right Engine Oper Ign / Norm" and "Left Engine Oper Ign / Norm". Both have the same slight issue. The first line is for the TM WH throttle and can only be selected for that controller. The 2nd line is for other controllers and keyboard, and cannot be selected for the TM WH throttle. The two lines have the same name, but different code in the related files ("Throttle - HOTAS Warthog.lua" and "default.lua"). Normally, lines of code with different code should have different names and since this rule is violated the lines display in orange. This causes no malfunction apart from the possible confusion. You could get rid of the orange by changing the name of the command in the file "Throttle - HOTAS Warthog.lua" but that's not worth the trouble. And the file would be restored to original each time you update or repair.

In which folder/file do you create your "custom blinds for kneeboard next and previous page"? The original commands are in "...\DCS World OpenBeta\Config\Input\Aircrafts\Common\keyboard\default.lua": {combos = {{key = ']'}} , down = 3001, cockpit_device_id = 100, value_down = 1.0, name = _('Kneeboard Next Page') , category = _('Kneeboard')}, {combos = {{key = '['}} , down = 3002, cockpit_device_id = 100, value_down = 1.0, name = _('Kneeboard Previous Page'), category = _('Kneeboard')}, And for what purpose do you create custom binds for these commands?

I agree it generally doesn't cause any malfunction, and therefore it's not a critical defect. But the orange color generally is meant to signal an issue and therefore it causes confusion and should be considered a bug. I'm referring to the frequent situation where the "default.lua" files under "\joystick" and under "\keyboard" have identical lines. Earlier versions of the software showed this as a single line in Options/Controls and in black. And somewhere around March 2019, ED made a change to the software which brought us to the current situation. And as it's low priority it might stay with us forever, unless a lucky software change brings the smarter logic back.

Seems that it has been deleted. I still have it because I use a modified file which was backed up and therefore not overwritten in the update. If you want to recover the command, you need to add this line: { down = iCommandGraphicsFrameRate, name = _('Frame rate counter - Service info'), category = _('General')}, into the file "default.lua" in the folder "...\DCS World OpenBeta\Config\Input\Aircrafts\Default\keyboard". Insert it in the block of lines under "-- Gameplay" using Notepad++. You should then be able to bind it to RCtrl + PAUSE.

You need to 1. make sure that the right folder is selected. The user interface is a bit weird. It does not pre-select the right folder for the aircraft you're working on. 2. select a file you want to overwrite with current profile data, or enter a new file name. And of course, the profile you save is for one controller at a time. As you say, separate files for throttle and stick.

I got engine failures without any battle damage. In the debrief I see a failure I've never seen before: "Erroneous ignition timing...". I cannot see the complete message as the display column is not wide enough and I cannot adjust it (why don't they make sure the columns are wide enough for all messages, resp. keep message length within column width?). After that message it displays "engine overheat" and then failure.

Just after mission start, before you begin the start-up sequence, move the throttle from IDLE to OFF to make sure the sim "knows" that it's OFF. Sounds ridiculous I know. Technical reason: the contact in the throttle lever closes when you move to the OFF position. It opens when you move to IDLE. The sim does not reliably detect the transition from closed to open if it has not seen a transition from open to closed before.

I have seen this many times, and it might be that I didn't push the hat correctly left or right. Either way, I now use the Slew Push for SOI left, and the Mic switch push for SOI right. That works every time.

The problem with the USB splitter is that it splits not only the data but also the available power. To avoid these problems you should always used powered USB hubs which provide the full USB power (0.5 A I believe) to each USB Out ports. The fact that you did not see these problems with the Hornet is pure coincidence.

The profile you save is for a single controller (per the column selected) and for a single aircraft. You can load any profile, but if the button numbering is not the same for the same function then you load a mess. I, for example have used a native VRP stick in the past, and now I use the TM-WH grip in the VRP base. The game still sees it as a VRP stick, but I had to re-bind all the buttons because their numbering is different.

In many situations a wing man keeps calling out threats or targets, or just repeats "Return to base" endlessly. If there are 50 ground targets, the wing man calls out every one and this goes on forever. In a mission just now a wing man managed to dig himself deep into the runway and kept yelling "Return to base" (actually it was "zurück zum Gartenzaun"). This is not only a big nuisance. Sometimes it's impossible to send a command to my flight members. We should have a command that allows us to silence the gabby wing man.

very interesting! Thanks for the info!

what is Stream Deck?

Yes. Scenario 1 = MW50 OFF

My stable version was still at 2.71.7139, and it behaved exactly as the current OB 2.7.3. So the behaviour in scenario 1. is not new. I'm not sure that the engine's behaviour in scenario 1. is wrong. The boost pressure does rise to 1.8, but: - I do not get any significant increase in indicated air speed; thus no gain in engine power. - the engine apparently runs very roughly, because the entire cockpit shakes. - the oil temperature increases. - the engine finally overheats and breaks down. In other words, you gain no power and if you persist in this mode you kill the engine. The only thing that seems odd to me is that the engine sound does not change between the two modes. I'm no engine expert but I would imagine that the engine would produce a rougher sound in mode 1.

That's (in my irrelevant opinion) not a valid reason for powering the HMCS down. If you want to declutter the screen use the command DMS Left Short to "hide" the DMCS. If you don't like to hold the DMS switch, you can add a keyboard command to that same binding (providing you can find a key that's not in use already).

This command is still [Num5] in my set-up, it has never changed. It is defined in the file "common_keyboard_binding.lua" in the folder "...\Config\Input\Aircrafts". Unless you have change the binding yourself I cannot imagine why it would be changed for you.

I agree the button commands for prop speed are too "fast" for precise control. Personally I use the axis command and that's fine. Out of curiosity, I changed the "gain" parameter for this command in "clickabledata.lua", in folder "...\Mods\aircraft\SpitfireLFMkIX\Cockpit\Scripts" from 0.1 to 0.01 and that made the lever movement with button commands more controllable. I tried 0.05 first, but that didn't feel much better for me. This is the original line before I changed it: elements["PROP"] = default_movable_axis(_("Cockpit.SpitfireLFMkIX.pitch"), devices.ENGINE_CONTROLS, device_commands.Button_6, 129, 0.0, 0.1, true, false) and this is the line after the change: elements["PROP"] = default_movable_axis(_("Cockpit.SpitfireLFMkIX.pitch"), devices.ENGINE_CONTROLS, device_commands.Button_6, 129, 0.0, 0.01, true, false) I have made a fair number of such changes because I've rarely or never seen ED making these "cosmetic" changes. The downside of editing these files is that they are overwritten with the stock files each time you do an update or repair. The modified files therefore need to be backed up. I use OvGME to handle that. PS: do not edit these files with programs like Word as these might insert unwanted formatting! The free Notepad++ works fine.

Yes, this was mis-spelled in the stock files as well some updates ago, and correct spelling would not have worked. The updated collection of added bindings is posted here: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#elControls_4691325_menu

When you start a mission in the air, the nose goes brutally down and left. You need to apply a lot of rudder -right and nose-up trim, plus a bit of aileron trim before you can fly her with any level of precision. In an instant action mission you may already be under fire before you are done trimming, and before you can make any adjustment to target wingspan and range, let alone worrying about engine settings. The P-47D should have at least approximately correct trim settings when the mission starts airborne.

I will try to concoct a mission with Hornets defending the islands against Chinese aggression. Hopefully we will get some Japanese WWII assets in due course.

I wanted to create a mission engaging Japanese fighter aircraft, but I could not see any in the dropdown. Would be nice to have at least the Zero fighters as AI available as bandits.