Page 1 of 3 123 Last
Results 1 to 15 of 37

Thread: EDRefCard - makes a printable reference card of your controller bindings

  1. #1

    EDRefCard - makes a printable reference card of your controller bindings

    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.

  2. #2
    If EDRefCard doesn't know about your controller it will explain how to report that. Adding a new device requires print-quality images or line art of the device that are aligned suitably for attaching call-out boxes to every button and axis.

    It is important that these images be licensed as "free to use, share, or modify". I have had good results from using Google Advanced Image Search with that option selected for the "usage rights".

  3. #3
    Thank you very much for this VB - your hard work is very much appreciated.

  4. #4
    EDRefCard is open source under the MIT licence and the repo is here.

    It is entirely in Python3 and I intend to keep it that way.

  5. #5
    Dude - This is simply amazing. Found it linked in reddit a couple days ago, and just today someone asked how I had my scanner keys bound, and this made it so simple to show and share the binds.

    Question/Suggestion - I like that I can color-code the joystick view, and was wondering if I missed a step in order to generate colors for the full bindings section? In particular just for the modifier keys.

  6. #6
    How about adding Mouse controls also to refcard output?

  7. #7
    +1 for taking this on!

  8. #8
    Am I missing something? I printed my reference card (TM 16000M FCS and TWC 5 throttle) and did not see any of the bindings for the FSS or DSS.

    Also, the web site points to the old forum thread for questions.

  9. #9
    Unknown device reference: uhvjnn

    It's a Virpil T-50 Mongoos Throttle for buttons 1-32, and a Vjoy virtual device using Joystick gremlin for buttons 33+. Dunno if this is even doable from your side, but that's what I'm flying with.

  10. #10
    Originally Posted by Xenoit View Post (Source)
    Dude - This is simply amazing. Found it linked in reddit a couple days ago, and just today someone asked how I had my scanner keys bound, and this made it so simple to show and share the binds.

    Question/Suggestion - I like that I can color-code the joystick view, and was wondering if I missed a step in order to generate colors for the full bindings section? In particular just for the modifier keys.
    Yes, you can colour by modifier keys:


  11. #11
    Originally Posted by Greybeard_LXI View Post (Source)
    Am I missing something? I printed my reference card (TM 16000M FCS and TWC 5 throttle) and did not see any of the bindings for the FSS or DSS.
    Do you have a link for that? So as to save space in the text boxes, the engine supresses what I call "redundant specialisations" -- such as FSS pitch being the same as regular pitch.

    Originally Posted by Greybeard_LXI View Post (Source)
    Also, the web site points to the old forum thread for questions.
    This is in hand.

  12. #12
    Originally Posted by grue View Post (Source)
    How about adding Mouse controls also to refcard output?
    It's conceivable if there's enough demand. EDRefCard can't see what model your mouse is, so it'd be a listing (like the keyboard page) rather than a diagram.

  13. #13
    Hello! Thank-you for your work!!

    I too am having issues with EDRefCard recognizing my CH Controller Setup (Fighterstick, Pro Throttle and Pro Pedals). The reference code is: xritbg

    The Fighterstick commands are showing up on the pro throttle, but nothing else is shown.

    Any assistance would be appreciated!!


  14. #14
    Originally Posted by VerticalBlank View Post (Source)
    It's conceivable if there's enough demand. EDRefCard can't see what model your mouse is, so it'd be a listing (like the keyboard page) rather than a diagram.
    You're a hero! This tool has saved me a crapload of effort, AND it's given me a reason to buckle down on learning python. If I was going to suggest anything it would be a legend on the card somewhere for when you have the controls colored by type.

    Something like:

    Flight
    Multicrew
    SRV
    I don't know what the purple ones are yet

  15. #15
    Originally Posted by b_corvallis View Post (Source)
    You're a hero! This tool has saved me a crapload of effort, AND it's given me a reason to buckle down on learning python. If I was going to suggest anything it would be a legend on the card somewhere for when you have the controls colored by type.

    Something like:

    Flight
    Multicrew
    SRV
    I don't know what the purple ones are yet
    I was trying to reply to the thread, must have hit the wrong link. I'm not too familiar with this forum, sorry!

Page 1 of 3 123 Last