LeCuvier

Sacarino identified the file for you. Open the file with Notepad++ and you will see these lines at the beginning: return { forceFeedback = { trimmer = 1.0, shake = 0.5, swapAxes = false, }, keyCommands = { Insert the added lines (the ones you want to use) below the line saying "keyCommands = {". Note: this is assuming you don't want to bind any of these commands to a TM Warthog throttle or stick, or a Saitek X52 Pro Flight Controller, or a F16 MFD 1/2. Any command to be bound to one of these controllers must be added into the file with that name, e.g. "F16 MFD 1.lua". This applies to all controllers that have a dedicated ".lua" file in that folder. It does not apply to files ending with ".diff.lua".

Check your axis bindings. There are probably multiple bindings on the same axes. This happens sometimes after updates.

If you are using the TM Warthog throttle and stick you should use the "reset to default" function.

Didn't the combination of Kommandogerät and Übertragungsgerät take care of that?

Good news, thanks!

I tried your scenario. Throtttling back to IDLE just reduces your thrust to nothing; but the electronics continue to work. And no master caution light. It's when you pull the throttles back over the hump to OFF that engines and electonics are cut off. By the way, I could restart the engines after moving the throttles forward (over the hump) to IDLE by flicking the APU switch to OFF and then to ON.

ED is in a difficult position. On one side there are the "comfort gamers" who would like to have an autopilot on the Bf-109K4, and on the other side the realism purists who don't even want to see features of an experimental version. And both defend their positions heatedly, someties dogmatically. I think we should all be a bit more tolerant and accept that we don't have a monopoly on being right.

I found the cause of my issue. I'd had a similar issue with the Hornet and that led me to the solution for the Viper. Background: I use a TM Warthog grip in a VRP MongoosT50 base. The Warthog grip is rather heave and its center of gravity is forward of center. That makes the stick always lean forward some degrees and therefore produces a small pitch input when the stick is free. In the Hornet, I had to enter a 3% deadzone for the pitch axis to make the AP BALT and RALT work. When I tried to apply that solution to the Viper, I found that I needed a deadzone of 6% which I didn't like. So I increased the Pitch axis stiffness in the VRP base quite significantly. The stick is now very stiff in the pitch axis and the pitch autopilot works for both Hornet and Viper now. With deadzone back to 0 for the Hornet and a whopping 5% for the Viper. Bottomline: the Viper's pitch AP is extremely sensitive to small pitch inputs - much more so than the Hornet, and this interferes with the Viper's pitch AP. I have no way of knowing whether that's realistic and therefore won't call it a bug. But I don't like it, and that's putting it very mildly.

Good point, thanks! I have updated my two posts above.

It's a habit acquired from flying the hog. In the hog you need to trim before engaging the autopilot, else it will lose control very quickly. In the hog, the AP is really just a stabilizer. I suppose it wouldn't harm to trim the Viper before engaging the AP, would it?

Changing the indicator_Type from COLLIMATOR to COMMON made the gun useless for both air and ground targets. Also the HUD indication was spread out too wide. I changed it back to COLLIMATOR.

@DH14300I changed the indicator_type per your suggestion, but the HUD does not export. I also changed the viewport name (in both files). No result. Frustrating! This is my .lua: _ = function(p) return p; end; name = _('FA-18 HUD_RDDI_AMPCD_IFEI'); Description = 'FA-18 HUD, RDDI, AMPCD and IFEI, camera on the center (on main monitor)' --Game screen size set to 3600 x 1440. Hardware: Main monitor 2560 x 1440; second monitor 1680 x1050 on the right. Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; aspect = 2560 / 1440; viewDx = 0; viewDy = 0; } } F18_HUD = { x = 2560; y = 380; width = 512; height = 364; aspect = 512/364; } RIGHT_MFCD = { x = 3075; y = 380; width = 512; height = 512; aspect = 1; } CENTER_MFCD = { x = 2560; y = 900; width = 512; height = 512; aspect = 1; } F18_IFEI = { x = 3075; y = 1150; width = 430; height = 167; aspect = 430/167; } UIMainView = Viewports.Center -- GU_MAIN_VIEWPORT = Viewports.Center

@DH14300 How did you manage to export the FA-18C HUD? I added these lines to the file "AVQ32_init.lua" dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("HUD") and added these lines to the monitor setup LUA file HUD = { x = 2560; y = 380; width = 512; height = 512; aspect = 1; } But the HUD does not export to the secondary monitor.

