Keyboard and HOTAS Reference Sheet Generator

Status
Thread Closed: Not open for further replies.
This uses a different ID to the ones I have seen before. I've added it to the list so it will show the controls, at least. Still somewhat unsure about the grouping system so I'd be interested in hearing how well what you are seeing maps to reality.

I initially tried using a genuine Xbox360 controller and got the result I mentioned. I changed over to a Razer Sabretooth controller with the same results. Thats the bind file I sent. With getting the same result with both , also both seem to be identified as the same in ED's controller setiings I didn't think it would matter. I can use either for any tests.
 
Wow! Awesome. This needs to be stickied imo.

Am thinking of getting a HOTAS thingummybob next year after I build myself a HOTAS/Steering Wheel mount.
 
Thanks for the information. I've added it to the webpage so give it a shot and let me know how it goes.

Looking pretty good! I've just tried it with my current bindings and found two small bugs: the click button on the mousewheel and the red button on the joystick are not handled properly. In my binds I have the joystick button set up as UI select and the wheel click button as UI back. This is what the relevant section looks like on my binds file:

Code:
 <UI_Select>
  <Primary Device="SaitekX55Throttle" Key="Joy_22" />
  <Secondary Device="07382218" Key="Joy_28" />
 </UI_Select>
 <UI_Back>
  <Primary Device="SaitekX55Throttle" Key="Joy_20" />
  <Secondary Device="07382218" Key="Joy_25" />
 </UI_Back>

This is what currently looks like on the generated page:

sidepanelcontroldeck bug.jpg

And this is what it should look like:

sidepanelcontroldeck proposed fix.jpg
 
This uses a different ID to the ones I have seen before. I've added it to the list so it will show the controls, at least. Still somewhat unsure about the grouping system so I'd be interested in hearing how well what you are seeing maps to reality.

For spaceflight only yaw, but I do the whole SRV driving with them.
 
Looking pretty good! I've just tried it with my current bindings and found two small bugs: ...

Sorry didn't realise that the scroll wheel clicked. I've updated the template with this information so it should now generate correctly. Give it a shot and let me know how it looks.
 
I initially tried using a genuine Xbox360 controller and got the result I mentioned. I changed over to a Razer Sabretooth controller with the same results. Thats the bind file I sent. With getting the same result with both , also both seem to be identified as the same in ED's controller setiings I didn't think it would matter. I can use either for any tests.

Okay the Sabretooth and XBox pad should be picked up correctly now. Give it a shot and if it doesn't work please let me know the URL of the binds (should be shown at the top of each page) so that I can take a look and see what's going on. It does appear that there are a lot of controllers out there with different IDs that FD haven't mapped, though, in which case I'll need to keep adding the mappings myself as I run in to them.

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

For spaceflight only yaw, but I do the whole SRV driving with them.

Are the settings complex enough that you feel a reference sheet is required? I could add pedals in without a huge amount of effort, but I haven't seen pedal controls that are anything other than obvious so thought that a reference sheet would be of minimal use.
 
Personally I am not too bothered about adding rudders to the reference sheet. But if you do want tp put them in for completeness I have both CH and Saitek rudders and would be willing to offer any binds using them later today if that helps.
 
Sorry didn't realise that the scroll wheel clicked. I've updated the template with this information so it should now generate correctly. Give it a shot and let me know how it looks.

Looking much better! Just one left... the scroll wheel is labelled up-down/left-right/click when it should be up/down/click. The previous iteration had the correct up/down icons. Also, this one's a nitpick so feel free to ignore it :) : the text inside the tables for the the side panel captions is closer to the left than the similar text for the X55 reference sheet (ie the grid left margin seems smaller for the side panel than for the X55).
 
Last edited:
Looking much better! Just one left... the scroll wheel is labelled up-down/left-right/click when it should be up/down/click. The previous iteration had the correct up/down icons. Also, this one's a nitpick so feel free to ignore it :) : the text inside the tables for the the side panel captions is closer to the left than the similar text for the X55 reference sheet (ie the grid left margin seems smaller for the side panel than for the X55).

Thanks for pointing this out. I've fixed the incorrect labelling of the scroll wheel.

And yeah, the text is sitting a little close to the left at the moment. I need to make a few more tweaks to the existing templates at which point I'll be able to add a margin across the board.
 
Okay the Sabretooth and XBox pad should be picked up correctly now. Give it a shot and if it doesn't work please let me know the URL of the binds (should be shown at the top of each page) so that I can take a look and see what's going on. It does appear that there are a lot of controllers out there with different IDs that FD haven't mapped, though, in which case I'll need to keep adding the mappings myself as I run in to them.

Just got chance to try and they are working great with both the original Xbox360 controller and also the Razer Sabretooth. I haven't fully checked everything yet but the controllers are being recognised now. I also got hold of an Xbox One Elite controller today and can confirm that also works with the sheet generator. I'll give them a good test to see if there is any problems.

Brilliant work. Thanks.
 
Just had another look, the saitek side panel reference sheet looks great now. Thanks for all the hard work, your page is incredibly useful when trying out new layouts.
 
I like this idea!
I'm getting a 500 Internal Server Error after uploading the custom .binds file though.
The error occurs on scripts/bindings.py.
 
I like this idea!
I'm getting a 500 Internal Server Error after uploading the custom .binds file though.
The error occurs on scripts/bindings.py.

Sorry I was doing a bit of maintenance on the server, it should be back again now.
 
One thing I just noticed on the X55 reference sheet, but which is probably on all of them: in Horizons FD renamed the Radar Panel to Role Panel - that's the lower panel that shows the SRV info in it. Unfortunately I don't know if the rename is a 2.0 only thing or if 1.5 also has the new name for the lower panel.
 
Well I can give it a shot. Could you send me your binds file along with the details of your pedals (make/model) and their configuration (which controls do what) and I'll see if I can add it?

How do I best do that, other than sending them as plain text in a PM ? I have the CH pro pedals. Main axis is bound to ship yaw and SRV left/right steering. Right toebrake is accelerate SRV, left toebrake is decelerate SRV.
 
Last edited:
  • Like (+1)
Reactions: jgm
How do I best do that, other than sending them as plain text in a PM ? I have the CH pro pedals. Main axis is bound to ship yaw and SRV left/right steering. Right toebrake is accelerate SRV, left toebrake is decelerate SRV.

Either PM me your custom.binds or upload it to the website and send me the reference (which should show up on the pages in the top-left).
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom