Keyboard and HOTAS Reference Sheet Generator

Status
Thread Closed: Not open for further replies.
Frenotx,
I just wanted to know what your Throttle Hat with say a Up motion puts out to or sends to the Elite control file to cause Head look to look UP? When you clicked just to the right of the Head look UP line in the control file.. what appeared in the "clicked" area when you moved the Hat switch UP?

Dx mode? digital
Or does it send a Keyboard character? Or a script?
Help JGM..

Buzz
 
With the advent of Horizons there are even more bindings to remember, so it's a good time to generate a reference sheet for your own customised configuration.

The reference sheet generator has been updated and is available at http://www.mcdee.net/elite/ It takes a copy of your custom binds file and generates reference sheets for you for both keyboard and HOTAS. Details of how to use it are available on the site.

If you find any problems with the files that are generated, would like another product supported, or have any general comments then please put them here. Thank you, and I hope that you find this useful.

This is a great tool. Thank you. Although I don't need it now I have marked it for future use. I was looking for exactly this a few months ago. Do you have plans on setting this up to work with Star Citizen Or DCS Warthog or anything like that?
 
Frenotx,
I just wanted to know what your Throttle Hat with say a Up motion puts out to or sends to the Elite control file to cause Head look to look UP? When you clicked just to the right of the Head look UP line in the control file.. what appeared in the "clicked" area when you moved the Hat switch UP?

Dx mode? digital
Or does it send a Keyboard character? Or a script?
Help JGM..

Buzz

I use the throttle mouse for head look but use the combined analogue control rather than the separate digital control.

My binds are at http://www.mcdee.net/elite/binds/jgm

I don't use the CH manager for anything other than calibration of the stick.
 
I got it!..

I had put the control commands in the wrong line in the Elite control file. It should have gone into the HeadLookYawAxis and the HeadLookPitchAxisRaw. I use the 4 position Hat switch .. the one with the push in the middle on/off switch. This switch I put in the HeadLookToggle command line. nice.

These commands are set in the CM control software in the "DX mode" for the Hat Switch.

Buzz
 
Mine gives me an error for unsupported device and says to reference "micwvk". The device is that I use a PS4 controller as a bluetooth controller for my SRV. Thanks for the tool, I was literally looking for something like this very recently and this is perfect.

Here, have some rep!

I've added preliminary support for the Dualshock 4, but strongly suspect that I have some of the buttons mapped incorrectly. Please could you try it again now and see if the buttons map correctly, especially the share, options, and PS buttons?

Also, is the trackpad available for mapping?
 
Great tool :) I've used it with the Xbox controller.
I've got a Thrustmaster T.Flight now and it comes up as unsupported. It's the standalone stick rather than the HOTAS.

reference: pnghoj

:)
 
Last edited:
Hi, I have an X52 Pro. Generating the sheet I found blank

Mouse_2 (ToggleFlightAssist)
Pos_Mouse_ZAxis (NextSubsystem Cycle)
Neg_Mouse_ZAxis (PreviousSubsystem Cycle)

they are the small rotary in the rear of the trottle.
 
  • Like (+1)
Reactions: jgm
Great tool :) I've used it with the Xbox controller.
I've got a Thrustmaster T.Flight now and it comes up as unsupported. It's the standalone stick rather than the HOTAS.

reference: pnghoj

:)

I haven't seen this one before. Let me take a look at it and see how easy it is to add it in.

- - - - - Additional Content Posted / Auto Merge - - - - -

Hi, I have an X52 Pro. Generating the sheet I found blank

Mouse_2 (ToggleFlightAssist)
Pos_Mouse_ZAxis (NextSubsystem Cycle)
Neg_Mouse_ZAxis (PreviousSubsystem Cycle)

they are the small rotary in the rear of the trottle.

Can you let me know the reference on the sheet so that I can take a look? Thanks.
 
JGM,
With my last problem out of the way I'd like to solve the next. (grin)
In my Custom file in Elite it shows me using a "ThrustMasterWarthogCombined" when indeed I'm using the T16ooo joystick.

file: http://www.mcdee.net/elite/binds/vivldy

I looked through the Target derived file that controls the stick and don't see a reference to specifying what stick is being used. In target, the controller that's checked is the T16000m. But when I program a stick function in Elite 's Custom file it comes up as being the warthogs stick ... as you can see in the binds file from the above link.

Any idea?

Buzz. AKA.. the continuous problem finder.
 
I haven't seen this one before. Let me take a look at it and see how easy it is to add it in.

- - - - - Additional Content Posted / Auto Merge - - - - -



Can you let me know the reference on the sheet so that I can take a look? Thanks.

this is the output

bindsX52Pro.jpg
 
JGM,
With my last problem out of the way I'd like to solve the next. (grin)
In my Custom file in Elite it shows me using a "ThrustMasterWarthogCombined" when indeed I'm using the T16ooo joystick.

file: http://www.mcdee.net/elite/binds/vivldy

I looked through the Target derived file that controls the stick and don't see a reference to specifying what stick is being used. In target, the controller that's checked is the T16000m. But when I program a stick function in Elite 's Custom file it comes up as being the warthogs stick ... as you can see in the binds file from the above link.

Any idea?

Buzz. AKA.. the continuous problem finder.

I've taken a look at the configuration file and as you say it says that you are using the Warthog. I suspect that TARGET is doing some jiggery-pokery to cause this, but I don't know anything about it so can't give you an idea of how to proceed. Although if you aren't using any of the advanced macroing features you would probably be better off throwing it out and binding directly within Elite.
 
Thanks for looking JGM,

I found a Debug site with CM controllers and told them about what I found. We'll see if anything comes of it..

The reason I used "Target" is to use the commands that the Voice attack software uses.

Buzz
 
It looks as if the generator doesn't handle modifiers for the hat.

I have mapped "Key_LeftAlt" + hat_[<|>|^|v] to powerdistributuion, but it doesn't show up on the stick bindings. The un-modified mappings (thrust and UI navigation) for the hat keys are shown.

Code:
<IncreaseEnginesPower>
        <Primary Device="Keyboard" Key="Key_UpArrow" />
        <Secondary Device="LogitechExtreme3DPro" Key="Joy_POV1Up">
            <Modifier Device="Keyboard" Key="Key_LeftAlt" />
        </Secondary>
    </IncreaseEnginesPower>
    <IncreaseWeaponsPower>
        <Primary Device="Keyboard" Key="Key_RightArrow" />
        <Secondary Device="LogitechExtreme3DPro" Key="Joy_POV1Right">
            <Modifier Device="Keyboard" Key="Key_LeftAlt" />
        </Secondary>
    </IncreaseWeaponsPower>
    <IncreaseSystemsPower>
        <Primary Device="Keyboard" Key="Key_LeftArrow" />
        <Secondary Device="LogitechExtreme3DPro" Key="Joy_POV1Left">
            <Modifier Device="Keyboard" Key="Key_LeftAlt" />
        </Secondary>
    </IncreaseSystemsPower>
    <ResetPowerDistribution>
        <Primary Device="Keyboard" Key="Key_DownArrow" />
        <Secondary Device="LogitechExtreme3DPro" Key="Joy_POV1Down">
            <Modifier Device="Keyboard" Key="Key_LeftAlt" />
        </Secondary>
    </ResetPowerDistribution>

The bindings are in "binds/vukzlk". They are work in progress, so you may want to delete them, as well as the predecessor "binds/bvikjm".
 
Last edited:
I'll have a look and see what I can do to fix that.

Great! Thanks for making the effort - and for making your work available in the first place.

I'm going to be using modifiers a lot in the future to group things more to my liking and in trying to get a much better flow.

I cannot afford one of the fancy HOTAS setups, so I'm working to fit everything, plus the kitchen sink, onto the stick handle (using neither button 7-12, nor the throttle), combined with my old, trusty n52te (remarkably flexible device actually), and modifiers have a major role to play in that. It is looking good, but it will take a while to get a good flow, all while I learn to fly in ED - but that's part of the fun.

(For those of you not familiar with how flexible the n52te really is, try looking up Grendalsh's channel on youtube and watch a few of his instructables)
 
  • Like (+1)
Reactions: jgm
Great! Thanks for making the effort - and for making your work available in the first place.

I'm going to be using modifiers a lot in the future to group things more to my liking and in trying to get a much better flow.

To date I've kept keyboard and HOTAS bindings logically separate in the code. I've tweaked the code so that it will handle the case of mixed bindings; please try it again and see how it goes.

You won't see the modifier show up in the keyboard list, however. That requires a rework of some other areas of the code. I'll see what I can to tackle that in my next major pass.
 
To date I've kept keyboard and HOTAS bindings logically separate in the code.
Understandable - there's probably not that many nuts like me out there :D

I've tweaked the code so that it will handle the case of mixed bindings; please try it again and see how it goes.
Many thanks. It seems to work just fine.

May I suggest placing some text linking the colors to the modifiers?

You won't see the modifier show up in the keyboard list, however. That requires a rework of some other areas of the code. I'll see what I can to tackle that in my next major pass.
Looking forward to that

Good thing I had to test things - I thought I'd changed some of the other bindings already, and would have gotten quite confused, expecting them to work :p

This is the layout I'm using on the n52te. Keys in () are on the numpad. I'll be using modifiers for those keys as well.

n52te_ED_map.png
Oh, the lower thumb key is mapped to enter
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom