TEST Warthog Bindings Development Group

Ocxyde · Nov 26, 2015

I own only the Stick one, not the Gaz ...
I play my fight with that both KB and the Stick.

Must I buy the Gaz too for my Connie ?

Ocxyde · Nov 26, 2015

That sounds pretty good for me, thank you bro. ;)

Gearen · Nov 26, 2015

I like that hotas, but I'll wait for the SC hot ass.....

Montoya · Nov 26, 2015

I keep changing these every time I play, but here is the current one. I think there are a few things missing here that I did not add yet.

intolerant_jerk · Nov 30, 2015

What I really need is for someone to develop a script for a Warthog thruster and a CH Flightstick. I bought the pair used for a great price, but it seems that people have customised scripts for a complete set of products, not a mix and match setup.

Curse my reckless spending frugalness.

intolerant_jerk · Nov 30, 2015

NKato said:
I plan to make the profiles available for standalone use, meaning there will be versions for the situation you just described.

Ah, brilliant. Cheers NKato.

TexasSkulls · Dec 10, 2015

I just posted this thread elsewhere, but figure it's also pretty relevant to this group:

https://testsquadron.com/threads/sc-alpha-2-0-keybinds.6028/

Also, I mapped out every button/switch/whatever on the Warthog Stick and Throttle, including the use of Solarfly's I/O switch, UMD pinky toggle, and short and long key presses. I also mapped out the final output from the TARGET software for each button press, be it a DX input or a keyboard input. Then I tied that together with his intended function bindings and their respective in-game and xml names.

Code:

https://docs.google.com/spreadsheets/d/1PTFbo2XviBQgdfJVA14DyPlSLZVgT0JCuiJu3rEnNhI/edit?usp=sharing

First thing I noticed was Solarfly's stuff was sometimes assigning a DX value to a controller button, even though there was already an in-game keyboard mapping for whatever function. For example, if launch countermeasures is mapped by default to Z, Solarfly's TARGET scripts would instead assign DX "Button3" to the button he wants to use to launch countermeasures. This means that you then have to also manually (or through his xml) map "Button3" to the launch countermeasures function on the Joystick tab in-game. If instead you assign a key press of 'X' to that same button in the TARGET software, you don't need to map it a 2nd time. In the Google sheet above, I made a lot of these fixes to limit the amount of joystick tab mappings I needed.

Solarfly's TARGET scripts are actually pretty easy to edit. In his solarfly_mappings file, he assigned the end output value to variables named exactly after their SC xml name. Following the above example, solarfly might have:

Code:

define v_weapon_launch_countermeasure DX3

You would then have to go in-game and bind Button3 to launch countermeasures under the joystick mappings tab. Instead, you can change the line to read:

Code:

define v_weapon_launch_countermeasure 'z'

Now, no new bindings are needed, as the key press 'z' is already bound to launch countermeasures. This simple change can be done for any of the other bindings he has in his files.

Long story short, I think Solarfly's base code is great in that it allows for so many more bindings than basic buttons/switches we have as Warthog owners. The pinky U/M/D toggle, I/O switch, and ability to track short and long presses is great, and even if you don't bind them to stuff, his code works as a good baseline. From there, and using the above info, we can customize it to our liking with a huge number of options available to us. Anyways, let me know if this helps any of you guys out, or if you have any questions.

Unshaven · Dec 10, 2015

Absolutely wonderful idea.
I picked up a warthog about a year ago.
I read through the Thrustmaster manual and went to RSI and found little to no official information from RSI on configuration.
By that I mean a defacto, official how to, including full directory paths, critical files and what they do, etc.
Like most companies today, they create a forum and throw you into that in order to figure things out so they don't have to be bothered with actually, you know, supporting the product (Apple comes to mind).

When you start going through and trying out all the online hotas warthog how too's (as I did, including solarflys massive CIG post) it quickly turned into a wad of @#$@, with files over here, files over there. Directory paths and names changed and broken by updates from CIG complicated things even more by making running changes. Instructions from people that mean well, but invariably assume things about the readers knowledge at one point or another which leads to problems and a non-functional hotas.

So I turned to the mouse/keyboard.
I'm an old school, real world aviation guy. You push the stick forward and the houses get bigger. You pull the stick back and the houses get smaller.
For a trackball, that means when you roll the top of the ball away from you, the ship is supposed to dive.
I found that CIG/AC is defaulted for the opposite of that, in order to cater to all the younger players who grew up not actually flying real airplanes I suppose.
I also found that no matter which pitch/y-axis setting I tried to invert, nothing would correct the pitch movement to be correct. It remained inverted from the way it was supposed to be.

Sigh.

So anyway, if I had a whole day or two to roll up my sleeves, read through all the stuff again I suppose I could probably sort it out, just too busy (for the hotas).

I think it would be a great idea to develop a simplified, no @#$@ how to that explains the directory paths, files required, etc. for configuring the TM hotas warthog. If anyone knows how to invert that mouse, I'm REALLY listening!

Oh and Merry Christmas!
:)

Vimes · Dec 10, 2015

I have the Warthog Hotas and Saitek Combat Pedals.

Currently i just use a custom keybinding.XML file provided by skupples in this thread

It works decent enough for my mapping needs, i used it as an base layout and then went on from there.

I support your project tough! and perhaps ill use your setup as a starter point in the future.

maynard · Dec 10, 2015

tl:dr binding warthogs sounds kinda kinky to me

solarfly · Dec 17, 2015

I saw this post a week ago as I was beginning the Solarfly StarCitizen Warthog Profile Update for 2.0, now available and released at http://3dpipeline.net. And your comment that it seemed too complicated is correct. As my own worst critic, there are things I hated, especially the extra shift state on EAC and how views and landing modes were handled. I took it to heart. At the same time, I'm sure by now you've realized that with the abundance of controls CIG keeps adding, it's no easy task.

I am proud to present the 2.1-PTU profile, which streamlines many of the operations and groups things nicely. Landing operations, IFCS toggles, Quantum drive, a really awesome Afterburner/Boost interaction and View Modes brought to the front of Hat1 are just some of the changes. Weapon controls, shields, power and HUD control all remain in-tact.

I added links and diagrams for the 2.1 version down in the thread below, and deleted the images here so as to keep it less spammy!

Please let me know what you think (make sure to pp_rebindkeys <enter> once to load defaults, then go ahead and load the profile).

Cheers,
Solarfly

lex · Dec 17, 2015

damn, that's complex and awesome profile. Gonna give it a spin now.

gladestone · Dec 18, 2015

Going to need some ones help with mind in 2,0 ill see if i can get supertokyo again its borked lol. Wish i was more techish like yall

TEST Warthog Bindings Development Group

Grand Admiral

Lieutenant

Grand Admiral

Lieutenant

Grand Admiral

Space Marshal

Administrator

Grand Admiral

Grand Admiral

Rear Admiral

Grand Admiral

Rear Admiral

Identifies as an Aurora Missile

Commander

Captain

Space Marshal

Lieutenant

Space Marshal

Vice Admiral

Grand Admiral