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

Hello there !
I just received my VKB Gunfighter MK.II with Kosmosima Space Combat Grip Premium-R in replacement of my old T.16000 and this is a really nice joystick.
I really would like to have an edrefcard map for this one, so here are the specifications that can be useful.

Four versions of the grip
  • Kosmosima SCG-L
  • Kosmosima SCG-R
  • Kosmosima SCG Premium-L
  • Kosmosima SCG Premium-R
Premium versions
This version is bundled with extra switches and can be customised like a standard version (see below).
  • A1 switch : Pushing on the #20 button switch the behavior from POV-switch to analog ministick.
  • B2 : The trigger can be pushed or pulled (27 or 26)
  • Fire : The trigger can be softly pushed or hardly pushed (1 or 1+2)

Standard versions
I didn’t find any map of this device but here are the differences from the premium version :
  • No B2 trigger
  • A1 is a Hat switch with center push
  • C1 is a push button
These joysticks are highly customizable with a software that push the setup into the device.
I can submit other informations (like my .bind file) and try to make some good photos if needed.
 
Last edited:
I'm having the same issue, with the same setup: CH Fighterstick, Pro Throttle, Pro Pedals. Also running on Oculus Rift and purchased through their store if that makes a difference. Ref code: jgdldp

Looks like the code has missed the USB identifier for the stick and assigned it to the Throttle.

If you look in your binds file 068EC010 that’s the stick, 068EC011 is the throttle. The ID for Pedals is 068E0501 and doesn’t appear in my Binds file as I’ve consolidated the controls using Control Manager, think in this case it gets picked up as a Stick R axis.

In any event, it’s a misread in the Page Code as mine looks the same as yours when printed despite it having worked OK previously.
 
Quick hint for Virpil/VPC owners: While EDRefCard does support the combination of the WarBRD base and the Constellation Delta grip, it will only detect them from your bindings file if they show up as device 03EB2044 (for right hand) or device 03EB2042 (for left hand). Unfortunately, these device IDs are simply the USB VID and PID values concatenated together. The problem is that these values are not only configurable in the VPC software, but also seem to change each time you use the VPC profile wizard. My (used) WarBRD+Constellation Delta showed up as device 03EB2049, and I always received an "you have an unknown device" error message from ED Ref Card.

It is possible but somewhat complicated to fix things without having to rebind everything:
  1. If Elite is running, quit to desktop.
  2. Launch the VPC configuration software, select your stick, use "load VPC device"
  3. go to the profile page, write down your old VID and PID values in the USB text area
  4. change the VID and PID values to 03EB and 2044 for a right hand stick, and 03EB and 2044 for a left hand stick
  5. use "save VPC device" and close the VPC software
  6. open your Custom.3.0.binds file in a regular text edit (Windows Notepad works just fine)
  7. Search for your old VID value. This will part of a Binding/Primary/Secondary Device="VVVVPPP" statement
  8. Now do a global search and replace of the VVVVPPPP value in your file by 03EB2044 (for right hand) or 03EB2042 (for left hand).
  9. Save and exit. Create a backup copy of your Custom.3.0.binds file that is NOT named <something>.binds.
  10. Launch the game and test. The bindings are read before the main menu appears. If you made a mistake, an error log file will show up in the bindings directory detailing which device was not found. In that case, exit to dekstop again, restore your bindings from the backup, and fix the device entries mentioned in the logfile.
  11. You can now create a reference card
 
Quick hint for Virpil/VPC owners: While EDRefCard does support the combination of the WarBRD base and the Constellation Delta grip, it will only detect them from your bindings file if they show up as device 03EB2044 (for right hand) or device 03EB2042 (for left hand). Unfortunately, these device IDs are simply the USB VID and PID values concatenated together. The problem is that these values are not only configurable in the VPC software, but also seem to change each time you use the VPC profile wizard.
...
Thanks for that, Cometborne. I'm not sure how much I can do to mitigate this in the source code if the device IDs are entirely user-configurable. To be honest, that sounds like a protocol violation on VPC's part. Device IDs are supposed to be stable and reliable.
 
Top Bottom