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

Maur

Maur
Reference ppgvur... none of my devices are recognised.

I have a Virpil MT-50CM3 base with a FLNKR grip (33444393), a Virpil VMAX Prime throttle (33448196), a Virpil Panel #2 (3344825A), a Thrustmaster T-Pendular Rudder (044FB68F), and I'm using Tetherscript Virtual Joystick (F00F0001) to translate a 3DConnexion Spacemouse Enterprise's 6DOF output into a joystick output, since ED bugs out if you try to use spacemice directly.

I'm not sure that it is possible to tell the difference between all the different grips that can be attached to a Virpil MT-50CM3, unless you query the USB device name after having the user modify the USB name from the default "VPC Stick MT-50CM3" to, say, "VPC MT-50CM3 FLNKR Ext"... the USB Product ID is the same for all grips attached to the base, and I hear that it depends upon the firmware. The number of buttons depends on whether the user is using default (22 buttons) or extended (30 buttons) hats, and if the user has enabled ALPS hats (26 or 38 buttons, depending on default or extended hats respectively)... or has modified the physical to logical button mapping...

There would also be a similar problem with the VMAX throttle, since the mode dial can be assigned by a profile to set shift mode, and there is an option to turn on ALPS diagonals as extra buttons...

The Panel #2 is the simplest of the devices, since it has no alternate configurations, no hats and no axes, just 42 buttons.
 

Brammmers

Brammmers
Maur said:
Reference ppgvur... none of my devices are recognised.

I have a Virpil MT-50CM3 base with a FLNKR grip (33444393), a Virpil VMAX Prime throttle (33448196), a Virpil Panel #2 (3344825A), a Thrustmaster T-Pendular Rudder (044FB68F), and I'm using Tetherscript Virtual Joystick (F00F0001) to translate a 3DConnexion Spacemouse Enterprise's 6DOF output into a joystick output, since ED bugs out if you try to use spacemice directly.

I'm not sure that it is possible to tell the difference between all the different grips that can be attached to a Virpil MT-50CM3, unless you query the USB device name after having the user modify the USB name from the default "VPC Stick MT-50CM3" to, say, "VPC MT-50CM3 FLNKR Ext"... the USB Product ID is the same for all grips attached to the base, and I hear that it depends upon the firmware. The number of buttons depends on whether the user is using default (22 buttons) or extended (30 buttons) hats, and if the user has enabled ALPS hats (26 or 38 buttons, depending on default or extended hats respectively)... or has modified the physical to logical button mapping...

There would also be a similar problem with the VMAX throttle, since the mode dial can be assigned by a profile to set shift mode, and there is an option to turn on ALPS diagonals as extra buttons...

The Panel #2 is the simplest of the devices, since it has no alternate configurations, no hats and no axes, just 42 buttons.
Click to expand...
Adding base support for those devices, mapping to the USB ID is possible. If the Virpil software can alter the device behind an ID, then we can't support that at present - in the same way that we can't support other virtual device software such as vJoy or TM TARGET based either. I'll add it to my notes for consideration in the rewrite.

Meanwhile I've created multiple issues on github for adding these devices Virpil MT-50CM3 base with a FLNKR grip (33444393), a Virpil VMAX Prime throttle (33448196), a Virpil Panel #2 (3344825A), a Thrustmaster T-Pendular Rudder (044FB68F) - at least in their base configurations as a starting point.
 
Last edited:

Brammmers

Brammmers
For all those who have recently requested device support ... I have logged them all as issues on the GitHub report.

Open requests/issues list can be found here:
github.com

Issues · brammmers/edrefcard2

EDRefCard2. Contribute to brammmers/edrefcard2 development by creating an account on GitHub.
github.com github.com

I've also merged two contributions from other people:
  • Label typo on keyboard controls regarding walking/sprinting (thanks clockbrain)
  • Better support for Ursa Minor Fighter Left/Right (thanks enyachoke)

@Epaphus would you be kind enough to pull the latest main branch please?
 

Brammmers

Brammmers
@AnarchoTheytriarch, @Kernic and @Zubastian - the latest upload supports the left and right stick of the hosas. Unfortunately it doesn't look like the angled throttle is represented in software of the "Space L" stick, so I can detect that automatically and adjust the image. Please let me know if any of your bindings are showing up in the wrong place. (or raise an issue on github).

J
 

CMDR Darth Vater

CMDR Darth Vater
Hi, I use a HOSAS Bundle with Virpil Alpha Prime Left plus Virpil Alpha Prime Right and the Virpil Control Panel #2.

@Brammmers was so fine to create issues already for my case. Today I started Elite after playing with the LEDs in Virpil Configuration Tool and ... I've got new "names" for the devices. 33443F5 became 334483F5. My Virpil Keybinds can't be loaded as I see in the error log: unknown devices ... what the heck? Any idea how to avoid that or to "mask" that naming for Elite and the edrefcard? How other Virpil-users handle that?
 