I find the Anton easier to land than the Bf-109 and probably on a par with the Dora. The German warbirds were generally not as easy to land as the P-51 or P-47. I find even the Spit easier to land than the Bf-109 with a little practice and an analog paddle on the stick.

I had a similar problem: After starting DCS I could fly one mission without any problem. However, when I had exited from the mission and selected "Fly again", the mission load would end with a mostly black page with the progress message "Mission Load done" in the bottom. From there, nothing could make it continue. The log file showed a Security error in the file "Macro_handler.lua" and a related IC issue: 2021-05-12 09:30:44.998 ERROR SECURITYCONTROL: Manifest check failed for file 'Scripts/Aircrafts/_Common/Cockpit/Macro_handler.lua' 2021-05-12 09:30:44.998 WARNING SECURITYCONTROL: IC fail: scripts/aircrafts/_common/cockpit/macro_handler.lua Now, I have added some lines to that file to enable macros I've added to "macrosequencies.lua" for some modules. So I compared the current stock file with my customized one and found that the stock file had some minor additions and changes. I have now updated my customized "Macro_handler.lua" with those changes and the problem is fixed. Why am I reporting this? Well. if the problem occurred each time I try to start a mission I would say that I fixed a problem I had caused with my customization and there was nothing to report. But it seems implausible to me that I could fly the first mission without any issues and the mission only failed to start the second time. And the latest log file still shows these two lines that suggested a problem with the macro hander.

