Community Event / Creation Thrustmaster Warthog Configuration & Sheets

[Devil]

HI, ok, im getting fed up of the joystick setup. and need advice.

when I use target software, ED does not find my joystick. When I do it the old way, most things just don't work.

So, can someone please give me tips here. between this and constantly getting killed by pvp while trying to learn how to get to other systems and stations.

Don't laugh I still have not managed to find a different station or system. dark fakk keeps killing me.

 

[cmdr awesome]

HI, ok, im getting fed up of the joystick setup. and need advice.

when I use target software, ED does not find my joystick. When I do it the old way, most things just don't work.

So, can someone please give me tips here. between this and constantly getting killed by pvp while trying to learn how to get to other systems and stations.

Don't laugh I still have not managed to find a different station or system. dark fakk keeps killing me.

Practice on the single player missions.
I don't use target, and ED recognised the Warthog with no problems. Everything works pretty well. The only slight niggle I have is that I use the speedbrake switch on the throttle for landing gear and cargo scoop, and they pulse rather than hold so I can push the switch forward to deploy the landing gear but need to return to centre and push forward+back again for it to retract.

Summary of my controls:

Joystick
CMS - cycle targeting (L/R for all, U/D for enemies), press for nearest enemy
Pinkie - Toggle FA
Trimswitch - headlook, menu navigation, thrust
TMS - power management, UI tabs
DMS - up for boost, down for toggle headlook, left/right for subsystems targeting
Trigger - primary fire
Weapons release - secondary fire
Nosewheel - target under reticule
Master mode - next firegroup

Throttle
China hat - hardpoints/frameshift
boat switch - silent running
speedbrake - cargo scoop/landing gear
mic - push for heatsink deploy
coolie - UI screen select
slew - yaw (I don't have pedals)
left throttle button - reverse

That covers most stuff. I think I mapped the lights to one of the control panel switches but couldn't say which!
I find I can do most combinations of things I need to. Headlooking is clunky but then if you have a tracker that's not a problem.

 

[MikeyTT]

Sorry, I've been away for a few days and haven't had chance to respond to any posts so far.

I should get time tonight to finally fire up the SB and have a look at how the new changes impact the target profile. I'll also see if I can record what I do and post up a quick guide on what I do.

 

[anongw65]

Hello All,

First and foremost, many thanks to MikeyTT and Yaffle for all the work and assistance to those of us trying to get this combination of hardware/software working.

Secondly, I despise the TARGET software! Love the hardware, though!

Ok, so I'll give you my experience. I downloaded MikeyTT's TARGET profile. Getting that into TARGET was an experience by itself. That's not actually the software's fault, just my inexperience. That being said, instead of "adding" the configuration file (which didn't bring in the bindings), I had to "Edit Configuration," which loaded it up. I assume that "Run Configuration" will do the same thing. At that point, I could see, after several screens, the "events." All well and good, and running the configuration worked.

A couple of points to be made. If you get into ED without running the configuration, you'll see the Thrustmaster listed. If you run the configuration, it will no longer be there, just a generic joystick. It also needs to be said, and this point was already mentioned in this thread, that once you start making any changes in ED, the listing automatically goes to "custom."

To this point, I'm ok. After trial and error, I loaded up MikeyTT's config file and made all the changes in ED as well.

Now, the frustration. Some of the switches worked as advertised, such as the Cargo Scoop. Most of the others from the TARGET config file, did not. I don't know what I'm doing wrong, but I'll attempt to reprogram all the bindings from within ED again. Many, when you try to program them in ED, such as "Jettison Cargo," don't have any effect. In other words, in ED, when I hit the action, and then try to associate a switch, nothing appears, as if the toggling of the switch wasn't recognized.

If I had to guess, I'd say I'm the one who's doing something wrong in the translation.

Let me get one thing out of the way. My setup consists of the TM Warthog HOTAS, the TrackIR5, and Saitek pedals.

If anyone has any idea of what I'm doing wrong, or has any suggestions, please feel free to criticize/educate me. If I may politely ask MikeyTT or Yaffle, maybe posting the "Custom.binds" file would help some of us out. Of course, that means the proper loading of the Thrustmaster config file which MikeyTT was kind enough to post. Please don't take this as a "I don't wanna do the work myself" query, because I'd love to know what I'm doing wrong so that I may actually be useful to someone else at some point.

In case anyone is wondering where that bind file is, it's in Users/<name>/AppData/Local/Frontier Developments/Elite Dangerous/Options/Bindings.

If nothing else, I hope that my experience/rant can help others on this thread.

 

[Yaffle]

I am unsure why certain binds don't work for you.

It may be worthwhile running the TARGET config, and from the resultant window use the Event Tester functions (buttons down the bottom). These allow you to press the buttons and will display what you have pressed. At least by doing that you can see if the joystick is sending anything to the OS.

 

[anongw65]

Thank you Yaffle,

I will try again. I just wish TARGET was a bit more user friendly, or at least more noob friendly (for noobs like me).

 

[anongw65]

I am unsure why certain binds don't work for you.

It may be worthwhile running the TARGET config, and from the resultant window use the Event Tester functions (buttons down the bottom). These allow you to press the buttons and will display what you have pressed. At least by doing that you can see if the joystick is sending anything to the OS.

Hi Yaffle,

I tried the Event Tester. Very interesting. I'm under the assumption that only certain "actions" were programmed into the script which MikeyTT provided. I say that because most of the actions that I take with the HOTAS have no "events," only certain switches on the throttle. As such, the remaining functions on the HOTAS are programmed via ED. If that is, indeed, the case, I just learned something new. That being said, all of the switch functions on the throttle work except for "jettison cargo" and "deploy heatsink."

I'll get back into ED and reset the configuration. I'll let you know how it goes.

See, even old dogs can learn new tricks.

 

[anongw65]

Hello everyone,

With the help of Yaffle, and MikeyTT's script, I think I've got everything working! I'd like to attach my "Custom.binds" file, but I'm unsure of how to do that. If anybody wants it, it's yours, as long as you can tell me how to attach it.

As I've said, I've got the TM Warthog HOTAS, TrackIR5, and Saitek pedals, so if your setup is different, you'd have to make the minor modifications in ED.

Many thanks to Yaffle and MikeyTT!

 

[cmdr awesome]

I've just noticed there is a 'hold' mode for cargo scoop in the controls menu, and so by selecting that and using speedbrake forward for the scoop and backwards for landing gear, it's sorted my last niggle.

Having struggled with Target, I think I'm going to just ignore it as these standard mappings work just fine for me - until we get more gameplay features at least. If anyone wants a copy of my control.binds, let me know.

I'm not using pedals or a headtracker, so my setup should work for anyone.

 

[MikeyTT]

Ok, I've updated the control sheets and created a video which shows how to map the control bindings into Elite.

It's not the worlds most exciting video, but hopefully it'll help those out who are struggling. I've just checked @ 14:14 and it's still in SD. Hopefully the HD vesion will be rendered soon.

The pictures have been updated and the custom.binds and video are now added in the first post of this thread...

Edit: When I get chance (hopefully Friday, or over the weekend) to spend a bit more time in ED, I'll update the diagrams and bindings with anything new I find useful. I know I was going to bind the throttle friction control, and I need to figure out the new comms options.

 

[Buurman]

Thanks MikeyTT!

I used your config for my setup, like it a lot.

I will change some small things, like the Frame shift switch to the pinky trigger on the joystick, because I dont like it that you need to take of your hand of the throttle. I can switch it with Flight assist on/off that is now on it, because I dont use it a lot.

I am also thinking about switching the UI select button (push on thumb joystick) with the UI focus Mode button, because pushing the joystick sometimes causes a wrong selection.

If I will find more things, I will post it!

Again... thanks!

 

[anongw65]

Hey MikeyTT,

I'd like your opinion.

Recently, as the ED update came along, my ED binding profile was wiped. It wasn't a big deal, as it takes only a few minutes to go in and re-bind the keys, but that got me wondering. Your TM profile binds some of the functions, but leaves the rest to ED. Would it behoove us TM users, since many are already using the TARGET software, to program most, if not all, of the bindings using TARGET?

I understand that some things will probably still be required to be done from within ED, especially if there are additional peripherals (Saitek pedals), but having a "complete" TARGET profile would minimize the effect that the wipes have on existing binding profiles.

Also, I downloaded the TARGET manual. Depending on your opinion, as well as the opinion of anyone else who would care to comment, I may undertake the task. After all, although there are numerous individuals who selflessly help out others, I'd rather try to give back to the community as well.

 

[MikeyTT]

Would it behoove us TM users, since many are already using the TARGET software, to program most, if not all, of the bindings using TARGET?

I believe as soon as you put the Target software into the mix you lose the option of seeing the Thrustmaster as a controller. So you would have to create a custom command binding. Obviously without the Target you lose some of the, albeit limited currently, functionality that it brings.

It may be possible to use say a keyboard binding as a start point, but you still have to map the axis of the stick and throttle.

I guess it's only an issue when FD update the available command options, which screws with the existing bindings.

I've included my custom.binds file in the first post, so it saves you having to do this, which may help. When I get into ED I'll keep it updated, but as I work away a lot I really don't get on as often as I would like to. Happy for others to send me theirs (based on my default profile) as I can update the binds file remotely.

As for digging into the Target software yourself then I would say "go for it". If you manage to find some useful nuggets of info then it's all better for those in the community that use the Thrustmaster set-up. If you don't want to fracture into another thread then I'm more than happy to include any profile & diagrams, etc. you create here. I can host the files on my web host too. But your call.

 

[anongw65]

Hi MikeyTT,

You're correct in that, as soon as you introduce the TARGET software, the TM option vanishes from within the ED menu, but that's true whether you use the smaller TARGET profile which you have posted, or a profile that would encompass markedly more features, so I would consider this "the cost of doing business" when using the TARGET software.

You're also correct in another aspect. Being in Beta, bindings may change depending on new features being implemented, or old features being phased out. As such, whereas I'm still going to do some TARGET programming for my own gratification, I think the creation of a complete TARGET profile for ED should be delayed until it goes gold.

 

[MikeyTT]

Hi MikeyTT,

You're correct in that, as soon as you introduce the TARGET software, the TM option vanishes from within the ED menu, but that's true whether you use the smaller TARGET profile which you have posted, or a profile that would encompass markedly more features, so I would consider this "the cost of doing business" when using the TARGET software.

You're also correct in another aspect. Being in Beta, bindings may change depending on new features being implemented, or old features being phased out. As such, whereas I'm still going to do some TARGET programming for my own gratification, I think the creation of a complete TARGET profile for ED should be delayed until it goes gold.

Originally when I started I did have the stick mapped in Target too, but as there wasn't anything fancy going on I didn't see the point. It was just more to manage in the profile. I guess if you take advantage of the macros then it would be worth it.

I'd be interested to see what results you get when you've had a play in Target yourself...

 

[ceno]

Thanks for your really helpful work Mikey!
Got a Warthog yesterday and taking first steps with it (and this Target Software)
With all the Info you provided in the first post it was really easy to set all up.

However, i have a problem...everytime i flip a switch, like cargo scoop, landing gear or Ship Lights for instance, for about 5 seconds no other control input is possible, it seems the command blocks anything else.

Any idea what could cause this behavior?

 

[MikeyTT]

Thanks for your really helpful work Mikey!
Got a Warthog yesterday and taking first steps with it (and this Target Software)
With all the Info you provided in the first post it was really easy to set all up.

However, i have a problem...everytime i flip a switch, like cargo scoop, landing gear or Ship Lights for instance, for about 5 seconds no other control input is possible, it seems the command blocks anything else.

Any idea what could cause this behavior?

Ooooh, that's not good and unfortunately not something I've experienced myself.

What I would do to try and diagnose it is to start with the event tester once the profile is running in the Target software.

If that behaves ok, and you don't get the blocking then I would then move into the game. Try detaching both the stick and the throttle and see if you get the same blocking just with standard keyboard commands. Then move to adding just the stick without the throttle and test that. Then finally with the throttle.

Restarting ED in between the adding of the controllers should identify where the issue is. If the stick is where you get the blocking then try with just the throttle and no stick.

It may be that it's USB port related, so probably worth switching around where you plug true devices in too.

It really comes down to a bit of trial and error to understand exactly which component is creating the blocking. Also worth trying without the profile and Target being launched too.

Hope that helps...

 

[ceno]

Alright!
It was totally USB Port Related, it seems that the front Ports dont work well together with the Warthog.
Now it is very responsive and there is no blocking.
Thanks again for your work!

 

[Commanderhumpster]

Hi i seem to be ejecting heatsinks automatically. Any ideas i am running the script and the launch heatsink button is mapped to joy32 any ideas whats causing this?

Thanks

J

 

[anongw65]

Hi i seem to be ejecting heatsinks automatically. Any ideas i am running the script and the launch heatsink button is mapped to joy32 any ideas whats causing this?

Thanks

J

Hey CH,

First and foremost, when running the script, open up the Event Viewer to make sure nothing strange is going on. Having a second monitor helps a lot because you can have the EV on the second monitor while playing ED on the primary, therefore seeing, in game, if any commands are being input.

Secondly, what are the details? Does the problem happen all the time, or does it "all of a sudden" become a problem. I've had issues where I couldn't, "all of a sudden," get into the station's menus; the screen would come up for a split second and then disappear, as if I were constantly hitting the Exit key. I didn't have my event window open at the time, so couldn't see if anything weird was going. The only way I fixed it was by quitting ED, closing down TARGET, then restarting TARGET and ED. Everything was clean. Now, however, I make it a habit to open up the event window. Again, that was an intermittent problem, not a consistent one, and that's why I'm asking for details.