LeCuvier

I have a 4790-based PC with 16 GB of RAM. I flew a Hornet and the black Shark over some distance, and frame rates were around 50. No combat activity. Exiting the game and closing the PC down did not seem longer than usual. I was very impressed with the level and quality of the detail. Only in one point I was just slightly disappointed. I have been to Jordan a few weeks ago and visited the antique temple site of Jarash (Gerasa). This bit of northern Jordan is included in the Syria map and so I decided to re-visit Jarash with the Black Shark for some sightseeing. I could in fact find the temple site and some features (like the southern theatre and the oval square) reminded of the real thing. But the sim is very different from the real site. I didn't really expect it to be an accurate reproduction, but it would have been nice!

Thanks!

ATC works here. I've bound it to the MIC Push button.

I searched through the commands and could not find "Cockpit Global Illumination". Do you mean "CB Cabin Illumination"?

There is clearly an issue. I don't generally fly the Spit and I had never before today flown a mission in the CW version, but got curious when I saw this thread. Status this morning: I had no folder for the CW under "C:\Users\hans\Saved Games\DCS.openbeta\Config\Input\". I created a mission for the CW and flew it a couple of times. Everything worked fine. I actually added a binding during the mission. When I exited DCS World there was still no folder under "C:\Users\hans\Saved Games\DCS.openbeta\Config\Input\". Tonight: I started DCS World OB and launched the mission with the CW, and found I had no control over the aircraft. It turned out I had no commands bound except the defaults. I bound some axes so I could at least fly the thing, and oops! Now I have the folder "C:\Users\hans\Saved Games\DCS.openbeta\Config\Input\SpitfireLFMkIXCW". I was too lazy to re-create all the bindings for the CW, so I copied the "....diff.lua" files from "C:\Users\hans\Saved Games\DCS.openbeta\Config\Input\SpitfireLFMkIX" to "C:\Users\hans\Saved Games\DCS.openbeta\Config\Input\SpitfireLFMkIXCW", and that works just fine. Conclusion: There is inconsistent behaviour and I cannot see any logic that would explain why this morning I could fly the CW version but tonight it had no bindings except defaults. It's inconsistent and that may explain why some people have not seen the issue. Even if there is a hidden logic that developers understand, it should be reported as a bug. It could be very easily fixed. When you first fly the CW the software should copy the files as I did manually.

There is indeed an axis command "Engine RPM Setting". I tried it out of curiosity and it's not an absolute position-type axis. You have to move the slder very far from its center position before the "clock" pointer starts moving up- or downwards. It acts practically like a rocker switch. I find it useless and I would never waste one of my few axis controls for this command.

You can use keyboard binds, or bind the commands to buttons on your HOTAS. I've customized mine so I can both open the cover and initiate the jettison with a single switch.

I suppose you are referring to the command "Fuel Selector Valve AFT Tank Closed". In order to replicate your issue I bound the command to the button "JOY_BTN_POV1_D" on my joystick, and I could in fact replicate your problem. I also bound the same command to a button on my TM WH throtlle plus to a button on my Button Box, and there it worked fine. So it's certainly not a general problem. I checked my joystick bindings and found that this button was still bound to "View Down Slow" which is the default binding. I cleared this redundant binding and now the command "Aft Tank Closed" works fine. It seems that DCS World had not cleaned up the "....diff.lua" file for my joystick under "C:\Users\my name\Saved Games\DCS.openbeta\Config\Input\FW-190D9\joystick". I'm not 100% sure that the problem you observed is the same. Go through your bindings and check if it has a second binding, probably to one of the default bindings. Alternatively, you might delete that ".diff.lua" file under Saved Games and re-do your control bindings.

If you are referring to @GaryR's statement: this is not implemented in DCS World, and I do not know that they have any intention to implement it. So we are obliged to either accept the software as is, or edit the .lua files.

The Master Arm switch has bindings in the "Special for Joystick" category which enable the use of maintained 2- or 3-position switches. The Laser Arm switch does not have such options out-of-the-box unfortunately. The binding can be created by adding this line into the file "default.lua": {down = sms_commands.LaserSw, up = sms_commands.LaserSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('LASER ARM Switch 2-Pos ARM/SAFE'), category = {_('Instrument Panel')}}, If you want to try this but have no experience with this kind of edit I suggest you download and read the tutorial in this thread: This thread has many example additions for various aircrafts.