I have added these 2 lines to the file "default.lua": {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')}}, These two bindings work like the existing ones for the A/P roll switch. I use them with the AUTOPILOT switch on my TM Warthog throttle. My problem is: I do not see the Pitch autopilot holding altitude. I climb to the desired altitude, trim the pitch as required and set the switch to the upper position (ALT HOLD). But very soon she will start climbing or sinking. I have tried time and again, I'm back to fine-trimming the pitch to hold my altitude. Is the ALT HOLD working for everybody else?

The behaviour of the A/P Pitch switch seems inconsistent indeed if bound to the UP and Down commands. But does it matter? On the ground, before takeoff, both A/P switches should be in the center position and you don't mess with them. It would seem more important to me that they provide bindings for a 3-position ON-OFF-ON switch like the A/P Roll switch. Personally I use the mod I posted on 21-APR-2021 and that works fine for me. My only real problem is that I do not see the A/P maintaining altitude when the switch is in the UP position.

In Options/Controls there is a button above the columns (the leftmost one) labelled "Reset category to defaults". Unfortunately, the button is not wide enough so you see only "et category to defa" (might depend on screen size). You have to select a column (i.e.device) before you push the button. It will come back asking if you really want to reset all assignments for that device. If you confirm and the exit with the OK button, it will restore the defaults.

ED has provided a lot of ON/OFF toggles where the real cockpit has maintained 2- or 3-position switches. I have created a bunch of keybinds for 2- or 3 position switches. See below. Also I have posted a tutorial document that explains how to make your own https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#comment-4646929 Here is a collection of keybinds I created for myself and others. {down = iCommandPlaneAHCPGUNPACArm, up = iCommandPlaneAHCPGUNSafe, name = _('GUN/PAC switch 3-Pos ARM/SAFE'), category = _('Armament HUD Control Panel')}, {down = iCommandPlaneAHCPGUNArm, up = iCommandPlaneAHCPGUNSafe, name = _('GUN/PAC switch 3-Pos GUNARM/SAFE'), category = _('Armament HUD Control Panel')}, {down = iCommandPlaneAHCPLaserArm, up = iCommandPlaneAHCPLaserSafe, name = _('LASER switch 2-Pos ARM/SAFE'), category = _('Armament HUD Control Panel')}, {down = 3004, up = 3004, cockpit_device_id = 7, value_down = 1.0, value_up = -1.0, name = _('TGP switch 2-Pos ON/OFF'), category = _('Armament HUD Control Panel')}, {down = 3004, cockpit_device_id = 7, value_down = 1.0, name = _('TGP Power switch ON'), category = _('Armament HUD Control Panel')}, {down = 3004, cockpit_device_id = 7, value_down = -1.0, name = _('TGP Power switch OFF'), category = _('Armament HUD Control Panel')}, {down = iCommandPlaneAHCPIFFCCOn, up = iCommandPlaneAHCPIFFCCTest, name = _('IFFCC switch 2-Pos ON/TEST'), category = _('Armament HUD Control Panel')}, {down = iCommandPlaneAHCPMasterArm, up = iCommandPlaneAHCPMasterSafe,name = _('Master switch 3-Pos ARM/SAFE'), category = _('Armament HUD Control Panel')}, {down = iCommandPlaneAHCPMasterTrain, up = iCommandPlaneAHCPMasterSafe, name = _('Master switch 3-Pos TRAIN/SAFE'), category = _('Armament HUD Control Panel')}, {down = 3006, up = 3006, cockpit_device_id = 7 , value_down = 1.0, value_up = 0.0, name = _('AHCP HUD Mode 2-Pos DAY/NIGHT'), category = _('Armament HUD Control Panel')}, {down = 3007, up = 3007, cockpit_device_id = 49 , value_down = 1.0, value_up = 0.0, name = _('Emergency Flood Light 2-Pos DAY/NIGHT'), category = _('Electrical power control panel')}, {down = 3007, cockpit_device_id = 49 , value_down = 1.0, name = _('Emergency Flood Light DAY'), category = _('Electrical power control panel')}, {down = 3007, cockpit_device_id = 49 , value_down = 0.0, name = _('Emergency Flood Light NIGHT'), category = _('Electrical power control panel')}, {down = 3001, up = 3001, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('APU Gen Power 2-Pos ON/OFF'), category = _('Electrical power control panel')}, {down = 3004, up = 3004, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('AC Gen Left Power 2-Pos ON/OFF'), category = _('Electrical power control panel')}, {down = 3005, up = 3005, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('AC Gen Right Power 2-Pos ON/OFF'), category = _('Electrical power control panel')}, {down = 3004, cockpit_device_id = 1 , value_down = 1.0, name = _('AC Gen Left Power ON'), category = _('Electrical power control panel')}, {down = 3004, cockpit_device_id = 1 , value_down = 0.0, name = _('AC Gen Left Power OFF'), category = _('Electrical power control panel')}, {down = 3005, cockpit_device_id = 1 , value_down = 1.0, name = _('AC Gen Right Power ON'), category = _('Electrical power control panel')}, {down = 3005, cockpit_device_id = 1 , value_down = 0.0, name = _('AC Gen Right Power OFF'), category = _('Electrical power control panel')}, {down = 3006, up = 3006, cockpit_device_id = 1 , value_down = 1.0, value_up = 0.0, name = _('Battery Power 2-Pos ON/OFF'), category = _('Electrical power control panel')}, {down = iCommandPlaneLGPLandLight, up = iCommandPlaneLGPLightsOff, name = _('Landing Lights ON/OFF'), category = _('Landing gear panel')}, {down = iCommandPlaneLGPTaxiLight, up = iCommandPlaneLGPLightsOff, name = _('Taxi Lights ON/OFF'), category = _('Landing gear panel')}, {down = 3029, pressed = 3029, cockpit_device_id = 38, value_down = 1.0, value_pressed = 0.0, name = _('Anti-Skid Button ON'), category = _('Landing gear panel')}, {down = 3028, pressed = 3028, cockpit_device_id = 38, value_down = 1.0, value_pressed = 0.0, name = _('Anti-Skid Button OFF'), category = _('Landing gear panel')}, {down = 3029, pressed = 3029,up = 3028, up = 3028, cockpit_device_id = 38, value_down = 1.0, value_pressed = 0.0, value_up = 1.0, value_up = 0.0, name = _('Anti-Skid 2-Pos ON/OFF'), category = _('Landing gear panel')}, -- heureka, this works! {down = 3012, up = 3012, cockpit_device_id = 49, value_down = 1.0, value_up = -1.0, name = _('Nose Light 2-Pos switch ON/OFF'), category = _('Lighting Panel')}, {down = 3004, up = 3004, cockpit_device_id = 49, value_down = 1.0, value_up = -1.0, name = _('Accel & Compass Light 2-Pos Bright/DIM'), category = _('Lighting Panel')}, {down = 3013, up = 3013, cockpit_device_id = 49, value_down = 1.0, value_up = -1.0, name = _('Signal Lights 2-Pos BRIGHT/DIM'), category = _('Lighting Panel')}, {down = iCommandPlanePositionLightsFlash, up = iCommandPlanePositionLightsOff, name = _('Position Lights FLASH/OFF'), category = _('Lighting Panel')}, {down = iCommandPlanePositionLightsSteady, up = iCommandPlanePositionLightsOff, name = _('Position Lights STEADY/OFF'), category = _('Lighting Panel')}, {down = 3001, up = 3001, cockpit_device_id = 75, value_down = 1.0, value_up = 0.0, name = _('HMCS Power 2-Pos ON/OFF'), category = _('HMCS Power')}, {down = 3001, up = 3001, cockpit_device_id = 75, value_down = -1.0, value_up = 0.0, name = _('HMCS Power 2-Pos BAT/OFF'), category = _('HMCS Power')}, {down = 3001, cockpit_device_id = 75, value_down = 1.0, name = _('HMCS Power ON'), category = _('HMCS Power')}, {down = 3001, cockpit_device_id = 75, value_down = 0.0, name = _('HMCS Power OFF'), category = _('HMCS Power')}, {down = 3001, cockpit_device_id = 75, value_down = -1.0, name = _('HMCS Power BAT'), category = _('HMCS Power')}, {down = 3002, cockpit_device_id = 15, value_down = 1.0, name = _('Elapsed Timer STRT/STP/RST'), category = _('Systems')}, {down = 3001, cockpit_device_id = 75, value_down = -1.0, name = _('HMCS Power BAT'), category = _('HMCS Power')}, {down = 3010, cockpit_device_id = 39, value_down = 1.0, name = _('Seat Arm Handle SAFE'), category = _('Systems')}, {down = 3010, cockpit_device_id = 39, value_down = -1.0, name = _('Seat Arm Handle ARM'), category = _('Systems')}, {down = 3010, up = 3010, cockpit_device_id = 39, value_down = -1.0, value_up = 1.0, name = _('Seat Arm Handle ARM 2-Pos ARM/SAFE'), category = _('Systems')}, {down = 3007, cockpit_device_id = 39, value_down = 0.0, name = _('Canopy CLOSE'), category = _('Systems')}, {down = 3007, cockpit_device_id = 39, value_down = 1.0, name = _('Canopy OPEN'), category = _('Systems')}, {down = 3007, cockpit_device_id = 39, value_down = 0.5, name = _('Canopy HOLD'), category = _('Systems')}, {down = 3007, up = 3007, cockpit_device_id = 39, value_down = 1.0, value_up = 0.5, name = _('Canopy OPEN/HOLD'), category = _('Systems')},-- for maintained 3-position switch (ON-OFF-ON) {down = 3007, up = 3007, cockpit_device_id = 39, value_down = 0.0, value_up = 0.5, name = _('Canopy CLOSE/HOLD'), category = _('Systems')},-- for maintained 3-position switch (ON-OFF-ON) {down = 3007, up = 3007, cockpit_device_id = 39, value_down = 1.0, value_up = 0.0, name = _('Canopy 2-Pos OPEN/CLOSE'), category = _('Systems')},-- for maintained ON/OFF switch {down = 3016, up = 3016, cockpit_device_id = 36, value_down = -1.0, value_up = 1.0, name = _('Air Refuel Control Lever 2-Pos OPEN/CLOSED'), category = _('Fuel system control panel')}, Note: in some cases the switches in the cockpit are electro/magnetically held. There is no way to guarantee synchronization for these as we do not get feedback from the sim to the button box.

@icemaker: I can reproduce the anti-skid warning on the ground before takeoff. But not if I run a Landing instant action. Test: - Switch anti-skid OFF from my button box - Lower landing gear --> anti-skid warning goes ON - Switch anti-skid ON from my button box --> anti-skid warning goes OFF This makes sense to me as the anti-skid function is relevant for the landing process - not for takeoff. The flight manual should be updated as the warning light does function.

Sorry, I guess you are referring to the "Caution Light Panel". I wouldn't worry about that too much. The Flight manual states on page that the warning light will go ON if the gear is down and Anti-Skid is disengaged, then says "No function". So it's probably not a high priority for the programmers.

I have two versions. One uses 2 pushbuttons, and the other uses a single maintained ON/OFF switch. Both work without any antiskid warning. In fact, I have never seen the anti-skid warning.

Strange! I never see this message. Note: I fly in Open Beta all the time. The real test though is whether the anti-skid is active. It should prevent you from pirouetting when you brake brutally after touchdown.

Can you describe the scenario where you get the anti-skid warning? I tested this morning and it worked fine. When I set the switch to ON I could land without problems, and when it was OFF the landing was a disaster.

You will find the tutorial here: https://forums.eagle.ru/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/?tab=comments#comment-4646929 However I tried the tailhook UP/DOWN command and it works fine here. I just downloaded the A4 files and created the main bindings plus tail hook. All bindings work fine.