LeCuvier

Read his second statement: "The engine starts and operates with both magnetos OFF".

Apparently not.

I've had the Dora since it became available, I have never had an issue with these two commands, and they are working now. I cannot imagine why these very straightforward commands wouldn't work for you. Are the keyboard commands Ctrl + G and LShift + G working? Edit: Obviously you cannot close the canopy when you have taken off with the canopy open and you have exceeded 350 km/h.

Very strange! But glad I could help.

Yes, still working for me.

@Laidback: Do you use a non-English version, and if "Yes", which language? I switched my stable version to German, and the "Hornet Ball" is still there (as "Hornet Ball" as I expected). Also, I found that when you change language it does not change the command names in "default.lua". The translations from English to target language are in the file "input.mo" under "...\DCS World\l10n\de\LC_MESSAGES". And, if there is no translation for a given command, then Options/Control will show the original English command name. For this reason, language localization is noat a very likely reason for losing a command. Except, the translator could enter something unrecognizable like "B l" or a space by accident. But then you should see a strange command name in Options/Controls when you select the appropriate category. Edit: so you should still find the line in "default.lua" by searching for "Hornet Ball", or just "Ball" with the option "whole words only" not ticked of course.

In the unmodified "default.lua" under "\joystick", if you open it with Notepad++, it's in line 877: { down = intercom_commands.MsgHornetBall_EXT, cockpit_device_id = devices.INTERCOM, value_down = 1.0, name = _('Hornet Ball'), category = _('Communications')}, In a non-English version, simply search for the string "intercom_commands.MsgHornetBall_EXT" and you should find it. If you cannot find it this way, the file misses a line.

I wonder where you are looking! The "Hornet Ball" command is available for binding to whatever you want, and I find it in the "default.lua" under joystick and keyboard, and in the equivalent file for the TM Warthog throttle.

Just to be clear: Gun sight range and span with 0.1 and -0.1 values works fine here. In order to exclude any effect from my mods, I took the original "default.lua" and, instead of modifying values I added these 4 slow commands: {pressed = device_commands.Button_8, cockpit_device_id = devices.WEAPONS, value_pressed = 0.1, name = _('Gun Sight Range Increase Slow'), category = _('Gunsight')}, {pressed = device_commands.Button_8, cockpit_device_id = devices.WEAPONS, value_pressed = -0.1, name = _('Gun Sight Range Decrease Slow'), category = _('Gunsight')}, {pressed = device_commands.Button_11, cockpit_device_id = devices.WEAPONS, value_pressed = 0.1, name = _('Gun Sight Span Increase Slow'), category = _('Gunsight')}, {pressed = device_commands.Button_11, cockpit_device_id = devices.WEAPONS, value_pressed = -0.1, name = _('Gun Sight Span Decrease Slow'), category = _('Gunsight')}, I now have both the original fast and the slow commands, and this works like a charm. The Altimeter is a different story. I had never changed that; and when I added the slow commands for the altimeter in the same way, I could bind them, but they don't work. I tried a few variations but nothing works. So I have to conclude that I cannot modify the altimeter commands.

I've just tried, and pressing that button long or short does not produce a screenshot. To my surprise, this button actually duplicates the "Autopilot ENGAGE/Disengage" button. Screen shots are requested with the "SysRQ" button (on my German keyboard it's marked "Druck".

I understand that ED cannot give us everything we want, but as a minimum we as their customers can expect some transparency. Glasnost pozhalsta!

In the previous version of 2.7.9 you could export the HUD, it was just not good. That's why I posted the issue on 26-DEC-2021. I was not dreaming! In the current version of 2.7.9 It's not possible at all.

I just checked to be sure nothing has changed. Except for the conditions @Frederf referred to, the "Extend" button extends the speed brake until it's fully extended or you release the button. It then stays in that extended position. Only if you hit "Retract" (or "Retract/OFF") the speed brake retracts. The behaviour you describe sounds as if you had modified a line in the file "default.lua", which you probably have not. I'll explain my wild idea. The "Extend" command binding is defined by this line in "default.lua": { down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = -1.0, value_up = 0.0, name = _('Speed Brake Switch - EXTEND'), category = {_('Throttle Grip'), _('HOTAS')}}, If you had changed the "value_up" part so that it reads "value_up = 1.0" then it would do exactly what you describe. The only other explanation I can think of is that you have a switch bound to "Retract/OFF" (under "Special for Joystick") and that switch is in the "ON" position.

@GrooveWhat's the status? As far as I can see the HMCS Power switch still has no bindings.

You can still lock the stick in the forward position using the "LShift + X" command. It's only the mouse click that doesn't work. To me that means it's a bug. It's not a very recent bug though, because I still have stable at 2.7.7.15038, and it's the same situation. One can argue that it's low priority and I wouldn't object, but we shouldn't lose functionality along the way. Unfortunately, this does happen in DCS World and sometimes that's more irritating than in this case. PS: I used F2 view to see (in OB 2.7.9 only) what the lock commands do: "LShift + X" locks the elevator surfaces in the full nose down position, ailerons to neutral, and the rudder + tail wheel in whatever position they have when you "lock to forward". "LAlt + X" locks elevator and ailerons to neutral, and the rudder + tail wheel in whatever position they have when you "lock to neutral". I struggle to understand the rationale for this logic, especially in the light of what @grafspeesaid.

The earlier 2.7.9 update had added the ability to export the IFEI and the RWR without modifying the related "...ini.lua" files. I had therefore removed my modified files from OvGME. The latest 2.7.9. update has apparently reverted to to earlier "...ini.lua" files, and these devices no longer exported. I therefore had to modify the file "IFEI_init.lua" again by adding the required lines. (The RWR doesn't export well, so I don't care much about that issue.) ED, please fix these files and keep them stable!

These two lines of code seem to do what you describe: {down = alt_commands.ELEC, up = alt_commands.ELEC, value_down = -1.0, value_up = 0.0, cockpit_device_id = devices.AAU34, name = _('Altimeter Mode Switch ELEC/OFF'), category = {_('Instrument Panel')}}, {down = alt_commands.PNEU, up = alt_commands.PNEU, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.AAU34, name = _('Altimeter Mode Switch PNEU/OFF'), category = {_('Instrument Panel')}}, ED will probably provide them "in due course". If you can't wait: They need to go into the "default.lua" under "\joystick" or "\keyboard" depending on where you want to use the commands.

I could not find it in "default.lua". It could probably be created from info in "clickabledata.lua". But I'm not sure I understand how it's supposed to work. When I use it with the mouse left or right click, the switch will go to ELEC or PNEU, but returns to the OFF (middle) position as soon as I release the mouse button. If that's how it should work, I could probably provide two lines of code for use with a pair of pushbuttons. Please let me know if that's what you want!

Yes, sorry it was late (lousy excuse!)

Just to add two other aspects that make me prefer the LUA editing approach: 1. There are various software solutions that allow you to program the command sequences that are produced upon activating a switch. This includes Target (by Thrustmaster) and interesting solutions like VoiceAttack, and there are a few more. Most of them emulate keyboard key sequences. I have used Target for some time long ago, and it certainly has some benefit if you have Thrustmaster devices. But I also experienced stability issues (like with most 3rd party software) and I got rid of target long before I bought the VIRPIL joystick and the DSD button box. When I started to set up commands for VoiceAttack I realized that a very large proportion of the available bindings do not have default key sequences defined. So before being able to use VoiceAttack (or any keyboard-emulating software, I would have to define the many missing key sequences, without duplicating the existing ones. Well, I have stopped right there. 2. Many commands where we use UP/DOWN or INCR/DECR pushbutton bindings to rotate an axis are too "fast", and a few are too "slow". In most cass I can correct that by changing a "gain" parameter in "clickabledata" or a "value_down" parameter in "default.lua". Most of the "default.lua" files where I have added new bindings contain also these kinds of changes. All considered, I find that the LUA editing approach woks best for me. Notwithstanding that, the best solution would be for ED to get their act together and ... a) provide more comprehensive sets of bindings with well-tuned parameters b) provide the flexibility for adjustments that would make LUA editing superfluous

Thanks! I was wondering how they could get 60 PSI . Now this is clearly a bug then and it needs to be formally reported. With a track of course! PS: the Kurfürst boosts up to nearly 2 ata in this nearly wing-breaking scenario. Is that realistic?

OK I got beyond 1.6 ata starting the dive from above 6000 m, but the Ram effect only kicks in when I get above 700 km/h and then the pressure rises abruptly to above 1.65 ata. The manoeuvre does not feel comfortable! And I would have expected the engine to die. When I tried something similar with the jug, the boost pressure went up to 68 PSI (4.5 ata) and the engine overheated.

@streakeagle:That took me some time to read and try to understand. What I understand is that you're happy with your solution, whatever that is. I'll make it short and sweet: I'm happy with mine

@Silent Film Install the free Notepad++ and set it up to "Run as Administrator". Once you have installed Notepad++ you should have its shortcut on your desktop. Right-click the shortcut and select "Properties". Then, on the "Shortcut" tab, click "Advanced". This opens a pop-up window. On that window tick "Run as administrator and hit OK. From now on, when you start Notepad++ from the shortcut, a window will pop up asking whether you want to allow this app to make changes to your device. You confirm this by hitting OK, and now you can edit all .LUA files.

@NineLine: Thanks for engaging the development team on this subject. It's a long-standing sore and I have completely given up on Multi-Player as I keep getting shot down before I even know there is a bandit. Of course that's also due to my eyesight. I'm doing fine in SP, with labels ON (not just a little blue dot that merges with the blue sky).