I concur with @rob10. Looks like you are trying to re-invent the wheel.

I cannot belive you could do this booming and zooming without blacking out. Are you flying with G effects disabled?

The original "Instant Action" missions are under "K:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\P-47D-30\Missions\QuickStart". I save the modified versions under "C:\Users\hans\Saved Games\DCS.openbeta\Missions\P-47D\QuickStart". Your drive letters might obviously be different.

Yes, an Umformer is an electrical motor/generator. It would produce electrical power different from the general power supply's parameters. For example it might suüüly 3-phase current.

Solution here: https://forums.eagle.ru/topic/282230-upneutraldown-bindings-for-landing-gear/?tab=comments#elControls_4777152_menu (if you are willing to make a little edit in the "default.lua"). My second post in that thread includes two lines of LUA code.

I use the TM Warthog throttle and I do not see that issue.

I found a way for the landing gear switch. I added the two lines below to the "default.lua": {cockpit_device_id = devices.THREE_WAY_SELECTOR, pressed = device_commands.Button_4, down = device_commands.Button_2, up = device_commands.Button_2, value_pressed = 1.0, value_down = 1.0, value_up = 0.0, name = _("Gate Up and Chassis Lever Pull-Up/Middle"), category = {_("Systems"), _("Hydraulic System")}}, {cockpit_device_id = devices.THREE_WAY_SELECTOR, pressed = device_commands.Button_4, down = device_commands.Button_2, up = device_commands.Button_2, value_pressed = 1.0, value_down = -1.0, value_up = 0.0, name = _("Gate Up and Chassis Lever Push-Down/Middle"), category = {_("Systems"), _("Hydraulic System")}}, I bound these new commands to the 3-position Autopilot switch on my TM WH throttle and it worked acceptably for me. Correct operation requires that after pushing down or pulling up, you have to return the switch to the Center position, and wait till the lever in the sim has returned to the Center position, before you activate the switch in the opposite direction. Note: These 2 commands work also with 2 pushbuttons or a 3-position switch with spring return to OFF. That is my preferred solution. The same approach might work with the two other 3-position levers, but I won't able to play with this for a while.

The existing commands "Undercarriage gear, lever - pull up" and "...push down" work with a 3-position (ON1 -OFF-ON2) switch. I have bound the 2 commands to the "PATH" and "ALT" positions of the autopilot switch on my TM WH throttle and that works. Of course you need to use the lock gate to enable the movements.

It takes only this simple line of code, added to "default.lua" (or "Throttle - HOTAS Warthog.lua" if you want to use the slider on the TM WH throttle) : {action = 3013, cockpit_device_id = 38, name = _('Yaw Trim Knob Axis')}, However, ED in my experience have not been very responsive making such additions. You can easily add it yourself, but ED will restore the original file when it updates, so you must create a backup copy of the changed file.

It does not matter at all, as long as you put them into the right block of lines. Personally, I put all added lines at the end of the block for key commands., like this: --added HWF {down = mmc_commands.Alt, up = mmc_commands.Alt, cockpit_device_id = devices.MMC, value_down = 1.0, value_up = 0.0, name = _('HUD Altitude Switch 2-POS RADAR/BARO'), category = {_('Right Console'), _('HUD Control Panel')}}, {pressed = hotas_commands.THROTTLE_ANT_ELEV_UP, cockpit_device_id = devices.HOTAS, value_pressed = 0.2, name = _('ANT ELEV Knob - CW Fine'), category = {_('Throttle Grip'), _('HOTAS')}}, {pressed = hotas_commands.THROTTLE_ANT_ELEV_DOWN, cockpit_device_id = devices.HOTAS, value_pressed = -0.2, name = _('ANT ELEV Knob - CCW Fine'), category = {_('Throttle Grip'), _('HOTAS')}}, {down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('LG Handle 2-Pos UP/DOWN'), category = {_('Left Auxiliary Console')}}, {down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ALT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ATT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = fcr_commands.PwrSw, up = fcr_commands.PwrSw, cockpit_device_id = devices.FCR, value_down = 1.0, value_up = 0.0, name = _('FCR Switch 2-Pos FCR/OFF OFF'), category = {_('Right Console'), _('SNSR PWR Control Panel')}}, {down = ufc_commands.FLIR_GAIN_Sw, up = ufc_commands.FLIR_GAIN_Sw, cockpit_device_id = devices.UFC, value_down = 1.0, value_up = 0.0, name = _('ICP FLIR GAIN/LEVEL 3-Pos Switch GAIN/LVL'), category = {_('Instrument Panel'), _('ICP')}}, {down = ufc_commands.FLIR_GAIN_Sw, up = ufc_commands.FLIR_GAIN_Sw, cockpit_device_id = devices.UFC, value_down = -1.0, value_up = 0.0, name = _('ICP FLIR GAIN/LEVEL 3-Pos Switch AUTO/LVL'), category = {_('Instrument Panel'), _('ICP')}}, {down = rwr_commands.Power, up = rwr_commands.Power, cockpit_device_id = devices.RWR, value_down = 1.0, value_up = 0.0, name = _('RWR Indicator Control POWER Button 2-Pos DEPR/REL'), category = {_('Left Auxiliary Console'), _('THREAT WARNING AUX Panel')}}, {down = cpt_commands.EjectionSafetyLever, up = cpt_commands.EjectionSafetyLever, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever 2-Pos ARMED/LOCKED'), category = {_('Systems')}}, {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')}}, })

