LeCuvier

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.

You can wait for ED, or add the command(s) yourself to the file "default.lua" in the folder "...\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard". As a minimum, you need this line to switch the HMCS power ON: {down = 3001, cockpit_device_id = 75, value_down = 1.0, name = _('HMCS Power ON'), category = _('HMCS Power')}, For the OFF command you need to add this line: {down = 3001, cockpit_device_id = 75, value_down = 0.0, name = _('HMCS Power OFF'), category = _('HMCS Power')}, For a tutorial about editing these files go here: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#elControls_4646929_menu

We can take it for granted that the CB's could be manually popped. Whether that was done by pulling or by pushing the button in none of us knows and speculating does not get us anywhere. That level of detail could even vary in real life and it doesn't really matter as far as I'm concerned. If they can be manually popped then there is nothing (except orders) that would stop the pilot from doing that.

There are many reasons for wanting to pop one or several CB's mostly by the ground crew of course. But if the ground crew could pop them as you say, how do you prevent the pilot from doing the same? And why would the airforce want to prevent the pilot from isolating a possibly damaged part of the electrical system?

P-47D key binds: {down = device_commands.Button_35, up = device_commands.Button_35, cockpit_device_id = devices.CONTROLS, value_down = -1.0, value_up = 1.0, name = _('Undercarriage 2-Pos UP/DOWN'), category = {_('Systems'), _('Hydraulic system')}}, {down = device_commands.Button_39, up = device_commands.Button_39, cockpit_device_id = devices.CONTROLS, value_down = 1.0, value_up = 0.0, name = _('Compressibilty Recovery Flaps 2-Pos EXTD/RETR'), category = {_('Flight Control'), _('Systems')}}, {down = device_commands.Button_26, up = device_commands.Button_26, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 1.0, value_up = 0.0, name = _('Pitot Heat 2-Pos ON/OFF'), category = {_('Main Switch Box'), _('Systems')}}, {down = device_commands.Button_32, up = device_commands.Button_32, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 1.0, value_up = 0.0, name = _('Battery Switch 2-Pos ON/OFF'), category = {_('Front Dash'), _('Systems')}}, {down = device_commands.Button_24, up = device_commands.Button_24, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 1.0, value_up = 0.0, name = _('Generator Switch 2-Pos ON/OFF'), category = {_('Main Switch Box')}}, {down = device_commands.Button_19, up = device_commands.Button_19, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 0.0, value_up = 1.0, name = _('Gunsight fixed ring 2-Pos ON/OFF'), category = _('K-14 gunsight')}, {down = device_commands.Button_28, up = device_commands.Button_28, cockpit_device_id = devices.ENGINE_CONTROLS, value_down = 0.3, value_up = 0.0, name = _('Magnetos 2-Pos BOTH/OFF'), category = {_('Front Dash'), _('Engine Controls')}}, {down = device_commands.Button_28, up = device_commands.Button_28, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 1.0, value_up = 0.0, name = _('Oil Dilution Switch 2-Pos ON/OFF'), category = {_('Main Switch Box'), _('Engine Controls')}}, {down = device_commands.Button_7, up = device_commands.Button_7, cockpit_device_id = devices.WEAPONS, value_down = -1.0, value_up = 0.0, name = _('Gun Safety 2-Pos FIRE/SAFE'), category = _('Weapons')}, -- 2-position commands combined with cover Open/Closed {down = device_commands.Button_3, up = device_commands.Button_3, pressed = device_commands.Button_7, cockpit_device_id = devices.WEAPONS, value_down = 1.0, value_pressed = -1.0 , value_up = 0.0, name = _('Gun Safety 2-Pos and Cover'), category = _('Weapons')}, {down = device_commands.Button_36, up = device_commands.Button_36, pressed = device_commands.Button_39, cockpit_device_id = devices.CONTROLS, value_down = 1.0, value_pressed = 1.0, value_up = 0.0 , name = _('Compressibilty Recovery Flaps 2-Pos and Cover'), category = {_('Flight Control'), _('Systems')}}, {down = device_commands.Button_11, up = device_commands.Button_11, pressed = device_commands.Button_13, cockpit_device_id = devices.WEAPONS, value_down = 1.0, value_up = 0.0, value_pressed = 1.0, name = _('Left Wing Bomb Arm & Cover'), category = {_('Weapons'), _('Input.Generic.drop_ordnance_arming_panel')}}, {down = device_commands.Button_15, up = device_commands.Button_15, pressed = device_commands.Button_17, cockpit_device_id = devices.WEAPONS, value_down = 1.0, value_up = 0.0, value_pressed = 1.0, name = _('Right Wing Bomb Arm & Cover'), category = {_('Weapons'), _('Input.Generic.drop_ordnance_arming_panel')}}, {down = device_commands.Button_19, up = device_commands.Button_19, pressed = device_commands.Button_21, cockpit_device_id = devices.WEAPONS, value_down = 1.0, value_up = 0.0, value_pressed = 1.0, name = _('Belly Bomb Arm & Cover'), category = {_('Weapons'), _('Input.Generic.drop_ordnance_arming_panel')}}, -- Gun circuit breakers {down = device_commands.Button_51, up = device_commands.Button_51, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 1.0, value_up = 0.0, name = _('CB LH Inboard Guns 2-Pos ON/OFF'), category = {_('Main Switch Box')}}, {down = device_commands.Button_55, up = device_commands.Button_55, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 1.0, value_up = 0.0, name = _('CB RH Inboard Guns 2-Pos ON/OFF'), category = {_('Main Switch Box')}}, {down = device_commands.Button_51, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 0.0, name = _('CB LH Inboard Guns OFF'), category = {_('Main Switch Box')}}, {down = device_commands.Button_55, cockpit_device_id = devices.MAIN_SWITCH_BOX, value_down = 0.0, name = _('CB RH Inboard Guns OFF'), category = {_('Main Switch Box')}},

@Barrett_g: Remember that, when you do an update or repair, your modified file will be overwritten with the stock file. You need to have a way to back up and restore your modification. I have modifications in all my modules and use OvGME to manage this quite easily. You may be interested in the tutorial I've posted here: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#elControls_4646929_menu PS: this thread also has collections of added lines for various aircraft, incl. the Jug.