imacken

Sadly, still no good news after almost a year. Very disappointing that this apparently simple fix has not been implemented yet.

I believe it's 'Saved Games\DCS.openbeta\Kneeboard\AH-64D_BLK_II'. Doesn't get created as default, for me anyway.

Sure, here is one of the axis and the button tabs.

No, it is not, sadly. Really don't know what we have to do to get this simple fix made.

Interesting. I’ve never used multiplayer.

I assumed it would be a place to set a common bind for all modules, but it doesn't seem to be. For example, I set the F1 cockpit view to a button under 'General' - after removing all my individual binds for it - and it doesn't work. So, I'm wondering what this category's function is.

Windows device limit? I thought it was over 100 per USB controller.

An increase of a few pounds after all this time is not unexpected. Worth it for the quality of their devices.

My experience is very different. I love the thumb wheel, and one ‘click’ activates the button both up or down for me. It can also be configured as an axis, and as such, it can be used as buttons or axis for different modules, so answering the OP’s question on that.

I'll just use a modifier button - I already use 2 - on the 5th for the 6th button.

Yes, from people much more knowledgeable than me, I believe it is a very trivial fix, which makes this (and the same on Marianas) very frustrating. Still, BN has given the team a bump on this, so hopefully, it won't be much longer.

What about a bind for 'hide stick'? Don't tell me that's already in game as well!

Already got one of these Multi-Function Button Box - Total Controls Just couldn't see the HUD brightness as I was being an idiot, just searching for HUD or brightness! All good now.

Wow! After all this time, I never even noticed that! Thanks a lot.

Does anyone know how to define a bind for input to lua files (or injection by Quaggles mod) for the HUD intensity (brightness) rocker switch?

Is there any way to get a bind for the HUD brightness/intensity in the A-10C?

Firstly, thanks for this. These additional axes make all the difference! Can I just ask, are you familiar with Quaggles Injector Mod? This is a life saver and can be found here Basically, the problem with applying changes to the default.lua files in the DCS install folder is that the originals get overwritten. Now, that doesn't matter if there are no changes, but when changes occur, and they do quite regularly, things can get messed up and you have to redo the modded files. If you use Quaggles injector, then all your modded lua files sit in a folder structure within Saved Games, and never need to be touched after updates, etc. from the devs as they just get injected into the default.lua files in the install folder. I spent about an hour getting the mods here into separate files (after help with a mistake in the syntax fixed by @Munkwolfin the thread above) and all are working nicely.

Nice one! That was it. Thanks a lot.

I love this mod as it saves messing with the install folder luas. I've had it working OK to inject some keyboard commands, but today I tried to add in some axis commands to the F-14 and keep getting errors - obviously down to my total lack of skill - in the DCS log file. Can someone look at the attached and tell me what I should be doing? The keyCommands bit has always worked OK, but adding in the axisCommands has messed everything up. Any help appreciated. default.zip

Same here. Works a treat!

Thanks a lot for all your useful input here, guys. I'm glad I wasn't going mad! I'm going to study this in more detail now.

Yes, but that doesn’t really help with your issue. Encoders are not good for things like radar antenna. As button-to-axis they work well for things like HUD brightness or HMD brightness. As axes they can work for radar antenna, but not so well, as the range constantly goes up or down, depending on which you have chosen, when you do one click and then you have to one click in opposite direction to stop it. I personally use the up/down buttons on the hat under the 2nd finger for radar antenna. re zoom, I would highly recommend the ‘conventional’ axis, i.e. the z axis under the 3rd finger. It works perfectly for that purpose.

Sorry to be pedantic, but how can it be a pitch reference on the ladder when it’s not at zero in level flight?

Ah ok, thanks. What is the point of those wings then?

I don't ever fly the F-14, but I thought I'd give it a quick try tonight, and apart from not being able to get the auto-pilot working, level flight seemed odd. Do the attachments look right? I mean when the the velocity vector is level, the vertical velocity is showing quite a big negative value and level flight shows the velocity vector higher than I would expect. Sorry about the basic question!