Keyboard and HOTAS Reference Sheet Generator

Status
Thread Closed: Not open for further replies.
Great looking tool! It works for my Thrustmaster MFDs, Saitek Rudder Pedals, and Gamepad. I have an unknown controller for my Saitek X65f, reference "vafvyy". Is it possible to still add?

Thanks again,
 
I wonder if it might be possible to make this tool a repository of sorts, i.e. given the controller ID(s) it returns a list of all schemes that match. Just a thought.
 
First and foremost- THANK YOU!!!!! This tool is amazing. I had only wished that I had found it a bit sooner. Just got my x56 (my first HOTAS) and just started playing. Just going through the tutorial was a nightmare because of the lack of information as to what the controls were set to and what each control on the x56. So incredibly frustrating.

At this point I'm still not sure I'm liking how the controls are mapped. I was wondering if there's someplace to find others control schemes?
 
Hi there!

I have a truly legendary piece of Joystick (MS Sidewinder 2) :)
BUT it's not recognized and it said I should reply in this thread with this ID: "yszskv"

Hope that helps!
Thanks for your work!
 
It says unknown controller detected. Referece is sreefb. I'm running the Logitech Extreme 3d Pro, Saitek cyborg evo, and a steam controller for the SRV.

Great work with this and EDDI
 
Hi Jim,

I have an unknown controller. The reference is vszvxn . It's an XBox One Elite controller. Hope that helps.

I've put the basic configuration for this controller in place, but it assumes that the configuration is the same as that of the other XBox controllers. Please give it another go and let me know if it looks okay.

- - - Updated - - -

Hi there!

I have a truly legendary piece of Joystick (MS Sidewinder 2) :)
BUT it's not recognized and it said I should reply in this thread with this ID: "yszskv"

Hope that helps!
Thanks for your work!

It says unknown controller detected. Referece is sreefb. I'm running the Logitech Extreme 3d Pro, Saitek cyborg evo, and a steam controller for the SRV.

Great work with this and EDDI

I don't have enough information on the very old sticks like the Sidewinder and the Cyborg Evo, I'm afraid. The Steam Controller is a different problem: due to its configurability it is impossible to generate a correct reference sheet from just the Elite bindings.
 
This is great! Have you considered revisiting displaying mouse binds as well? I know most users probably leave them at the default, but I think anyone with a mouse equipped with extra buttons makes critical use of them. For instance, my mouse has descent on the thumb button (ascent on spacebar), shift+MMB deploys landing gear, mousewheel forward sets throttle to ahead half, backwards to reverse half, and MMB itself swaps yaw and roll when held. Clicking the MMB left and right deploys cargo scoop and weapons respectively, but those inputs register as keyboard inputs so it wouldn't show up anyway.
 
Last edited:
The tool worked great, and still works great. But it is not compatible with the bindings from Elite: Dangerous 2.3

Funnily enough I'm working on them now. They should still work fine, but some of the names might look a little strange as they'll be internal FD names. I also want to provide categories for commander creator, camera etc.

Is there a specific issue you've found?
 
Hi jgm,

found a bug :p

Possibly related to using the "little finger wheel" on a HOTAS 16000 throttle for Sensor Range setting, the webserver throws up a list of Python error messages which I wouldn't claim to understand, but at the bottom of it all I see this (hopefully it's relevant, otherwise I can give you the full error message or my bindings file):

Code:
context = <wand.drawing.Drawing object>, context.font undefined, text = {'Group': 'Misc', 'Style': None, 'Text': 'Sensors range'}

TypeError: 'NoneType' object is not subscriptable
      args = ("'NoneType' object is not subscriptable",)
      with_traceback = <built-in method with_traceback of TypeError object>

----

Update: "little finger wheel"/sensor range confirmed - unmapped the wheel from sensor range, and the HOTAS sheet generator works again
 
Last edited:
Hi jgm,

found a bug :p

Possibly related to using the "little finger wheel" on a HOTAS 16000 throttle for Sensor Range setting, the webserver throws up a list of Python error messages which I wouldn't claim to understand, but at the bottom of it all I see this (hopefully it's relevant, otherwise I can give you the full error message or my bindings file):

Code:
context = <wand.drawing.Drawing object>, context.font undefined, text = {'Group': 'Misc', 'Style': None, 'Text': 'Sensors range'}

TypeError: 'NoneType' object is not subscriptable
      args = ("'NoneType' object is not subscriptable",)
      with_traceback = <built-in method with_traceback of TypeError object>

----

Update: "little finger wheel"/sensor range confirmed - unmapped the wheel from sensor range, and the HOTAS sheet generator works again

Please could you PM me a copy of your binds file with the sensor range mapped so that I can see exactly what's wrong here? Thanks.
 
Please could you PM me a copy of your binds file with the sensor range mapped so that I can see exactly what's wrong here? Thanks.

It's probably that bogus V-axis (should be U-axis) issue again re the little wheel on the Thrustmaster TCS Throttle.

It's not like I filed a bug report on that with FD in the last beta: oh wait I did. And I just diffed the default bindings for the TCS HOTAS in the new beta and lo, it isn't fixed.

The sad thing is that if FD would only adopt proper issue-tracking and change-control procedures, like any grown-up writing software in 2017, they might be gaining ground in fixing such things. Instead, it's just the ostrich school of project mgt.
 
The reference sheet generator has been updated with the 2.3 controls, including the new camera mode and multicrew. Please let me know if you find any problems with it; thanks.
 
Hi JGM,

Any chance for adding the Saitek X-65F controller?
"You have a device that is not supported at this time. Please report details of your device by following the link at the bottom of this page supplying the reference "bgvutt" and we will attempt to add support for it."

Thanks,

Cmdr Takesix
 
Hi JGM,

Great to see you still maintaining your utility. While you're plugging away at an update to support 2.3, would it be possible for you to look at supporting the Saitek X45 controller? I've supplied you with controller reference images in the past.

Reference "lebdto" on your site.


Also, another suggestion, how about adding an index (by controller type) to your website to allow people to browse public profiles? At the moment, unless I've missed something, the only way to see someone elses' profile is if they send you a link to it.

Keep up the great work :)
- Micha.
 
What a wonderful tool! Many thanks for making this available!

I got this message:

> You have a device that is not supported at this time. Please report details of your device by following the link at the bottom of this page supplying the reference "okqujm" and we will attempt to add support for it.

I have an ancient Microsoft Sidewinder USB joystick attached: No hat, no Z-axis rotation -- just the X-Y axis stick, 7 buttons, and a throttle dial.

Cheers,

T.

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.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom