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

[DawnTreader777]

I was looking at this:

And I realized that you could do columns, one for ship, one for galaxy map, one for SRV in the amount of space in the "tables", then, instead of color coding you could just have headers on top of the columns on the top table on each side. This would make it easier to read. Keep the colors, but is it possible to lay out the results in actual columns?

 

[Epaphus]

Hi

Love the tool, just got a new HOTAS and going through binding hell trying to work out where I want everything .

I uploaded my bind file and I'm getting a not supported message, reference "wrgemv"

Controllers:
VPC WarBRD-D Base with VPC Constellation ALPHA Prime (Right hand)
VPC MongoosT-50CM3 Throttle

I have the split into 32 buttons mode enabled if that makes a difference.

Please let me know if you need any more details.

Thanks

Epaphus

---

Edit: Worked out how to add my HOTAS setup and submitted a pull request to the EDRefCard project.

In the mean time if anyone uses above controllers I've setup an instance at https://edrefcard.epaphus.uk/ which has support for the above. I've included the outstanding pull requests for Thrustmaster TCA Sidestick and OTA versions of VKB Glad NXT on my instance for people using those devices.

 

[Crackensan]

Please add support for https://www.amazon.com/PDP-Victrix-Wireless-Controller-Playstation-5/dp/B0B9LDPXBF

It registers as a Xbox Controller.

 

[mbulava]

"yypiha" It registers as a Xbox Controller.

 

[Ship Puppet]

This is tool helped me to rationalize bindings across different sets of controls. Thanks!

One thing -- the Color by Type option in the controller bindings uses numbers for both the controller buttons and keyboard. Numbers for the controller buttons make sense for the Extreme 3D Pro. But, it would be super helpful to have the nice keyboard buttons from the keyboard bindings instead of three digit numbers.

 

[Darthtoe]

Could add support for the new VKB STECS Throttle System.

 

[jamestiberiuskirk3]

yypiha "yypiha" im using a vkb evo omni left and vkb evo right and only the right shows with unknown controller at the top

 

[soullessred]

bitjgu. looking for support for the VKB Gladiator Evo

 

[CMD Jack Jackster]

Have twin Alpha constellation setup and added key bindings but when I try to print a reference card on EDRefCard is just comes up with an error saying unknown device? I looked at the device in the binds file and it list it just as a number rather than words like x52 pro etc. but when i checked someone's bindings that do print a card they also had a device listed as just a number?

 

[fourth]

I'm getting xpkmab error code with double VKB Gladiators NXT EVO. Right one is detected correctly, but left one (which is in Omnithrottle configuration) is not detected. Is there anything that can be done in this case?

 

[Feorhhyrde]

Reference toqfcz
Dual VKB NXT EVO Omni throttles. I had a proper ref card for them before but I believe I had the wrong firmware flashed as the art was for an upright stick. When you get to supporting them don't hesitate to just use the line art for the upright config as a placeholder, will translate to the Omni varient just fine.

 

[Doosty295]

Reference: https://edrefcard.info/binds/mzoatz
Issue: Left controller not recognized.
Controllers:

VKB Gladiator NXT EVO Omni Throttle (Left) with firmware VKBsim Gladiator EVO OT L XT2 v2.165​

VKB Gladiator NXT EVO Premium (Right) with firmware VKBsim Gladiator EVO R XT2 v2.165​

 

[Myysty]

Reference: tvmtqv

Issue: Throttle and Joystick not recognized

STECS Throttle System - Standard
Gunfighter IV ‘Modern Combat Edition’ Ultimate - Extended

Thanks

 

[Ascarx]

Reference: xqvujs
Issue: Left controller not recognized
Controllers:
VKB Gladiator NXT EVO Omni Throttle (Left) with firmware VKBsim Gladiator EVO OT L XT2 v2.165
VKB Gladiator NXT EVO Premium (Right) with firmware VKBsim Gladiator EVO R XT2 v2.165

 

[deadsmiley]

Reference: xqvujs
Issue: Left controller not recognized
Controllers:
VKB Gladiator NXT EVO Omni Throttle (Left) with firmware VKBsim Gladiator EVO OT L XT2 v2.165
VKB Gladiator NXT EVO Premium (Right) with firmware VKBsim Gladiator EVO R XT2 v2.165

I just bought this exact same setup and I have the same issue.

 

[PiLhEaD]

Just thought I'd pop by to say thanks (again hopefully) for this super helpful tool!!

 

[Fnord Velkor]

Are "yooze guys" messing with the programming of the VKB EVO sticks? I just default calibrated them and EDRefCard sees them with no issues. See here:

EDRefCard

(Sorry about the Cougar MFDs. I have not remapped the blank ones after reassigning them.)

 

[Arrowroot 66]

Are "yooze guys" messing with the programming of the VKB EVO sticks? I just default calibrated them and EDRefCard sees them with no issues. See here:

EDRefCard

(Sorry about the Cougar MFDs. I have not remapped the blank ones after reassigning them.)

It looks like it's caused by the Omni throttle. The pic of the left hand unit in your link doesn't show it, so EDRefCard seems to be assuming you have the normal base but since your A1 and A3 4-ways have the Up/Down/Left/Right all rotated by 90° you must have fooled it somehow.

FWIW I've only ever done the default calibration but I've got the same results as yooze guys above: the LH controller gives "unknown controller" but the RH one is fine.

My EDRefCard

 

[Helmut Grokenberger]

It's the firmware, or better: The hardware ID differences between different firmwares. My Omni Throttle came with the "normal" firmware and it was recognized by both the VKB software and EDRefCard as the normal left handed stick. Updating the firmware to the OT firmware changed its hardware ID from 231D:0201 (left handed NXT EVO) to 231D:3201 (left handed Omni Throttle), probably to be able to differentiate between OTs and normal sticks via the hardware ID and not just by looking at them - after the update the VKB software identified the left one correctly as an Omni Throttle. Maybe newer OTs come with the newer OT firmware by default. Anyway, the newer USB IDs of the Omni Throttles are not supported by EDRefCard, and from VerticalBlank's post history I'd guess it is not going to happen any time soon.

If you do want to upload your binds file to have it online as a reference, you'd have to edit the file it and change every occurence of the left handed OT's ID (231D3201) to the left handed stick's ID (231D0201). I would guess it would be similar for a right handed OT (I'm guessing the right handed OT will have the ID 231D3200, the normal right handed EVO is 231D0200). But those binds files could then not be just downloaded and used without modification if your Omni Throttle(s) run the newer firmware with different hardware IDs.

 

[Arrowroot 66]

Ok, that edit [231D3201 -> 231D0201] worked (yes, I copied the file first!) Thank you!

As you say, it's a way of getting it uploaded for reference or backup but it won't work for me with those hardware IDs. So next time I change my mind about the throttle keys, I'll just have to remember to make a copy, edit that copy and then upload. Simples!