DawnTreader777

DawnTreader777
CMDR Darth Vater said:
Hi, I use a HOSAS Bundle with Virpil Alpha Prime Left plus Virpil Alpha Prime Right and the Virpil Control Panel #2.

@Brammmers was so fine to create issues already for my case. Today I started Elite after playing with the LEDs in Virpil Configuration Tool and ... I've got new "names" for the devices. 33443F5 became 334483F5. My Virpil Keybinds can't be loaded as I see in the error log: unknown devices ... what the heck? Any idea how to avoid that or to "mask" that naming for Elite and the edrefcard? How other Virpil-users handle that?
Click to expand...
Go into the profile part of the Virpil configuration and set the USB product ID back to what it was. OR use sublime text to find and replace the binding references to the previous ID and put in the new ID. I find it easier to force the sticks to keep the ID than to edit my bind file.

1745698288344.png
 

CMDR Darth Vater

CMDR Darth Vater
DawnTreader777 said:
Go into the profile part of the Virpil configuration and set the USB product ID back to what it was. OR use sublime text to find and replace the binding references to the previous ID and put in the new ID. I find it easier to force the sticks to keep the ID than to edit my bind file.

View attachment 427580
Click to expand...
then it would really make sense for using edrefcard that the users set the Product ID to a specific ID and it stays as such?
 

DawnTreader777

DawnTreader777
CMDR Darth Vater said:
then it would really make sense for using edrefcard that the users set the Product ID to a specific ID and it stays as such?
Click to expand...
I thought the problem was that your game wasn't loading the sticks? This fixes the problem with the game loading the binds file, not anything to do with ED Ref. ED Ref just loads your binds XML and presents it against detected controllers. ED Ref doesn't care in the same way that Elite does. If Elite doesn't see the devices, it won't load the binds, and your controllers won't work in game.
 

CMDR Darth Vater

CMDR Darth Vater
DawnTreader777 said:
I thought the problem was that your game wasn't loading the sticks? This fixes the problem with the game loading the binds file, not anything to do with ED Ref. ED Ref just loads your binds XML and presents it against detected controllers. ED Ref doesn't care in the same way that Elite does. If Elite doesn't see the devices, it won't load the binds, and your controllers won't work in game.
Click to expand...
yes, but if I set e.g. my Product ID to yours, then I assume I can even load and use your keybinds from edrefcard.

Does anyone know why the old x56 Saitek or Thrustmaster are named as such in the keybinds and Virpil not?
1745699673078.png
1745699689140.png


ED Tracker is named after it's processor:
1745699959496.png
 

DawnTreader777

DawnTreader777
CMDR Darth Vater said:
yes, but if I set e.g. my Product ID to yours, then I assume I can even load and use your keybinds from edrefcard.
Click to expand...
Don't set it to mine. Set it to what it was looking for in the bind error log. Use what yours was originally. This is mine.
1745704703132.png

The bind error log is in the same folder as the binds. Open it and determine what it was looking for. If it is virpil it should show something similar to mine. Take the last 4 characters and put them in the virpil configuration software where I showed before, hit the save button. Your stick should now show that PID in these 2 places.
1745704537395.png


If you need to do that for both sticks, repeat for the other stick and then try loading the game. Your binds and controls should work.

Does it really matter if the thrustmaster and saitek are "named" and the virpil is not? In the end it doesn't really matter to your game play. I suspect that the thrustmaster and saitek report the devices differently that the virpil does. It would be nice if the virpil's did the same, but think about this, the base and the stick are 2 separate entities. How would you report that to the game?
 

CMDR Darth Vater

CMDR Darth Vater
What my recommendation is: write on edrefcard.info a short info where, why and what numbers for PID:
Control Panel #1: 44F1
Control Panel #2: 44F2
Control Panel #3: 44F3
Left Stick Alpha Prime: 44F4
Right Stick Alpha Prime: 44F5
...
Like that edrefcard.info will always recognise the products. The bindings uploaded are usable for anyone. I set mine for testing to @DawnTreader777, just needed to throw out t-rudder, vjoy and an unknown device used under humanoid.

I am unsure if any of the digits has a meaning or the letter F? It just seems to me that the numbers are random and go up once updating LEDs, calibration, firmware. And the F seems reoccuring for the sticks, but my panel has got an A:
1745740469754.png
 
Last edited:

Brammmers

Brammmers
CMDR Darth Vater said:
I asked Virpil Support if there is deeper meaning behind their PID or if it's just random hexadecimal.
Click to expand...
Typically the VID (first 4 digits) is a Vendor ID ... so all Virpil devices should have a common value here (3344). This is usually assigned by the USB forum people. (Intel's for example is 8088).

The last 4 digits are a PID - product ID and can be whatever the vendor wants it to be - feel free to change this, so long as it's unique on your system for that Vendor ID.

J
 
You must log in or register to reply here.
Back
Top Bottom