Release EDRefCard - makes a printable reference card of your controller bindings

Status
Thread Closed: Not open for further replies.

Brammmers

Brammmers
Thanks @Downslide, are the attached correct?
mark-kb.png
mark.png
mark-t1600.jpg

J
 

Imagix

I
Brammmers said:
That's ok... Code handles devices 0/1 already by the looks of it.

Will need to see a sample binds file too to check out and test with.

J
Click to expand...
The code seems to assume that all of the 0/1 bits are assuming that the two devices are the same device. Where in this case, the two are very different layouts. The 0 device has 5 axis (two throttles, an analog dial, and an analog stick) plus a number of buttons, where the 1 device only has buttons.

Anyway, I've put up some code at https://github.com/Imagix/EDRefCard/tree/vkbstecs for the button layouts. The coordinates are all wrong and the refcard images are works in progress. But the bindings.py now can recognize if the deviceIndex represents a different device or not. And the bindingsData.py at least lists the right buttons (what they map to on the hardware is in the comments next to each line).

All assuming that it is an as-shipped STECS. I don't know what happens if you'd physically moved any of the buttons or hats (or replaced them).

Edit: I agree.. the code could use some TLC. Update it away from the cgi module as that's deprecated, properly type annotate everything, etc.
 

Brammmers

Brammmers
OK, I'll combine that with my local codebase. I really need to sort out a git repo for this! :)

I'm tinkering with dry-ing the code out for now, and deduping the multiple copies of devices held in the bindingsdata py file. I've also moved the controls definition to it's own file as I got fed up scrolling past it - and it's a relevtively static item (until FDev add some new gameplay controls).

Once that's done, I'll look at the device IDs thing.

Can I grab a copy of your binds file to test with please?
 

Imagix

I
Attached. Now, I don't have something bound to every button. But I have something bound on each device. (Renamed .binds -> .txt so the forum would let me attach it)
 

Attachments

  • HCS VKB Gunfighter Pro + STECS.4.0.txt
    68.1 KB · Views: 121

Brammmers

Brammmers
I've made a repo in GitHub (will share link when I've polished things), found the old pull requets and merged them in by hand (not hard).

@Helmut Grokenberger you're in luck, someone did the VKB OTA profiles back in 2022 - I've merged them...
left-ota-helmut.jpg
 
Last edited:

Brammmers

Brammmers
@Imagix as I was quite a ways ahead of Richard's repo anyway, so I created a new one here: https://github.com/brammmers/edrefcard2 rather than do a pull request.

Your changes look straightforward, would you like to do a PR off my repo (as all other pull's have now been merged into it) or I can manually create a branch and copy your changes across.

That repo is a WIP (e.g. contains private IPs for hostnames etc.) but that can be fixed-up once hosting has been sourced.

I've also started an idea at line 69 in bindingsData.py on how to de-dupe the co-ords structure to make it more maintainable.
 

Imagix

I
Brammmers said:
@Imagix as I was quite a ways ahead of Richard's repo anyway, so I created a new one here: https://github.com/brammmers/edrefcard2 rather than do a pull request.

Your changes look straightforward, would you like to do a PR off my repo (as all other pull's have now been merged into it) or I can manually create a branch and copy your changes across.

That repo is a WIP (e.g. contains private IPs for hostnames etc.) but that can be fixed-up once hosting has been sourced.

I've also started an idea at line 69 in bindingsData.py on how to de-dupe the co-ords structure to make it more maintainable.
Click to expand...
Ok, I've put up a PR for the necessary changes. I've added blank pages (.jpg and .svg) just so that it has anything to display at all.
 

cgar07

C
VerticalBlank said:
Do you confuse your lights with

your landing gear? Or maybe you've

just splurged on a new HOTAS and

are looking for a decent control set?



Either way, EDRefCard

has your back!

​

EDRefCard is a website that can take your custom bindings file and generate a beautiful printable reference card for both your keyboard and controller, be it a gamepad, joystick or HOTAS.

The reference cards are high-resolution for printing, and can optionally be filtered by control group and/or colour-coded by control group or modifier key -- yes, bindings that use modifier keys are fully supported!

You also have the option to save your bindings, which can be useful both as a backup and to sync across more than one computer. Saved bindings are public and browsable via a (currently rather primitive) listing.

EDRefCard will also warn you of the slip-up of binding an analog axis to a digital input when there is an analog input available.

While there is currently no way to upload the bindings files from a game console, I do always maintain the game's default bindings schemes on the site, currently under names starting "3.3 default", and those include the standard XBox and PS4 schemes.

In case you were wondering, yes EDRefCard is the successor site to the reference card generator originally written by CMDR jgm, handed over with his blessing. The old thread is here.
Click to expand...
Can you please add the

VKB STECS Throttle System - Mini Plus​

 

Attachments

  • STECS Throttle System - Mini Plus front.png
    STECS Throttle System - Mini Plus front.png
    649.5 KB · Views: 70
  • STECS Throttle System - Mini Plus rear.png
    STECS Throttle System - Mini Plus rear.png
    611.2 KB · Views: 74

Nismerf

N
So I just set up my kvb NXTEVO omni throttle setup. When I went to create the card, it said the omni throttle was not supported, is there a trick?
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom