LeCuvier

I think I have found the culprit, it's in the mission's radio settings for the Player's flight. Open one of the defective missions and select the aircraft group of the player's flight. The checkbox between the labels "Radio" and ""Frequency" needs to be ticked in order to enable radio communications. In this mission ("P47-Channel-Fw 190 D9 Dogfight") the checkbox is not ticked and therefore radio communication is not enabled. So the problem is easy to fix: just tick the checkbox and save the mission. Now, if ED does not fix it in the published version, your change will be lost in the next update. You can prevent this in two ways: 1. Save the corrected mission with a modified name (e.g. include your initials in the file name) 2. Save the corrected mission under "Saved Games" @NineLine: please report. This should be checked and corrected in all published missions!

I tried two P-47 Instant Action missions, both in the Channel map, with wingmen: 1. FW-190A8 Furball 2. FW-190A8 Dogfight In the Furball mission my wingmen (3 of them) did respond to radio messages. In the Dogfight mission the (single) wingman did not respond ever. I checked both missions and in both the inflight radio frequency was set to 105 MHz and 105 MHz was assigned to channel "A". So mission settings are probably not the cause of the problem. And we cannot say that Wingmen radio comms fail generally with the P-47D, because it worked in the furball mission. In order to (hopefully) find out what makes it fail, you guys need to provide more specifics; especially on which mission it fails or works. Note: I have observed that wingmen sometimes respond and sometimes don't, when I fly other warbirds. So the problem might not be related to the P-47D but to AI wingmen in general.

Agree with @grafspee. Let her run till she wants to lift off and then pull only minimally to let her clear off the deck, retract gears and let her accelerate to a safe speed before you pull up. Compared with the German fighters she is very easy to handle in take-off and landing.

Yes certainly you can bind OSB's to pushbuttons on your game controllers or keyboard. So if you bind a pushbutton to OSB 5 on the left MFCD for example, pressing that pushbutton will always activate OSB 5 on the left MFCD, no matter what mode you are in and no matter which MFCD is SOI.

There are 2 commands for pushbuttons: "Push to Test Switch - CCW/Decrease" "Push to Test Switch - CW/Increase" The naming is a bit ridiculous isn't it? There is no axis commands, but it might be possible to create one if that's what you want.

My experience is more like that of @foxit. Note: I always fly with the "Sync Cockpit Controls at mission start" checked, and I have never seen the issue described by @Cerulean; but prompted by this thread I did a little test. 1. I unchecked the said option and launched a "free flight" mission with the F-16, with my throttle at about 50%. The throttle in the sim was at maximum, but the rudder was in neutral position. 2. I re-checked the said option, and launched the same free-flight option, again with the throttle at 50%. The throttle in the sim was at about 50% and the rudder was in neutral position. So for me (and @foxit) the option "Sync Cockpit Controls at mission start" works as expected when it is checked. For @MAXsenna and @Ceruleanit doesn't. Unfortunately our test sample is too small to come to any solid conclusion, other than that there seems to be some inconsistency in the handling of this option. But I would like to see if there is a pattern related to the equipment for Rudder and Throttle. I use the TM Warthog throttle and MFG pedals. Would each of you guys state what you use?

@moridarThanks, that gives me the picture! Sounds attractive; I'll probably try it.

@moridarI'm trying to understand what exactly TouchDCS is. Does it require a touch screen?

I continue to use the old FMOptions.lua which has a "last changed" date in August 2018. Out of curiosity I switched to the current stock file and did a take-off and landing, then switched back to the old file and did the same, using the same process. With the current file 1. I need a little bit of differential braking at the very beginning of the take-off run, but no big deal. 2. The landing needs a bit more attention after touchdown to keep her from breaking left of right, but again quite manageable. In conclusion, I see a distinct difference and maybe the current file is more realistic, but the difference is not dramatic at all. Having said this, I continue using the old file as it handles more nicely. This does not pass Integrity Check for MP, but that's no problem for me as my old eyes cannot spot hostiles without labels (real lablels, not a blue dot), so MP is out for me anyway.

The gun is much more effective for these targets.

What do you mean by "the off"?

I suspect it's modelled as in the real thing. And it's used for different functions, not just NWS. And if you modify the command that might not work well with the other functions. Not a good candidate for customizing.

I do not see that issue with my TM WH throttle and MFG pedals. Are you guys sure you don't have duplicate (or multiple) bindings on these axes?

Thank you for posting this article, it certainly reduced my ignorance in this matter. But could you be a bit less harsh to those of us who are less knowledgeable than you?

If your joystick is connected via a USB hub then the hub could be the problem; especially if it doesn't have its own power supply.

Back to the original subject of this thread: I was tired of having to mess with a lot of trimming at the start of airborn missions, so I figured something out. 1. all 3 trim wheels are in their center position when the mission starts. 2. Elevator trim must be more tailheavy, rudder needs a lot of yaw-right trim, and ailerons need a bit of right-wing down trim. 3. I determined, by trial and error, which action values would be required for the trim axes and found: Elevator = -0.4 Rudder = 0.2 Ailerons = -0.15 Note: the action value for the center or "neutral" position is = 0. I created a key command (to be bound to a pushbutton or keyboard key) that combines the 3 action values. This line of code is added to my "default.lua": {down = device_commands.Button_6, pressed = device_commands.Button_9, up = device_commands.Button_3, cockpit_device_id = devices.CONTROLS, value_down = -0.4, value_pressed = 0.2, value_up = -0.15, name = _('Elevator_Rudder_Aileron Trim Preset'), category = {_('Flight Control')}}, This creates a new command "Elevator_Rudder_Aileron Trim Preset" which I bound to a button on my joystick. Immediately after mission start I hit this button and from there I have very little trimming to do. (at about 300 knots IAS) Those who don't mind modifying the "default.lua" are welcome to try this solution.

Negative. I do have these two commands in the file "default.lua", and that's because I added them myself.

I've used the CBU-105 a lot in the past and I could rarely kill more than 3 armoured vehicles with one bomb. Recently I used it again and it killed almost everything within range. It has obviously been made more deadly. I hope it will stay that way!

I reduced the "gain" parameter for the 3 trim wheels from 0.025 to 0.0125 in the file "clickabledata.lua" in the folder "...\DCS World OpenBeta\Mods\aircraft\P-47D-30\Cockpit\Scripts". Here is the block of lines with the 3 modified lines: -- Aileron Trim Wheel elements["pnt_91"] = cabin_axis_limited(0, _('Aileron Trim'), devices.CONTROLS, device_commands.Button_1, 91, 0.0, 0.0125, false, false, {-1.0, 1.0}, {135, -45}, {45, -45})-- HWF changed Gain from 0.025 to 0.0125 elements["pnt_91"].sound = {{SOUND_SW5}} -- Elevator Trim Wheel elements["pnt_92"] = cabin_axis_limited(0, _('Elevator Trim'), devices.CONTROLS, device_commands.Button_4, 92, 0.0, 0.0125, false, false, {-1.0, 1.0}, {-135, -20}, {-45, -30})-- HWF changed Gain from 0.025 to 0.0125 elements["pnt_92"].sound = {{SOUND_SW5}} -- Rudder Trim Wheel elements["pnt_93"] = cabin_axis_limited(0, _('Rudder Trim'), devices.CONTROLS, device_commands.Button_7, 93, 0.0, 0.0125, false, false, {-1.0, 1.0}, {135, -45}, {45, -45})-- HWF changed Gain from 0.025 to 0.0125 elements["pnt_93"].sound = {{SOUND_SW5}}

As far as I can see they are not included in the stock file. I think you are using a modified "default.lua" file.

I posted the attached "How-to" document years ago but cannot remember where. I also attach a copy of my file "Macro_sequencies.lua" (folder "...\DCS World OpenBeta\Mods\aircraft\P-47D-30\Cockpit\Scripts". If you compare it with the stock file in Notepad++ you will see that I added some declarations at the top (marked with the comment "-- added HWF): dofile(LockOn_Options.script_path .. "command_defs.lua") dofile(LockOn_Options.script_path .. "devices.lua") std_message_timeout = 15 local t_start = 0.0 local t_stop = 0.0 local delta_t_com = 2.0 start_sequence_full = {} stop_sequence_full = {} cockpit_illumination_full = {} -- added HWF function push_command(sequence, run_t, command) sequence[#sequence + 1] = command sequence[#sequence]["time"] = run_t end function push_start_command(delta_t, command) t_start = t_start + delta_t push_command(start_sequence_full,t_start, command) end function push_stop_command(delta_t, command) t_stop = t_stop + delta_t push_command(stop_sequence_full,t_stop, command) end function push_CBs_command(delta_t, command) -- added HWF t_stop = t_stop + delta_t push_command(cockpit_illumination_full,t_stop, command) end and the macro to push the CB's at the end: -- added HWF: Macro to push all CB's to simplify manual start push_CBs_command(1.0,{message = _("Push CB's Macro Starting"),message_timeout = std_message_timeout}) push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_54, value = 1.0})--CB Guns LO push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_56, value = 1.0})-- CB Guns RI push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_58, value = 1.0})-- CB Guns RO push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_60, value = 1.0})-- CB Fuel Pumps push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_62, value = 1.0})-- CB Oil Cooler push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_64, value = 1.0})-- CB Intercooler push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_66, value = 1.0})-- CB Guns Relay push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_68, value = 1.0})-- CB Gun Sight push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_70, value = 1.0})-- CB Canopy push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_72, value = 1.0})-- CB LLight (or ILight?) push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_74, value = 1.0})-- CB Warnings push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_76, value = 1.0})-- CB CLight push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_78, value = 1.0})-- CB Pitot push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_80, value = 1.0})-- CB NLight push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_82, value = 1.0})-- CB RLight push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_84, value = 1.0})-- CB Radio push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_86, value = 1.0})-- CB Prop push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_88, value = 1.0})-- CB Bombs push_CBs_command(0.01, {device = devices.MAIN_SWITCH_BOX, action = device_commands.Button_90, value = 1.0})-- CB CRFlaps push_CBs_command(6.0,{message = _("Push CB's Macro COMPLETE"),message_timeout = std_message_timeout}) You could just change the 4 first commands (device, action and value) to produce the jettison lever commands and delete the remaining commands, and modify the 2 message lines. The message lines are not necessary but I like them for debugging. If you want it to be neat, change the function name from "push_command" to something like "jettison_wing_hardpoints". The only other thing you need to do is add this line to "default.lua" (change the name of course!) and bind it to a button: {down = 300, name = _('Push CBs'), category = _('Cheat')}, -- Requires macro! On some airplanes I added two macros (for interior lights) but the second macro is more tricky. As I said,a lot of hoops to jump through and more rewarding for long command sequences. How to Create Macros_2019-07-26.pdf Macro_sequencies.lua

Unfortunately I found no way to trigger more than 3 commands in a single line of "default.lua". That's because I cannot pair the command "pressed" with an equivalent of the "up" command. I have added a second "up" and "value_up = 0.0" but that has no effect. The only way to create more commands with a single button is via a macro. That's the mechanism used for the auto-start and auto-stop function. ED has built in some provision for a third macro, and I build on that with a macro that pushes all 19 CB's in on the P-47D. I could share that method but doubt that anybody would be interested in the context of this thread.

In Controls/Options, the bindings for Compass Course show to pairs of duplicated orange lines. This is due to inconsistent parameters of the "value_down" between the "default.lua" files under "\joystick" vs "\keyboard". If you use the bindings for keyboard, the compass ring will therefore rotate slower than if you use the binding for pushbuttons. The attachment shows what it looks like in Controls/Options. Here are the lines in the "default.lua" under "\joystick": {pressed = device_commands.Button_18, cockpit_device_id = devices.CONTROLS, value_pressed = -1.0, name = _('Input.SpitfireLFMkIX.compass_minus'), category = _('Front Dash')}, {pressed = device_commands.Button_18, cockpit_device_id = devices.CONTROLS, value_pressed = 1.0, name = _('Input.SpitfireLFMkIX.compass_plus'), category = _('Front Dash')}, And the lines from "default.lua" under "\keyboard": {combos = {{key = 'C', reformers = {'RAlt'}}}, pressed = device_commands.Button_18, cockpit_device_id = devices.CONTROLS, value_pressed = -0.25, name = _('Input.SpitfireLFMkIX.compass_minus'), category = _('Front Dash')}, {combos = {{key = 'C', reformers = {'RCtrl'}}}, pressed = device_commands.Button_18, cockpit_device_id = devices.CONTROLS, value_pressed = 0.25, name = _('Input.SpitfireLFMkIX.compass_plus'), category = _('Front Dash')}, The values for "value_pressed" are 4 times higher for pushbuttons compared to keyboard. We should not have different values for bindings with the same name, as this produces duplicated orange lines which confuse users. I suggest that the values be made the same, 1.0 and -1.0 should be acceptable.

The file "Throttle - HOTAS Warthog.lua" has special commands for 2- and 3-position switches on the TM-WH throttle. These are functionally different from the related commands in the "default.lua" files under "\joystick" and "\keyboard", but in 3 cases they have the same "names". In Options/Controls they show as pairs of orange lines, which signals an irregularity; but the user does not know what the issue is, and he/she does not why one of these lines can only be bound to the TM-WH throttle and the other line won't work with that controller. Attachment 1 shows what it looks like for the "HOTAS Boat Switch". The lines for the Boat switch in "default.lua" are designed for use with 3 independent pushbuttons: {down = iCommandPlane_HOTAS_BoatSwitchAft, name = _('HOTAS Boat Switch Aft'), category = _('HOTAS')}, {down = iCommandPlane_HOTAS_BoatSwitchCenter, name = _('HOTAS Boat Switch Center'), category = _('HOTAS')}, {down = iCommandPlane_HOTAS_BoatSwitchForward, name = _('HOTAS Boat Switch Forward'), category = _('HOTAS')}, The lines for Boat switch in "Throttle - HOTAS Warthog.lua" are designed for the 3-position switch on the right throttle lever: {combos = {{key = 'JOY_BTN10'}} ,down = iCommandPlane_HOTAS_BoatSwitchAft,up = iCommandPlane_HOTAS_BoatSwitchCenter, name = _('HOTAS Boat Switch Aft'), category = _('HOTAS')}, {combos = {{key = 'JOY_BTN9'}} ,down = iCommandPlane_HOTAS_BoatSwitchForward,up = iCommandPlane_HOTAS_BoatSwitchCenter, name = _('HOTAS Boat Switch Forward'), category = _('HOTAS')}, Both sets of lines use the binding names "HOTAS Boat Switch Aft" and "HOTAS Boat Switch Forward". This is what causes confusion. The lines in "Throttle - HOTAS Warthog.lua" should be named to something like "HOTAS 3-position Boat Switch AftCenter" resp. "HOTAS 3-Position Boat Switch Forward/Center", or whatever else make sense. But the names must be different for these lines. Attachment 2 shows what it looks like for the Pinky switch. It has the same problem as the boat switch, and the bindings for the TM-WH throttle need to be renamed. Attachment 3 shows what it looks like for the Engine IGN/NORM switches (left and right): Both "default.lua" (in "\joystick" and "\keyboard") and "Throttle - HOTAS Warthog.lua" have commands named "Left Engine Oper Ign / Norm" and "Right Engine Oper Ign / Norm", but these commands do not have the same function as you can see in the lines of .lua code. Lines in "default.lua": {down = iCommandPlane_L_ENG_OPER_Ign , up = iCommandPlane_L_ENG_OPER_Norm , name = _('Left Engine Oper Ign / Norm') , category = _('Engine Control Panel')}, {down = iCommandPlane_R_ENG_OPER_Ign , up = iCommandPlane_R_ENG_OPER_Norm , name = _('Right Engine Oper Ign / Norm') , category = _('Engine Control Panel')}, Lines in "Throttle - HOTAS Warthog.lua": {combos = {{key = 'JOY_BTN31'}} , down = iCommandPlane_L_ENG_OPER_Ign , up = iCommandPlane_L_ENG_OPER_Norm_from_Ign , name = _('Left Engine Oper Ign / Norm') , category = _('Engine Control Panel')}; {combos = {{key = 'JOY_BTN32'}} , down = iCommandPlane_R_ENG_OPER_Ign , up = iCommandPlane_R_ENG_OPER_Norm_from_Ign , name = _('Right Engine Oper Ign / Norm') , category = _('Engine Control Panel')}; The lines in "Throttle - HOTAS Warthog.lua" should be renamed. Edit: The original A-10C has exactly the same issues.

I checked this, and I found that there is no change from previous state. If you had ON and OFF separately and/or ON else Off modes for these commands you were probably using a modified "default.lua" just like I do. And if you have not backed your modified file up you've obviously lost these commands. I've posted the added key binds for F/A-18C and other aircrafts 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