LeCuvier

It's always been like this: You need to drop the bombs first, and then jettison the bomb rack (or jettison the bombs with the rack). Now, if your rockets switch is in the "ON" position you can fire the rockets by pressing the Weapon Release switch. We have only one pushbutton for bombs and rockets. And as long as the bomb rack is present, pressing the weapons release button will not release the rockets. Personally I have no issue with this because I will always want to drop my bombs before anything else, because their mass and drag make the FW-190 an easy target for fighters. However, having to jettison the bomb rack makes little sense to me as this is somewhat valuable hardware and the resource-strapped Reich could not really afford throwing it away. Whatever ED will do or not do, this situation does not prevent you from using rockets.

The LUA edit @scoobie provided still works for the Mosquito. It works generally for modules where the line of .lua code for the trim command has something like "value_down = 1.0". In the A-10C (both versions) that's not the case. If you have questions about the A-10C please post them under the related sub-forum, "Controller Questions and Bugs"

We have a very recent statement from @Flappie that this will be fixed in the upcoming OB update.

This must be frustrating! I cannot believe it's the game controllers themselves. A lot of people have experienced erratic behavior of their game controllers because they were connected via cheap USB hubs that draw power from the PC via their USB feed. Game controllers should be connected directly to the PC, or via powered USB hubs.

I thought it could be done with the MIC hat on my throttle, but that switch cannot activate two contacts at the same time. So I just bind the APU Start switch on my TM WH throttle to "Water injection". That switch stays in the ON position until I flick it back OFF, so I don't need the "Lock" toggle. Not ideal, but it works. I did try an addition to "default.lua" and that worked most of the time, but that wasn't good enough.

I'm not the greatest expert in this matter; but I have done a few setups that work, and decided to document the steps in a structured document. I posted it here: https://forums.eagle.ru/topic/263336-multi-monitor-set-up-beginners-guide/#elControls_4580247_menu

@saburo_cz: I have bound the lock too; but it seems to me that water injection continues even though I never activate the lock. Have you ever seen water injection stopping when you hadn't locked it? Ignore my question! I have bound the water injection button to the "APU START" switch on my TM WH throttle so it's as if I kept my finger on the pushbutton forever.

As the localization is currently broken you have to look for the "internal" command names. This one is "Input.P47.nos". Fortunately I bound the commands before this bug appeaered. ED has stated that they treat this bug as high priority. But no deadline published. If you need more help with this just note the commands you're looking for.

I re-calibrated the joystick and now it seems ok

There is a Radiator Axis command for the TM Warthog throttle, and we could copy that command to the "default.lua" so it could be used for other HOTAS devices. But unfortunately the command doesn't work at all. It's bugged.

No problem. We don't neeed to re-invent any wheels, just use existing wheels in a different manner. The file "Throttle - HOTAS Warthog.lua" contains the two lines below for use with the 3-position flaps switch on the TM Warthog throttle: {down = iCommandPlane_FLAPS_UP, up = iCommandPlane_FLAPS_MNR_from_UP,name = _('Toggle Flaps Up'), category = _('Systems')}, {down = iCommandPlane_FLAPS_DN, up = iCommandPlane_FLAPS_MNR_from_DN,name = _('Toggle Flaps Dn'), category = _('Systems')}, The 1st line says "when the bound switch goes to ON, retract the flaps to UP, and when it goes to OFF extend them to MVR position". The 2nd line says "when the bound switch goes to ON, extend the flaps to DN, and when it goes to OFF retract them to MVR position". So we want to implement 4 commands with 3 pushbuttons: RETRACT, EXTEND FULL, EXTEND to MVR, RETRACT to MVR. The 3 lines below do that: {down = iCommandPlane_FLAPS_UP, name = _('Set Flaps to UP'), category = _('Systems')}, {down = iCommandPlane_FLAPS_DN, name = _('Set Flaps to DOWN'), category = _('Systems')}, {down = iCommandPlane_FLAPS_MNR_from_DN, up = iCommandPlane_FLAPS_MNR_from_UP, name = _('Set Flaps to MNR'), category = _('Systems')}, The 1st two lines are obvious. The 3rd line is just a little bit unusual. It says "when the bound pushbutton is pressed retract the flaps to MVR position, and when it's released extend them to MVR position. You can see that when you use the pushbutton bound to the 3rd line: If your flaps are UP and you push & hold the button, nothing happens. Only when you release the buttons the flaps will extend to MVR. If your flaps are DN and you push the button, the flaps will immediately retract to MVR. When you release the button nothing happens. Notes: 1. I used names that are distinctly different from the existing flaps commands. You can use different names; but they must be different from existing names, and they should be distinctly different to avoid confusion with existing commands. 2. The 3 lines of code should be added to "default.lua". If however you use the Saitek X52 Pro Flight Controller then you need to add them to the "Saitek X52 Pro Flight Controller.lua". 3. You know probably that update or repair restores the original files, so make sure you back up your modified file! 4. I tested the new commands with pushbuttons on my DSD button box and they worked fine. If you get stuck I will help as best I can.

@Art-J: thanks for your feedback! I have now deleted the sub-folder for P-47D-40 and that does not make any difference. I use a VIRPIL base with a TM WH grip, and the Jug is the only aircraft behaving differently in 2.7.8. Unless some other people experience the phenomenon, I can only hope that some future version will fix it just by good luck.

So I re-named the config subfolders under Saved Games, restarted DCS OB, re-created the bindings for basic flight axes and trim POV bindings, and re-launched my test mission. In my test mission I fly a P-47D-40. But DCS only created a subfolder for the P-47D-30. And what's worse: It's now impossible to trim her pitch-neutral. For the time being i'm done with this thing. She makes a nice target for my Hun fighters.

@Barrett_g No, I have no double binding on my axes. And the button bindings are not messed up. I just checked all my bindings. @Art-J No, I have no FFB stick. I will rename my saved games config subfolders for the 2 jug versions to see if the culprit is there.

@Art-J: thanks for the hint, I corrected the title. I have backed out all mods (with OvGME) and ran a Repair (slow). The problem is still there. I have to trim almost fully tailheavy (see screenshot) in order to achieve horizontal flight without pitch input. I attach a screen copy. This is in a free-flight instant action mission, and no mods in the system. (Anyway, I have no mods that affect flight behaviour. The mod I mentioned simply allows me to set a trim axis to a pre-determined value by pushing a button.) Flaps and undercarriage are retracted and the aircraft has no payload. And I use the latest 2.7.8 version. So what could make her so excessively nose-heavy? One might think of a mis-calibrated joystick; but then I would have similar problems with Mosquito, Mustang, Spit, Bf-109 and FW-190 and that's not the case.

Background: When the jug's mission starts airborn, the nose goes down immediately and you have to trim the elevator heavily for horizontal flight. That makes instant action missions difficult as the bandit tends to be shooting at you berfore you are done trimming. So I created a new key command that sets the elevator trim to -0.4 (40% tail-heavy) when I push the button. And that worked satisfactorily for a while. But now, with version 2.7.8, I had to change my custom command to -0.85 (85% tail-heavy!) in order to fly horizontally without heavy pitch input. This indicates to me that the aircraft has become significantly more nose-heavy, to a degree that seems unrealistic to me. Shouldn't the aircraft be balanced so that it can fly with elevator trim near neutral?

under "...\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts" in "clickabledata.lua" you find "device = devices.ENGINE_INTERFACE" and in "devices.lua" you find "devices["ENGINE_INTERFACE"] = 4"

Because of a bug in 2.7.8 many commands are not correctly localized. The Throttles bindings are in these 3 lines: - Throttle Port Slider - Throttle Slider (selected engine) - Throttle Starboard Slider

glad to hear that you got it sorted!

Yes, and as I wrote in my post above you should make the same changes in both "default.lua" files to avoid duplicated orange lines.

@Funflite: I suspect you copied & pasted the last 2 lines of code from my post. I just see that I lost some characters when I copied & pasted from my file to the forum. And if you pasted that into your file that would have corrupted it. Here are the full lines: { pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.1, name = _('PITCH TRIM Wheel - NOSE UP'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, { pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.1, name = _('PITCH TRIM Wheel - NOSE DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, Anyway, as I said, you should simply overwrite the values in the original lines. If you prefer to copy & paste the modified lines, you must previously either delete the original lines, or inactivate them by inserting two hyphens ("--") at the beginning of the lines. Also, don't use something like Word. Use Notepad++ or equivalent! And, I apologize for my negligence.

The management of key bindings is certainly not a discipline where ED excels. I would go as far as calling it a mess. I would gladly spend some unpaid time to help them clean it up. But ED is not even good at picking up the many improvements some of us have posted. I have added bindings to every module I own, and I have optimized many settings like trim values etc that change too fast. I therefore have to use OvGME to back my changes out before, and back in after an update. With OvGME the task becomes quite manageable for me. But for the newbies that's an additional complexity most of them would rather avoid.

I don't know what you did. If you had simply overwritten the original values with smaller values, this kind of problem would never happen.

This kind of mods passes IC. No need to re-bind anything except the commands you have just modded.

In the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" , look for these lines below "-- Manual Trim Panel": {pressed = control_commands.RollTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.3, name = _('ROLL TRIM Wheel - L WING DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.RollTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.3, name = _('ROLL TRIM Wheel - R WING DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.3, name = _('PITCH TRIM Wheel - NOSE UP'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.3, name = _('PITCH TRIM Wheel - NOSE DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.YawTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.3, name = _('YAW TRIM Knob - L/CCW'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, {pressed = control_commands.YawTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.3, name = _('YAW TRIM Knob - R/CW'), category = {_('Left Console'), _('MANUAL TRIM Panel')}}, The original lines have lots of tabs after the "{" which I removed as they have no function and take too much space. You can reduce the "value_pressed" parameters and that will make the trim value change more slowly. I only changed the pitch trim: {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = 0.1, name = _('PITCH TRIM Wheel - NOSE UP'), category = {_('Left Console'), _('MANUAL TRIM Panel')}},-- modified value_pressed from 0.3 to 0.1 {pressed = control_commands.PitchTrim_ITER, cockpit_device_id = devices.CONTROL_INTERFACE, value_pressed = -0.1, name = _('PITCH TRIM Wheel - NOSE DN'), category = {_('Left Console'), _('MANUAL TRIM Panel')}},-- modified value_pressed from 0.3 to 0.1 You obviously have to bind your POV hat to the modified commands. Personally, I use the "normal" trim commands for aileron and rudder (like "TRIM Button - LEFT WING DOWN") as we have the luxury of two sets of trim commands (not counting the axis commands). Notes: 1. you need to make a backup copy of the modified file as updates and restores will restore the original file. 2. you should make the same change to the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard" in order to avoid getting duplicated orange lines in Options/Controls.