Keyboard and HOTAS Reference Sheet Generator

Status
Thread Closed: Not open for further replies.
The tool didn't work. Almost every button was blank. Without support to represent the VoiceAttack assignments to buttons from the VoiceAttack bindings, the reference sheet is mostly blank.
 
The tool didn't work. Almost every button was blank. Without support to represent the VoiceAttack assignments to buttons from the VoiceAttack bindings, the reference sheet is mostly blank.

I'm afraid I don't understand your specific setup. Could you explain it in a bit more detail, preferably providing a specific command and how you activate it as an example, and also let me know the ID returned when you upload your binds file so that I can take a look at it for reference?
 
So glad I came across this thread. It's been a bout 8 months since I've played and I could not remember what I had set up. Here is my set up that I'm running at the moment.
rsjtwx-x55.jpg

Now with landings, maybe it's time to add more.
 
So glad I came across this thread. It's been a bout 8 months since I've played and I could not remember what I had set up. Here is my set up that I'm running at the moment.
View attachment 90685

Now with landings, maybe it's time to add more.

Couple of tips:
1. Don't map anything on the throttle to Boost. When the X55 gets phantom presses, the button you have mapped to Boost is one of the ones that tends to get pressed, and that's how I pancaked my first clipper into the back of the station (I later found out about deploying the cargo scoop as emergency brakes). I use the button you have as Target Highest Threat to Boost, and the one you have for Boost as Flight Assist
2. The silver wheel on the throttle you have mapped as increase/decrease sensor range works much better as target prev/next subsystem. With a bit of practice, you can give it a quick flick to select the power plant.
 
Couple of tips:
1. Don't map anything on the throttle to Boost. When the X55 gets phantom presses, the button you have mapped to Boost is one of the ones that tends to get pressed, and that's how I pancaked my first clipper into the back of the station (I later found out about deploying the cargo scoop as emergency brakes). I use the button you have as Target Highest Threat to Boost, and the one you have for Boost as Flight Assist
2. The silver wheel on the throttle you have mapped as increase/decrease sensor range works much better as target prev/next subsystem. With a bit of practice, you can give it a quick flick to select the power plant.

Great tips, Thank you. I will have to try those. I've read about the phantom switches, does it just happen to the throttle? I'll move the boost over to the stick.
 
Great tips, Thank you. I will have to try those. I've read about the phantom switches, does it just happen to the throttle? I'll move the boost over to the stick.

It's only on the throttle, yes. As far as I know there's been no official word from Saitek, but it's been pretty much established that the phantom presses happen because the USB port doesn't supply enough current to the throttle (it uses a lot more juice than other USB devices), and that causes the circuitry inside the throttle to glitch; hence the advice to either use a powered hub or try a different USB port (some ports provide more power than others, depending on the motherboard. The USB spec states the minimum power the port must supply, not the maximum, and providing more power than baseline is both safe and useful). I personally think it's the dozen or so LEDs inside the throttle, because the stick must have similar circuitry and doesn't have those problems.
 
Last edited:
I'm afraid I don't understand your specific setup. Could you explain it in a bit more detail, preferably providing a specific command and how you activate it as an example, and also let me know the ID returned when you upload your binds file so that I can take a look at it for reference?

Many of my buttons are assigned using the VoiceAttack macros instead of the ED bindings. The macros issue one or more ED actions. For example, I have a button assigned to a VoiceAttack macro called "Landing Gear" which issues the Deploy/Retract Landing Gear toggle, tracks the position of the landing gear and provides verbal feedback about it's deployment. The landing gear position is used by other macros (e.g. "Deploy Weapons", "Jump"). Ideally, the reference sheet would indicate the ED and VA assignments.
 
Last edited:
Many of my buttons are assigned using the VoiceAttack macros instead of the ED bindings. The macros issue one or more ED actions. For example, I have a button assigned to a VoiceAttack macro called "Landing Gear" which issues the Deploy/Retract Landing Gear toggle, tracks the position of the landing gear and provides verbal feedback about it's deployment. The landing gear position is used by other macros (e.g. "Deploy Weapons", "Jump"). Ideally, the reference sheet would indicate the ED and VA assignments.

