Keyboard and HOTAS Reference Sheet Generator

Status
Thread Closed: Not open for further replies.
The new ED-branded Thrustmaster T16000M FCS HOTAS now has a default bindings file in 2.2, the stick is obviously already recognised but the throttle isn't. The 6-char code is shdvqj.
 
Definitely looking forward to seeing the TWCS Throttle supported. I generated a sheet with the let others see it unchecked and got the message about the 6 character code. Since there is already a report, I see no need to submit a second one.

Good work on this generator. You rock.
 
The new ED-branded Thrustmaster T16000M FCS HOTAS now has a default bindings file in 2.2, the stick is obviously already recognised but the throttle isn't. The 6-char code is shdvqj.

Is there a reference sheet for this yet? I keep getting errors and unknown device. I have the new HOTAS and absolutely love it! upgraded from HOTAS X.
 
Thank you, and a request

So happy with this I could burst - I've got the Saitek X56 and this worked PERFECTLY! I do have one suggestion however - I'd love the option to print out either a blank form based on the binds file for my HOTAS, or (even better?) the option to include the button numbers on the printout. I can now x-ref the binds file and write in what the button numbers are (and extrapolate what's not assigned), but it would be very helpful if the button numbers could be printed on the sheet too. For some reason my joy.cpl will only let me test the throttle, not the joystick, on my Windows 10 (and even that is inconsistent) so it was quite a chore to customize my binds file. Having the button numbers on the printout would help me tremendously.

Thanks for what you have done - this is truly a Godsend utility already!

Best,

DJ
 
Last edited:
I just generated bindings. Nice, but I have two problems:

1. I use T16000 for left hand and binding shows base button bindings on left side, while actually I have them configured on right side.
2. I use quite old Logitech WingMan RumblePad for driving control and it was reported as unknown controller.

My reference is: rayqbu
 
A nice tool. I am impressed that it understands how i use the pinkie button on my joystick for several purposes, including as modifier for other buttons.
.
The only thing which i'd still enjoy would be the possibility to add comments to some of the bindings. The reason for that is that some buttons on my joystick are not bound directly to game functions, but i used the joysticks software to program keypresses.
.
E.g. in this configuration https://www.mcdee.net/elite/binds/fuhrbc?replay=fuhrbc the slider on my X-56 is bound to press the pause button and the pause button is bound to be FA-OFF, so i can use the pinkie button on the joystick for a quick temporary FA-OFF, or use the slider on the throttle and as it keeps pause pressed as long as active, FA stays off till i switch the slider back to the default position. (Also, the two four-ways are similarily bound to do energy management by sending button presses. )
.
Being able to add such small info "Programmed blah blah in joystick software" as comments thus would be awesome, although i guess it's not of high priority. Also, i am not sure how you could prevent vandalism on setups if you allow comments, unless you require registration and a password to allow adding comments. The only thing that could work is to allow to add comments and save the configuration with comments as new (seperate) configuration with its own link.
.
 
Last edited:
Any idea when we're going to get the Thrustmaster TWCS throttle compatible with this? My reference code is nvqmvk

Thanks
 
Last edited:
Greetings all!

First let me say that the work here is AMAZING. In fact, it was the support I have seen here that finally convinced me to take the leap away from my Logitech Extreme 3D Pro to a brand new Logitech G Saitek X-56 HOTAS - which just arrived today.

Unfortunately, I did not realise the magnitude of the task now at hand as I try to set this beast up for use. I was wondering if there is anyone willing to share a copy of their binds file for their x-56 so that I can use it as a starting point for getting mine set up and useable in the game. I have tried some manual work on my own - set up, do training mission, rinse, repeat..but am getting confused as I am being told to use buttons that are not labelled the same on my unit.

If I have read the posts here correctly, I should be able to (after making a backup copy of my binds file) copy/paste the relevant bits from another users binds file and the print the appropriate reference sheet so I can try this bad lad out...maybe even get to where I can manually dock and get rid of my DC :).

Any assistance would be very greatly appreciated..
 
Hi! Thanks again for an awesome tool.

Proud owner of yet another oddball TWCS throttle here :p The code for mine is "kszqun".

Edit: in the binds file the throttle is identified as "T16000MTHROTTLE", eg:

Code:
	<Supercruise>
		<Primary Device="T16000MTHROTTLE" Key="Joy_5" />
		<Secondary Device="{NoDevice}" Key="" />
	</Supercruise>
 
Last edited:
Greetings all!

First let me say that the work here is AMAZING. In fact, it was the support I have seen here that finally convinced me to take the leap away from my Logitech Extreme 3D Pro to a brand new Logitech G Saitek X-56 HOTAS - which just arrived today.

Unfortunately, I did not realise the magnitude of the task now at hand as I try to set this beast up for use. I was wondering if there is anyone willing to share a copy of their binds file for their x-56 so that I can use it as a starting point for getting mine set up and useable in the game. I have tried some manual work on my own - set up, do training mission, rinse, repeat..but am getting confused as I am being told to use buttons that are not labelled the same on my unit.

If I have read the posts here correctly, I should be able to (after making a backup copy of my binds file) copy/paste the relevant bits from another users binds file and the print the appropriate reference sheet so I can try this bad lad out...maybe even get to where I can manually dock and get rid of my DC :).

Any assistance would be very greatly appreciated..

I don't have a X56, but I do have an X55 and one thing I can recommend is to *not* put Boost anywhere in the throttle - put it somewhere in the joystick instead. Ghost presses cost me my first Clipper as it decided to boost right when I was going into a station. Use the buttons and hats on the throttle for anything that would be harmless if it were to activate on its own at any given time. On mine I had thruster control, supercruise, hyperspace, targetting subsystems, landing gear, lights and the various UI navigation controls.
 
Last edited:
I don't have a X56, but I do have an X55 and one thing I can recommend is to *not* put Boost anywhere in the throttle - put it somewhere in the joystick instead. Ghost presses cost me my first Clipper as it decided to boost right when I was going into a station. Use the buttons and hats on the throttle for anything that would be harmless if it were to activate on its own at any given time. On mine I had thruster control, supercruise, hyperspace, targetting subsystems, landing gear, lights and the various UI navigation controls.
.
Not a problem of the throttle per se, but a problem with powering it. Quite often USB ports on mainboards are splitted too far without compensating for it, so they deliver less power than they should, according to specifications. Many devices don't mind that, but the X-55/X-56 is a bit more power hungry than a USB stick, so it runs into problems when specifications are not met. Try to plug it to another USB port or, if you have it available, connect your throttle (and joystick) to a powered USB hub.
.
The other big known problem with the X-55 throttle is that cables wear down, but that does not result in ghost presses, but in buttons not being responsive any more. Wish you luck, that your X-55 is not affected.
.
 
Last edited:
.
Not a problem of the throttle per se, but a problem with powering it. Quite often USB ports on mainboards are splitted too far without compensating for it, so they deliver less power than they should, according to specifications. Many devices don't mind that, but the X-55/X-56 is a bit more power hungry than a USB stick, so it runs into problems when specifications are not met. Try to plug it to another USB port or, if you have it available, connect your throttle (and joystick) to a powered USB hub.
.
The other big known problem with the X-55 throttle is that cables wear down, but that does not result in ghost presses, but in buttons not being responsive any more. Wish you luck, that your X-55 is not affected.
.

Thanks! :)

The buttons on my throttle got really mushy, that's why I decided to get the Thrustmaster FCS. I'm in the middle of figuring out how to map the various buttons, so I can't wait for jgm to implement support. Hey jgm, if you're reading this I will happily be your researcher/tester. I'm in the US Pacific timezone.
 
Apologies for those of you waiting for the new Thrustmaster template. I'm struggling to find a front-on image of the throttle stick. An example of what I mean is shown below in the X-55 template (the image at the bottom):

https://www.mcdee.net/elite/res/x55.jpg

If anyone knows of a high-resolution front-on shot of the Thrustmaster throttle that I can use (so ideally with a plain white background) please drop the URL here so that I can finish the template. Thanks.
 
Apologies for those of you waiting for the new Thrustmaster template. I'm struggling to find a front-on image of the throttle stick. An example of what I mean is shown below in the X-55 template (the image at the bottom):

https://www.mcdee.net/elite/res/x55.jpg

If anyone knows of a high-resolution front-on shot of the Thrustmaster throttle that I can use (so ideally with a plain white background) please drop the URL here so that I can finish the template. Thanks.

I'll try to cull one from the manual PDF. For this throttle, top-down might be best I suspect.

Edit: PDFs of the manual and a button schematic are available here: https://support.thrustmaster.com/en/product/twcs-throttle-en/

Edit 2: Image from Thrustmaster's publicity material:
VNhdwPZ.jpg
 
Last edited:
Apologies for those of you waiting for the new Thrustmaster template. I'm struggling to find a front-on image of the throttle stick. An example of what I mean is shown below in the X-55 template (the image at the bottom):

https://www.mcdee.net/elite/res/x55.jpg

If anyone knows of a high-resolution front-on shot of the Thrustmaster throttle that I can use (so ideally with a plain white background) please drop the URL here so that I can finish the template. Thanks.

A quick image search reveals this one: http://www.mod-your-case.de/include/images/usergallery/img_1463.jpg

There's also the "official" ones from the manual: http://ts.thrustmaster.com/download/pictures/pcmac/TWCS/TWCS_PC_Generic_Mapping.pdf and http://ts.thrustmaster.com/download/accessories/manuals/TWCS_throttle/TWCS_Throttle_Manual_All.pdf
 
Last edited:
Apologies for those of you waiting for the new Thrustmaster template. I'm struggling to find a front-on image of the throttle stick. An example of what I mean is shown below in the X-55 template (the image at the bottom):

https://www.mcdee.net/elite/res/x55.jpg

If anyone knows of a high-resolution front-on shot of the Thrustmaster throttle that I can use (so ideally with a plain white background) please drop the URL here so that I can finish the template. Thanks.


Thanks for these, the problem with them is because they are angled it makes it very hard to fit them on the page in a sane fashion. I played around them but couldn't find a good result. I'll use them if there is nothing else, but would far rather have a straight-on view as it allows the image to be larger and the result clearer.
 
I'm going to go with the angled version for now; it's not idea but it'll do.

Please could you fill out the template at http://www.mcdee.net/elite/res/t16000mfcs.png manually for the *throttle only* and put a link to it here, along with a reference to your binds file uploaded to the reference sheet generator. I'll use the information to map the various controls and automate the process. Thanks.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom