Monash

Hello Ozone Thanks for following up. I have "solved" this issue by recognising that changing bindings in the UI layer can affect existing bindings for modules. I'll admit to not fully understanding the issue, but since I really only wanted to map one key (pause/break) from the UI Layer, and now it seems to be working, I'm leaving well enough alone. Thanks for the tip about how to backup the input folder. Cheers, Monash

A solution appears to be to delete the following file: DCS World OpenBeta\Mods\aircraft\Ka-50_3\Input\ka-50_3\joystick\Joystick - HOTAS Warthog.diff.lua. This fix is suggested in the following forum thread:

This sounds just like the issue I was having and posted about here: EDIT The link posted by Insonia suggests deleting the file "Joystick - HOTAS Warthog.diff.lua" saved in DCS World OpenBeta\Mods\aircraft\Ka-50_3\Input\ka-50_3\joystick. This seems to have fixed the issue! Thank you Insonia. I hope it works for you too. Monash.

Thank you for trying. I'll contact support.

Hi Flappie, I think you might have missed my post from 7:43 AM yesterday when I describe how I have already tried what you suggest. I renamed the Saved Games/DCS.openbeta folder to DCS.openbeta.OLD and launched DCS. This didn't fix the issue. I followed this up with a complete re-installation of DCS. The trimmer still does not work.

I removed the extension and double checked Stick Timmer Mode is set to default, but trim still does not work. I've put the extension back on. I should point out that I am not using a keybind assigned to the joystick for these tests. I'm using the keyboard and the default "T" keybind. I am doing these tests with the heli started up, on the runway, ready to take off.

I tried cleanup and repair, but the issue remains. I (backed up) and deleted the DCS save game folder, completely uninstalled DCS world, confirmed all files from the installation folder were removed, and reinstalled the game and only the BSIII module. Trim still does not work. I can hear the click, but the stick location always returns to center. Edit: The only thing I can think of that changed is the addition of the extension to the stick. I suppose I'll have to remove the extension and see if that fixes the problem. It was a *expletive* to connect the cable so I was hoping to avoid this. But unless you can suggest some other possibility (and if you can please do), I guess I'll have try and see. Cheers.

Confirmed that I am using the correct command.

Hi Flappie, I am using a Thrustmaster Warthog joystick. As I mentioned I have added an extension to the joystick. Stick timmer mode is set to Instant Trim (default). Pedals trimmer and PPR. Pedals override are both unchecked. Note this issue applies to both the BS2 and BS3.

I recently returned to the Ka-50 III module and the trimmer switch no longer seems to work. Previously, I would hold down trim, move the cyclic, release trim, and recenter the cyclic. The control indicator showed the "trimmed" position of the cyclic. I think this was the expected behaviour. Now, however, the trimmer button does not appear "hold" the cyclic in place. I can hear the "click" when clicking the trimmer switch, but otherwise it does not appear to do anything. Any ideas what could be causing this? I recently added a stick extension if that is relevant. Cheers, Monash

Thanks again, this is very helpful to me. You are correct: I am very new to DCS (moving over from IL-2). I think I need to step away from this for a while, take a break, and come back to it tomorrow. Cheers, Monash

Hello LeCuvier Thank you for the explanation re UI Layer vs General. I appreciate you taking the time to help me out. Putting to one side the wisdom of assigning Pause to an MFD button (which works for me because I use the clickable cockpit controls to operate the in-game MFDs), I still do not understand why it shows a conflict with other keybinds when those conflicts simply do not exist (as shown in the screenshots). I investigated "F16 MDF 2.lua" in the A-10C_2 folder you pointed to. I do see the line you quoted in your reply. But this raises a number of other questions for me: 1. Why is that keybinding in the file when it most certainly does not exist in game (because I deleted it in-game). 2. Why is a control for the F16 (which I do not own) of any relevance? I accept it is, but I do not understand why. 3. Why is a control for the F16 included in the controls for the A-10C. 4. Why does any of this make it so complex to set a keybinding for pause in a completely unrelated module? As things stand, I am unable to do something that should be simple: assign pause to a button. Sorry if I am coming across as frustrated. I do appreciate your help.

A follow on question. While still trying to trouble shoot this, I returned to the UI Layer page and tried to set a keybind. But now I get a message saying that if I change things then all changes in the A-10C profile will be lost. Why? I mean, all I want to do is assign "pause" to a button. Does it really have to be this complex? null

lHello, I have a couple of questions regarding keybinding in DCS that have arisen during setting up the F/A-18, but I suspect are issues arising from my ignorance of how the various different categories of keybindings work together in DCS. My issues arose after I purchased and installed the A-10C, which I have loaded up, but now flown yet. What is the difference between the UI Layer and General categories of keybinds? Some items are in both categories, e.g., BDA show/hide. Why? I want to set a button on my (real not ingame) MDF controller to the pause command which is in the UI Layer category. But when I do so, the assignment panel shows that the button I want to assign is already assigned to "Right MFCD OSB 19 (A-10C II) and F10 Theater Map View (General)" This is shown in an attached screenshot. However, as shown in the screenshots, these bindings are NOT set (because I've gone through and removed them as part of trying to trouble shoot this). What is going on?

Perfect. Thank you!