Discussion EDRefCard v1.4+ - new hosting, new maintainers (the follow-on to "EDRefCard - makes a printable reference card of your controller bindings")

Can you reupload mine? For the X56. Should be CMDR-Christian-117's slightly edited binds or something like that, but it has my name, and there's two, please reupload the newest one I had, I just had to reinstall my os and don't have my bindings now T-T
If you have the unique reference code I can do it, otherwise I'd be searching all the files and there's thousands!

J
 
If you have the unique reference code I can do it, otherwise I'd be searching all the files and there's thousands!

J
I hope its somewhere in that pic, idk if its the yobcuw thing
 

Attachments

  • WhatsApp Image 2024-12-23 at 19.13.11_ea9d8eb5.jpg
    WhatsApp Image 2024-12-23 at 19.13.11_ea9d8eb5.jpg
    256.5 KB · Views: 39
Thanks for this.

The turtle has a touchscreen I believe, which will make supporting this device non-trivial.

Can't put a timeline on it at the moment.

J
I'd like to second the Turtle Beach VelocityOne FlightDeck as well.

Having said that, I would suggest simply not supporting the touchscreen element because it would be a major project to do so. The screen is entirely customizable - you can create up to 3 "panels", with each containing 3 rows of buttons (first row has 3 spaces, then the next 2 have 5 spaces). You can then place momentary buttons, toggles, or a dial in any of those places (the dial takes up 2 stacked vertically). You'd have to determine how many panels, and what is in each space before you could do anything else.

The one upside is that all the buttons and toggles simply map to keyboard inputs, though the default layout seems to be sequential across the keyboard and wrapping to the next line.

For example, here is a single panel. The top row and the first 2 buttons in the 2nd and 3rd rows are momentary buttons, the red and switch looking items are toggles, and then the last element is a dial.
If you look at the 2nd picture you can see the equivalent keybindings.

Screenshot 2024-12-26 154954.png
Screenshot 2024-12-26 155632.png


Frankly, I wouldn't expect someone to put in the effort for this for a single stick unless it was EXTREMELY popular, and even then I am not sure it would even be possible. I'd be happy to just have the normal buttons/switches on the controller, and even then it might be complicated because some of the dials and knobs can be toggled between acting as a single analog axis, or a pair of digital buttons - thankfully they are consistent so you either have a Z axis or B24/B25.
 
Brammers :

Still having some issues with device recognition. I'm running the following setup:
Virpil MongoosT-50CM3 throttle (0x33440197)
Virpil Control Panel #2 (0x3344025B)
Virpil Constellation Alpha Prime Right (0x33444390)
Virpil Constellation Alpha Prime Left (0x3344038F)

The throttle and right stick are detected properly by EDRefCard. The control panel and the left stick are not. The code provided by EDRefCard is kdutdc. I went and looked at the code and it seems like the Alpha Prime Left should just work if the ID is added to the bindings data list. Control Panel #2 isn't listed at all, so that would be a new device to support. If I have the time, I'll try adding it myself and throwing out a PR for you, save you some work.

-A'
I can see that the prime left ID has been merged in (by Epahaus). I've updated the image for it this morning - awaiting a code pull onto the server.

If you'd like to create a PR for the control panel please do!

J
 
I can see that the prime left ID has been merged in (by Epahaus). I've updated the image for it this morning - awaiting a code pull onto the server.

If you'd like to create a PR for the control panel please do!

J
Awesome, thanks man! I'll have a look at the code and see what I can do. I think I have some graphics for it around here somewhere as well.

I tried my bindings file again a few minutes ago - the new code must not be live yet, as it has the same results. I'll keep checking.

-A'
 
Reference code: bdpait
Unknown device is VPC Constellation Alpha Left. For some reason, it's not being spotted even though the device should def be supported. PID is 3344812F.

Also should note that I have a vJoy device which is an axis-merge of X and Y axis on the Slaw Pedals (but no big deal if that one doesn't come through).

Thanks!
 
Some limited vJoy support might (might!) be in the next major rewrite - currently no ETA.

The issue with vJoy/target/logic X56 software/VKB etc. is that they make a controller almost impossible to map and often even identify.

J
 
Reference code: sdntis

Unknown Controller Detected.

It got the keyboard, the TCWS Throttle, and the Gladiator NXT R, but it did not map the Gladiator NXT L + SEM (Vendor/Product: 231D/0205) and the Logitech G920 pedals connected via a Leo Bodnar Generic Pedal Adapter (recognized as Logitech G25 Pedal with Vendor/Product: 1DD2/100C).
 
If possible would be great to add this, maybe a niche device, newer model on sale just has different color buttons grey instead of black.

I'm Using "Win Wing" Hotas Orion 2 (F18) came up as "decuxa" in the message for unknown device.

I found These manuals below with graphics and button maps on "https://winwingsim.com/view/regular.html"
Searched
Item--> Throttle
Commodity -->Orion2 NavyAce Throttle Combo

Base PDF - T2-ORION THROTTLE BASE II - User MANUAL EN V1.1

Handle PDF -T2-ORION THROTTLE GRIP

Thank You in advance for checking
o7
Does this look right for the Orion2 throttle?

winwing-orion-throttle2-f18-handle.jpg
 
Hi,
would it be possible to produce bindings for a pair of WInWing devices? I have an Orion 2 combo - Joystick and throttle the user manuals are attached although I had to remove a lot of the contents to get them to upload, sorry.I am not sure what exactly what info you require so please let me know if there is more you need?

Many thanks

Please could you upload your bindings or provide the reference from the unknown controller message on the EDRefcard site?

Thanks
 
Back
Top Bottom