That might be a good idea.

I do not have the 4 lines displayed in orange, because my added lines have " Fine" added to the names of the added bindings. I suspect you added the new lines with the same names as the original lines. In other words, you have lines with identical names but different code. That's an (non-lethal) error condition. I could have changed the original lines as you did, but I wanted to keep the original lines for quick coarse adjustments.

@LowlyslowsYou copy the two lines above and paste them into the "default.lua", using the free Notepad++ editor. It's important you paste them into the right block of code. Refer to the document for specifics.

The how-to document and additions for several aircrafts are in this thread: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#elControls_4646929_menu

Just a few additions for the F-16C: {down = mmc_commands.Alt, up = mmc_commands.Alt, cockpit_device_id = devices.MMC, value_down = 1.0, value_up = 0.0, name = _('HUD Altitude Switch 2-POS RADAR/BARO'), category = {_('Right Console'), _('HUD Control Panel')}}, {pressed = hotas_commands.THROTTLE_ANT_ELEV_UP, cockpit_device_id = devices.HOTAS, value_pressed = 0.2, name = _('ANT ELEV Knob - CW Fine'), category = {_('Throttle Grip'), _('HOTAS')}}, {pressed = hotas_commands.THROTTLE_ANT_ELEV_DOWN, cockpit_device_id = devices.HOTAS, value_pressed = -0.2, name = _('ANT ELEV Knob - CCW Fine'), category = {_('Throttle Grip'), _('HOTAS')}}, {down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('LG Handle 2-Pos UP/DOWN'), category = {_('Left Auxiliary Console')}}, {down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ALT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ATT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = fcr_commands.PwrSw, up = fcr_commands.PwrSw, cockpit_device_id = devices.FCR, value_down = 1.0, value_up = 0.0, name = _('FCR Switch 2-Pos FCR/OFF OFF'), category = {_('Right Console'), _('SNSR PWR Control Panel')}}, {down = ufc_commands.FLIR_GAIN_Sw, up = ufc_commands.FLIR_GAIN_Sw, cockpit_device_id = devices.UFC, value_down = 1.0, value_up = 0.0, name = _('ICP FLIR GAIN/LEVEL 3-Pos Switch GAIN/LVL'), category = {_('Instrument Panel'), _('ICP')}}, {down = ufc_commands.FLIR_GAIN_Sw, up = ufc_commands.FLIR_GAIN_Sw, cockpit_device_id = devices.UFC, value_down = -1.0, value_up = 0.0, name = _('ICP FLIR GAIN/LEVEL 3-Pos Switch AUTO/LVL'), category = {_('Instrument Panel'), _('ICP')}}, {down = rwr_commands.Power, up = rwr_commands.Power, cockpit_device_id = devices.RWR, value_down = 1.0, value_up = 0.0, name = _('RWR Indicator Control POWER Button 2-Pos DEPR/REL'), category = {_('Left Auxiliary Console'), _('THREAT WARNING AUX Panel')}}, {down = cpt_commands.EjectionSafetyLever, up = cpt_commands.EjectionSafetyLever, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.CPT_MECH, name = _('Ejection Safety Lever 2-Pos ARMED/LOCKED'), category = {_('Systems')}}, {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')}},