LeCuvier

@Red Dog Coming back to the EPU switch, you would normally need 4 digital inputs and 4 end switches for the 2 guards. However, we can halve that by combining the respective ON and OFF commands into a single line of code each. I show how to do that, using the cover for ON as an example. The stock "default.lua" has these 2 lines of code: { down = engine_commands.EpuSwCvrOn, cockpit_device_id = devices.ENGINE_INTERFACE, value_down = 0.0, name = _('EPU Switch Cover for ON - CLOSE'), category = {_('Left Console'), _('EPU Control Panel')}}, { down = engine_commands.EpuSwCvrOn, cockpit_device_id = devices.ENGINE_INTERFACE, value_down = 1.0, name = _('EPU Switch Cover for ON - OPEN'), category = {_('Left Console'), _('EPU Control Panel')}}, We create a new line of code that combines the 2: {down = engine_commands.EpuSwCvrOn, up = engine_commands.EpuSwCvrOn, cockpit_device_id = devices.ENGINE_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('EPU Switch Cover for ON 2-Pos OPEN/CLOSE'), category = {_('Left Console'), _('EPU Control Panel')}}, The "Zeroize" switch is a 3-position switch, and unfortunately ED forgot to provide the 2 lines of code required for a proper 3-position switch which should be under "Special for Joystick". So we create these 2 lines based on the 3 lines that they provide for use with 3 digital inputs: {down = intercom_commands.ZeroizeSw, up = intercom_commands.ZeroizeSw, cockpit_device_id = devices.INTERCOM, value_down = 1.0, value_up = 0.0, name = _('ZEROIZE Switch - OFP/OFF'), category = {_('Right Console')}}, {down = intercom_commands.ZeroizeSw, up = intercom_commands.ZeroizeSw, cockpit_device_id = devices.INTERCOM, value_down = -1.0, value_up = 0.0, name = _('ZEROIZE Switch - DATA/OFF'), category = {_('Right Console')}}, Again, you need to create a line of code so you can use a single switch to control the guard, using the same approach as for the EPU switch guards.. If you need help with this, don't hesitate to get back to me, preferrably via PM.

@Red Dog: I got something working. Please check if that's what you want! I have added this line to "default.lua": {down = engine_commands.EngContSwCvr, pressed = engine_commands.EngContSw, up = engine_commands.EngContSwCvr, cockpit_device_id = devices.ENGINE_INTERFACE, value_down = 1.0, value_pressed = 1.0, value_up = 0.0, name = _('ENG CONT Switch + Cover SEC/PRI'), category = {_('Left Console'), _('ENG & JET START Control Panel')}}, This creates the new command "ENG CONT Switch + Cover SEC/PRI" (you can change the name to whatever you want, as long as it is unique). I bound this command to a maintained ON/OFF switch (like the EAC switch) on my TM Warthog throttle. When I set the physical switch to ON, the cover opens, immediately followed by the switch flipping down to the "SEC" position. When I set the physical switch to OFF, the cover closes pushing the switch back to the "PRI" position. The EPU switch is a challenge and I don't know if I'm up to it. Incredebible what kind of gadgets the aircraft designers come up with. One of these switches costs probably more than $ 10,000 because they are specially designed for the F-16 and need to go through alll the certifications. I will look at the two others first and hope for inspiration on the EPU. The following line of code is for the fuel master switch and cover. It works here: {down = fuel_commands.FuelMasterSwCvr, pressed = fuel_commands.FuelMasterSw, up = fuel_commands.FuelMasterSwCvr, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, value_pressed = 1.0, value_up = 0.0, name = _('FUEL MASTER Switch + Cover OFF/MASTER'), category = {_('Left Console'), _('Fuel Control Panel')}}, I will look at the Zeroizer tomorrow. For the EPU switch I don't see a comparable solution. There are bindings for a 3-position switch under "Special for Joystick", but you will have to provide inputs for the two guards.

@kablamoman Haha, I suspected that they had messed up the button numbers but didn't have the patience to fiddle with them. Thanks!

Question: Do you use maintained ON/OFF switches? And can you give me a few examples of switches (names of the switch bindings so I can find them)?

@Red Dog: I have made adds to the "default.lua" for several aircraft to combine the guard and the switch into a single binding. For which aircraft do you build your pit?

You don't need a dedicated .lua file for your button box under "...\DCS World OpenBeta\Mods\aircraft\FW-190D9\Input\aircraft\joystick". The "default.lua" is good for all game controllers that don't have a dedicated file like "Throttle - HOTAS Warthog.lua".

I'm slightly confused. You say that the rotary encoder is fast and the button command is slow. In my experience it's just the other way around, and that's because the rotary encoder provides only a very short pulse on every "click". Please clarify! Note: It's possible to make these commands faster by changing the "gain" parameter for the controls in "clickabledata.lua" under "...\DCS World OpenBeta\Mods\aircraft\A-10C_2\Cockpit\Scripts". These are the 2 lines of code with gain changed from 0.2 to 0.2: --Horizontal Situation Indicator elements["PNT-LVR-HSI-HDG"] = default_axis(_("Heading Set Knob"),devices.HSI, device_commands.Button_1, 45, 1.0, 0.2, false, true)-- HWF changed gain from 0.1 to 0.2 elements["PNT-LVR-HSI-CRS"] = default_axis(_("Course Set Knob"), devices.HSI, device_commands.Button_2, 44, 1.0, 0.2, false, true)-- HWF changed gain from 0.1 to 0.2

