Keyboard and HOTAS Reference Sheet Generator

Status
Thread Closed: Not open for further replies.
I fear I might be going down the rabbit hole of re-implementing the entire in-game interface.
On a serious note: even having the ability to create/change binds on the website and save to the "bind-file format" would be great! It would still be easier than using the in-game interface, (Imho).

Oh you will be going down the rabbit hole for sure. Detecting joysticks, gamepads, wheels, pedals, hotases and whatnot in javascript? FUUUN. Validating user input? Even more FUUUN. Conforming to an XSD sheet (bind file format as you call it?) which we don't have to make sure game understands it and doesn't reject it outright? FUN FUN FUN. Not to mention the simple mundane work of all form UI controls, which even when using a framework can be a PITA. Roooight :D

All that "FUN" may be spent on implementing some useful stuff mentioned earlier ;-) So yes, in theory it sounds like a good idea, but effort to gain ratio is abysmal, considering you already have the in game UI that does the job just fine. If you really despise the interface so much Grendell ;-) you can open the file with a text editor (Notepad++) and try to understand it - you will be able to do adjustments, it's an XML readable in English ;-)
 
@VerticalBlank - thanks for taking over this utility!

I'd asked several times for support for the X45, providing @jgm with, what I thought, were suitable image files, however he never got around to adding it. Are you able to add new controllers? If so, what do you need? Anything I can do to help or make it easier? I'm not a web-developer, but can probably figure it out..

Cheers,
- Micha.
 
@VerticalBlank - thanks for taking over this utility!

I'd asked several times for support for the X45, providing @jgm with, what I thought, were suitable image files, however he never got around to adding it. Are you able to add new controllers? If so, what do you need? Anything I can do to help or make it easier? I'm not a web-developer, but can probably figure it out..

Cheers,
- Micha.

Yes I'm already working on DualShock 3 and 4 and Oculus Touch. Actually DS4 is supposed to be working already but something is off. For the X45 I would need a suitable base image that is free to use and modify plus an enumeration of each input ID on the device. So either an existing bindings file where you tell me which control is which, or you could view the device in the "joy.cpl" control panel, press each control in turn, and note which button lights up on the screen.
 
Wow I did a server audit and I'm a bit surprised to see 151 private uploads versus just a handful of public uploads.

The old site defaulted to public whereas now I default to private and ask for a description string if you want to make it public.

Was asking for a description really that big a barrier?

Genuine question. I'm keen to foster a community of sharing configs, so if I've inadvertently hobbled that, then I need to know.
 
The old site defaulted to public whereas now I default to private and ask for a description string if you want to make it public.
Was asking for a description really that big a barrier?

More likely, you changed the default behaviour and the users clicked through without much reading ;-) [next, next, next, next, next... sounds familiar? ;-)]
 
Wow I did a server audit and I'm a bit surprised to see 151 private uploads versus just a handful of public uploads.

Genuine question. I'm keen to foster a community of sharing configs, so if I've inadvertently hobbled that, then I need to know.

Add a big encouragement on each poge?
 
Have you added support for pedals using this http://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=187 ? I have one so can provide data.

Quite a few pedals are already supported including CH Pro, Slaw, MFG Crosswind, Thrustmaster TFRP, Saitek and Logitech G940. Yours may very well be supported as part of that. Give it a go and let me know how you get on.

https://edrefcard.info/

Hello! Thank you for this tool! Now I can remember and fine tune my settings. Helps a ton! +1

https://www.mcdee.net/elite/binds/mkpjgl?replay=mkpjgl

Ah, I see jgm hasn't put in the redirect on his site yet. The newest version is now hosted at https://edrefcard.info/
 
Thank you for this great tool!

I'm now just trying to prepare my first setup and found out the Gametrix ECS is not recognized.
My config id is "zlbvcd".
Is there any chance to have that added? I've heard a lot of people in Elite using the engine control system.
 
The thing is, now that I have a listings page of all the published configs https://edrefcard.info/list I kind of need them all to have a description. I need to think about this some more.

Simplistic approach:
Code:
UPDATE TABLE Configs set description="None given" where description is NULL;
ALTER TABLE Configs change column description varchar (255) default 'None given';

:p

Eventually you can repeat your mapped device name as description in case none given :)
 
Thank you for this great tool!

I'm now just trying to prepare my first setup and found out the Gametrix ECS is not recognized.
My config id is "zlbvcd".
Is there any chance to have that added? I've heard a lot of people in Elite using the engine control system.

Sure. I would need one or more images of it that show all the controls and are free to use and modify. Also I'd need the input name of each control, either from the control panel (Windows+R "joy.cpl") or you could PM describe to me what each control is bound to in "zlbvcd".
 
Simplistic approach:
Code:
UPDATE TABLE Configs set description="None given" where description is NULL;
ALTER TABLE Configs change column description varchar (255) default 'None given';

:p

Eventually you can repeat your mapped device name as description in case none given :)

Yes, supplying a default name has of course occurred to me. I initially rejected the idea on the grounds that nobody would bother supplying a description and we would just end up with a list of configs all named "untitled" or whatever. But on reflection that I should better than having none at all.

I'm not a fan of forcing people to supply a name without providing a default as that tends to be really annoying UX.

The mapped device name is stored separately and already appears in the listing as of v1.0.5.
 
Last edited:
I'm not a fan of forcing people to supply a name without providing a default as that tends to be really annoying UX.

The mapped device name is stored separately and already appears in the listing as of v1.0.5.

That "annoying UX" part is true. Why not drop the description at all and make the mapped device the most significant? That way someone can look for a config matching their device, which we do anyway. I am surprised you put so much emphasis on the description field anyway, because the main use case of "public config" was sharing configs with people having the same device ;-)

Anyhow, great work, those are small annoyances at best. Let's not blow this out of proportion ;-)
 
jgm gets the lion's share of the credit. I'm just the maintenance programmer!

i think I might revert the default to being public with a default description of "untitled", but with the proviso that untitled entries might get expired after a certain number of days, whereas if you give it a proper description then it's permanent.

Thoughts?
 
entries might get expired after a certain number of days, whereas if you give it a proper description then it's permanent.
Thoughts?

Previous links did expire iirc. Watch out for server space if you want to promise anything "permanent" ;-), after all we have 2.75 million copies sold according to Braben ;-) Other than that, you will get a lot of descriptions like "bindings for hotas x", "jack's bindings" etc... Like I said IMHO the "selling point" is the device (or devices) the controls are for; I myself would treat description as some kind of a guide, like "modifier 1 - weapons related, modifier 2 - navigation related, modifier 3 - miscellaneous" etc. But I highly doubt more than 10% people to fill in something more than "lol".

Seeing the list on the website I am puzzled why didn't you name that field "TITLE" :D There's hardly room for a full fledged description, and it is a link :)
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom