LeCuvier

Yes, that's the correct file path for Open Beta. You might have put the lines in the wrong place in the file. I recommend you read the how-to document I have posted here: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

This is exactly what happens if you have a syntax error in the modified LUA file. The file just seems to disappear. If you send me your modified file via PM I'll look at it. Maybe I can see what's wrong.

If you want to help yourself, add these lines to the "default.lua" using Notepad++ ("Run as Admin"): 1. Ejection safety lever: {down = cpt_commands.EjectionSafetyLever, value_down = 1.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever ARMED'), category = {_('Systems')}}, {down = cpt_commands.EjectionSafetyLever, value_down = 0.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever LOCKED'), category = {_('Systems')}}, 2. Elec/Pneu switch: {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')}},

You need to open Notepad++ in Admin mode ("run as administrator").

Looks good to me! The yellow surfaces on the throttle grip still seem canary-like in my cockpit, but that might be due to my graphics settings. You could probably spend the rest of your life trying to make it perfect for everybody. So I declare "I'm happy".

Right, it needs to "see" the event.

in a cold start mission, the software needs to "see" the event of the throttle going to the cut-off position. I always start the mission by moving the throttle to cut-off before anything else.

I agree, the "ADI" was stupidly omitted from the binding's name. Very misleading.

You are trying to re-invent some wheels here . The button commands "Pitch Trim Knob - CW" and "Pitch Trim Knob - CCW" already exist under the category "Instrument Panel".

I'm a lazy fellow. Therefore, instead of writing a very long post about the basic process, I attach a how-to document I wrote mostly for myself. Please read through this and I hope it makes sense to you! It's somewhat complex as you need to add a .lua file for the monitor configuration, and make entries in Options/System that essentially allocate the real estate on your monitor(s), plus appropriate Windows display settings. The basic process as described in the document works perfectly for those displays that ED has enabled for export, like the MFD's. ED apparently think that the RWR is not worth exporting and therefore have not made provision for it. So we need to add a few lines into the file "RWR_ALR56_init.lua" located under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator". When you open the file with Notepadd++ you will see these lines at the beginning: dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.4 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true and so forth... Add these lines below "indicator_type = indicator_types.COMMON": ------------------------ added by HWF dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("RWR") ------------------------ end of added by HWF So now the file looks like this: dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON ------------------------ added by HWF dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("RWR") ------------------------ end of added by HWF shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.4 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true This makes the RWR available for export. Edit: Remember that ED will replace this file with the original when you update or repair, so be sure you keep a backup for the modified file. Plus a backup of the original file of course. Next, you have to create your monitor config file, and the detail depends on what you want to see on your screens. I used the attached file "Camera+LMFCD+RWR.lua" under "C:\Users\USER_NAME\Saved Games\DCS.openbeta\Config\MonitorSetup" to test the export. I realize this is a bit of a stretch for a 4-year old , so just take it step by step and let me know if you get stuck somewhere! DCS MultiMonitor Setup.pdf Camera+LMFCD+RWR.lua

???

The F-16 RWR can be exported, but it has the same shortcomings as the F/A-18C RWR export: The export shows only the luminous symbols. It does not show the static lines of the RWR. See attached screenshot. Note: the blurred appearance of the Mig-29 indication is caused by 2 Mig's flying in formation. Otherwise, the xport is crisp. If you think that it's worth it I can provide the information how to do it.

All versions of DCS World show "Multi-Thread Preview..." on the main screen. I believe that's a bug of the main screen.

As the OP stated that he has the issue in Stable, I downloaded the track provided by @Toastfrenzy and tried to replay it in Stable. However, the replay browser does not show the track file at all. I suspect the format is not valid for Stable. So I opened the track in OB (MT) and I could play it. However I did not see the "flickering". Also, when I fly myself in Stable (or OB), I do not see the flickering. I looked at the video where it is very visible, and my take is that it looks like a problem coming from the game controller, maybe a USB device with insufficient power supply.

Very nice work indeed! Only slight concern: the yellow part of the throttle lever shines a bit too bright when the sunlight hits it. I have Gamma set = 2.2

What kind of MFD modules do you have? If you have the MFD 16 MFD's (from Thrustmaster I guess) they should have default bindings to all MFD buttons and switches. But you cannot bind anything else to them without tampering.

This is definitely hosed. 1. When you change the HUD Video Contrast setting via a bound button, it overrides the HUD Brightness setting. @Maverick87Shaka states in his post that the "Video Brightness" goes up/down 10%. I do not see that. I see only the "HUD Brightness" affected. 2. The hint when you hover over the contrast button is misleading. The hint displays as "HUD Contrast Control", but the button is in reality the "HUD Video Contrast Control".

thanks, yes that was it.

I set up a mission for exercising A/G weapons with hot start from the runway. At mission start, the A/A mode is active by default, and there seems to be no way to switch to NAV or A/G. I have bound the Mode commands to pushbuttons on my button box, and I see the buttons depressing in the cockpit, but they have no effect. Is there some "magic" I have overlooked, or is this WIP behaviour?

It's actually no big deal to copy these .LUA lines from the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-15E\Input\F-15E\joystick" to the one under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-15E\Input\F-15E\keyboard". Especially for Voice Attack users that may be worthwhile. Of course the modified file will be overwritten when you do an update or repair, so you need to make a backup. Or, use the Command Injector developed by @Quaggles and keep your additions under Saved Games. That's what I do.

It does nothing other than emphasizing to the user that it's the "Pilot" version of a command normally reserved for the CPG.

He changes the "Name" field in the .LUA line by adding "Pilot" as a prefix.

Interesting, I learned something!

Oops, I'm not familiar with the Apache although I have the module, and I wrongly assumed that the aft cockpit is for the CPG. The command for the CPG is defined in this line in the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Input\AH-64D_CPG\joystick": {down = tedac_commands.RHG_SIGHT_SLAVE_BTN, up = tedac_commands.RHG_SIGHT_SLAVE_BTN, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, value_up = 0.0, name = _('RHG Sight Slave Button'), category = {_('TEDAC'), _('Right Handgrip')}}, You can add this line into the "default.lua" under "C:\Users\USER\Saved Games\DCS.openbeta\InputCommands\AH-64D\Input\AH-64D_PLT\joystick". But I'm not sure that the software will let the pilot use this command. Also, I wouldn't know how to test it as the pilot doesn't see this button.

The command "RHG Sight Slave Button" is already available for the CPG. What are you trying to add?