Some of us (including myself) don't have any spare slider. I created these 3 commands (for addition to "default.lua") that set the lever axis to MAX, OFF or HALF. I actually only use MAX and OFF. {down = device_commands.Button_18, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 1.0, name = _('Cold Air Control OFF'), category = _('Carburetor Air Controls')}, {down = device_commands.Button_18, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 0.0, name = _('Cold Air Control HALF'), category = _('Carburetor Air Controls')}, {down = device_commands.Button_18, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = -1.0, name = _('Cold Air Control MAX'), category = _('Carburetor Air Controls')},

@ESzczesniak I have created these lines for the fuel dump switch and they worked at the time: {down = fuel_commands.DumpSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, name = _('Fuel Dump Switch ON'), category = {_('Left Console'), _('Fuel Control Panel')}}, {down = fuel_commands.DumpSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = -1.0, name = _('Fuel Dump Switch OFF'), category = {_('Left Console'), _('Fuel Control Panel')}}, For the pitot heater: {down = elec_commands.PitotHeater, cockpit_device_id = devices.ELEC_INTERFACE, value_down = 1.0, name = _('Pitot Heater Switch - ON'), category = {_('Right Console'), _('ECS Panel')}}, {down = elec_commands.PitotHeater, cockpit_device_id = devices.ELEC_INTERFACE, value_down = -1.0, name = _('Pitot Heater Switch - AUTO'), category = {_('Right Console'), _('ECS Panel')}}, PS: To insert .LUA code, copy the lines to the clipboard. Then in the post window click on the "post" button marked "<>". This will open a window where you can paste your code.

But, hold it! You talk about trying to use left and right wheel brakes, and then you refer to to the "X" and "Z" commands which are for the rudder. Can you be clear about what you are doing?

On a personal note: I'm 76 and the years have taken a toll on my eyesight, glaucoma and a beginning of cataract not helping. I love to fly in this sim, but these artifacts that the developers add with the best intentions make it far more difficult and tiring for my eyes. And I'm certainly not the only person with similar impairments. So please, ED, if you think that younger people need reflections and opacities, please keep in mind that these take the fun out of the sim for a lot of people and give us options to reduce or void them! I wish the ED team and my fellow simmers a happy, healthy and successful year 2022!

Yes, I spent some time creating the ECM commands but gave up. And having to use two commands for every one of the buttons on the numeric pad is not acceptable. I'm afraid we'll have to wait for ED.

Makes me sick to think of the many hours developers spend on creating and tweaking reflections and opacities that cause problems for most people. Plus the hours simmers spend to try and get rid of them? Don't we have real bugs and deficiencies the developers could focus their energy on?

I just tried again in 2.7.9 , with gunsight range and base set to 0.1 and -0.1 values and they work.

no, there is no adjustment for reflections.

No luck! I tried different values in the lines below, and the Heading didn't move at all. { pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = -0.01, name = _('HDG Set Knob - CCW/Decrease'), category = {_('Instrument Panel')}}, { pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = 0.01, name = _('HDG Set Knob - CW/Increase'), category = {_('Instrument Panel')}},

@BIGNEWY Thanks!

I have found 4 .dds files that had a "modified" date of 23-DEC-2021. I do not understand these files although I have some experience with Photoshop and have been able a couple of times to reduce opacity of a HUD or so. But I took a gamble and replaced the 4 files with those from 2.7.7. stable release. And that works for me. There are still plenty of reflections especially in the free flight (Caucasus) mission, but I don't see the instrument board anymore. And in a dog fight mission it's back to what it was. The screen shot shows the 4 files I replaced. ED tried to fix what wasn't broken, and made it worse.

Correct. Makes the issue very visible, good test case!

If my old eyes don'tplay me a trick, the knob placement is ok. It's just the label "Frequenzschalter" that's off to the left. And if you consider the circumstances under which these machines were produced, the label alignment was the least of their priorities.

I happened to be in a mission today where the reflections are weak enough so they don't bother me, and some people may just not have been in daylight conditions where it's as bad as in my screenshot above. But at any rate, as @Art-J stated, there is no way by the laws of optics that there can be reflections of the instruments board on these glass surfaces.

I cannot reproduce what you describe.

Well, I don't fly in VR and I don't like to be frustrated. And maybe that's because I'm 76. My screenshot didn't capture the reflections well. Here is what it really looks like for me, captured with the Windows 10 snipping tool. I tried the same scenario in 2.7.7 stable release with the same graphics settings, and it has none of this.

How do the wheelbrake axes test in Windows? Can you post screen shots with the pedals not depressed and fully depressed?

All 3 trim axes work as expected here. Open Beta, Sim mode, no FFB.