Honestly I don't know how I would tackle that. VA commands are macros so could do pretty much anything, and there is no metadata that gives me suitable information to build a useful reference sheet. The best I can think of doing would be to parse out the trigger phrases but I don't see that having a lot of utility. What would you expect to see in the reference sheet?
 
I've added initial support for some pedals. If you have pedals please could you try out the reference generator and let me know how things show up? I've had to guess the initial mappings so there is a fair chance that there are some problems; if you see anything that looks incorrect please let me know.
 
This is awesome, thanks!

Just for fun, here is my current Hotas Warthog bindings. WIP, but works pretty well for me atm, but I guess I'll change it somewhat later. I also have a G27 wheel that's handy with the SRV's (then I still can use the joystick for pitch and roll), and which I've mapped a couple of other functions to also (handbrake is H-shifter 4th gear, for example, and booster jump is 3rd). Unfortunately my G27 wheel buttons or paddle shifters don't work any longer, but luckily the rest of it does.

I'm also using the pedals for yaw in ships (and accelerator pedal for thrust / speed in SRV), though the yaw function is of course almost useless. Still, to use clutch and accelerator pedals for that, I use an Autohotkey script called UJR - Universal Joystick Remapper (remapped to virtual joystick - vJoy). Works great!

So I guess your awesome Reference Sheet Generator lacks the G27, but it's no biggie at all. Just saying.

iomsjb-warthog.jpg
 
I've added initial support for some pedals. If you have pedals please could you try out the reference generator and let me know how things show up? I've had to guess the initial mappings so there is a fair chance that there are some problems; if you see anything that looks incorrect please let me know.

Working great here. Thanks for including the pedals.
 
This is awesome, thanks!

Just for fun, here is my current Hotas Warthog bindings. WIP, but works pretty well for me atm, but I guess I'll change it somewhat later. I also have a G27 wheel that's handy with the SRV's (then I still can use the joystick for pitch and roll), and which I've mapped a couple of other functions to also (handbrake is H-shifter 4th gear, for example, and booster jump is 3rd). Unfortunately my G27 wheel buttons or paddle shifters don't work any longer, but luckily the rest of it does.

I'm also using the pedals for yaw in ships (and accelerator pedal for thrust / speed in SRV), though the yaw function is of course almost useless. Still, to use clutch and accelerator pedals for that, I use an Autohotkey script called UJR - Universal Joystick Remapper (remapped to virtual joystick - vJoy). Works great!

So I guess your awesome Reference Sheet Generator lacks the G27, but it's no biggie at all. Just saying.

Glad to hear that it's useful for you. It might be possible to support the G27, but I'd need a few more people with existing configurations so that I can map all of the various functions. Anyone else out there using a G27 for Elite?
 
Just thought I'd pop back in and mention, when you run the configuration software for the Warthog, it actually creates a NEW device instead of using the throttle and stick profile. I don't know if it's even reasonable to try to add this, a good number of the buttons aren't recognized by the game once you turn on the profile, so you have to set them to key board bindings.
 
Just thought I'd pop back in and mention, when you run the configuration software for the Warthog, it actually creates a NEW device instead of using the throttle and stick profile. I don't know if it's even reasonable to try to add this, a good number of the buttons aren't recognized by the game once you turn on the profile, so you have to set them to key board bindings.

Yes unfortunately when the mapping software gets in the way it becomes much harder to track which buttons do what. The mapping software grabs the HOTAS inputs and translates them to whatever it feels like, which makes things a lot more complex for me to map as there are conditionals, macros and all sorts of stuff.

What in particular are you using the mapping software for? Is it something that you can't manage to do without the mapper?
 
Yes unfortunately when the mapping software gets in the way it becomes much harder to track which buttons do what. The mapping software grabs the HOTAS inputs and translates them to whatever it feels like, which makes things a lot more complex for me to map as there are conditionals, macros and all sorts of stuff.

What in particular are you using the mapping software for? Is it something that you can't manage to do without the mapper?

I'm using it so that the stick doesn't "hold" buttons down when I use some switches. If the game expects a momentary switch, I have to flip it twice to shut it off, unless I program a key press on off, and the same one on the "on". Plus my docking macro.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom