Help with Thrustmaster Controller Setup PLEASE.
-
I have tried to get Muds profile to work to no avail and now resigned myself to the fact that I am just going to have bind joystick and throttle commands within the controller setup.
The problem now is that the only way I can get the game to see the HAT switches on the Throttle ( the HAT next to the mini joystick ) so that I can bind them to commands is to select the Throttle - HOTAS Warthog in the Controller options.
However if I do this I cant get the Joystick axis to work at all even though all the joystick buttons are seen.So how do I get the game to see all my Warthog axis and buttons.
This is so frustrating.
Please can somebody help me out I am at a loss how to resolve this and actually start to learn and enjoy this game.
Thanks
-
Try out my profile?
-
Thanks for the reply Ice
Just had a look at your profile, looks complicated and I only have the one monitor so I don’t know if this profile would be suitable for me. I assume I would have to edit it to remove all the touch screen commands so that the profile would work with the standard 1 monitor setup.
-
You only need the ver6.tmc files, which is the same for both 1-screen and 2-screen setups. The rest of the “complicated” stuff is due to Helios and YAME integration, both of which have nothing to do with the TARGET profile.
Oh, and you’d want to use my .key file as well. -
Gave it a try Ice, Joystick commands seem fine unfortunately none of the switches and buttons on the base of the Throttle are seen.
No idea whats up with my controllers buttons / switches in rthis game. All work fine in DCS and Battle of Stalingrad. Just Falcon 4 BMS seems to cause issues.
-
The problem now is that the only way I can get the game to see the HAT switches on the Throttle ( the HAT next to the mini joystick ) so that I can bind them to commands is to select the Throttle - HOTAS Warthog in the Controller options.
However if I do this I cant get the Joystick axis to work at all even though all the joystick buttons are seen.That’s normal behavior, only one HAT is available within BMS. You should use the Thrustmaster Target software to Assign functions to the second HAT. You should never select the throttle on the main controller page, that will mess up everything. In the main controller page select the device that steers the aircraft, so always the joystick, and never change that…… That’s why the joystick axes don’t work when you select something else.
Verstuurd vanaf mijn F5121 met Tapatalk
-
Thanks Terminator.
Am having problems getting any of the posted profiles to work properly, probably due to the fact I have a force sensor mod in my Warthog joystick which I am assuming this is the problem.
But I can get the Joystick / Throttle to work within BMS controller setup and bind commands to axis and buttons except for that HAT POV on the throttle. I am just going to have to accept that this will be the best I can get and live with it.
Many thanks for the input.
Cheers
-
I wouldn’t give up just yet Zenith.
I am sure there’s a solution and unless the force sensor mod makes TARGET/TM scripts unable to deal with the throttle hat, I think you’ll eventually solve this.
I’ll just run through some AFAIK stuff that you may already know but just maybe one of these things can help you out.
1. You can use TARGET to bind your stick and throttle into a unified VIRTUAL device. If and when you do this, always turn on the virtual script before starting Falcon. Otherwise, there’s a bunch of weird things that will happen but basically Falcon is trying to make itself flyable as best it can using your HOTAS as a DIRECTX device. This can screw up your bindings and so what I’ve done, and it seems to work, is after you get everything (or just about everything) working right to make the following files readonly: devicesorting.txt axismapping.dat [yourkeyfile].key. You may have to make them writeable if you want to change something (but not if you are just going to map a button to a keyboard command within TARGET).
2. As a virtual device (unless your mod prevents it) you can now configure a POV on your throttle to fake as a HAT switch. AFAIK Falcon will no longer see that POV as a POV at all. You can either trick Windows/Falcon into thinking it is a 4way HAT or 4 distinct Direct X buttons that you assign or even keystrokes (which is mostly how I do it). As long as you can get TARGET or the TM scripts to override DIRECTX output you should be able to solve this. So, maybe the mod changes how a TM script addresses your throttle POV, if so maybe then all you need is to tweak that part of the script and you’re gold. I don’t use scripts I use TARGET so I don’t know even what to look for in those scripts, but maybe someone else does.
If possible maybe play around with TARGET and see how it recognizes the throttle POV and if you can trick Windows into thinking it’s something else.
-
Gave it a try Ice, Joystick commands seem fine unfortunately none of the switches and buttons on the base of the Throttle are seen.
No idea whats up with my controllers buttons / switches in rthis game. All work fine in DCS and Battle of Stalingrad. Just Falcon 4 BMS seems to cause issues.
Yeah, I’ve “remmed” them out for the moment. I use this with a touchscreen so didn’t really need the buttons on the base. If you want to activate them, I’m afraid you may have to learn a little bit about TARGET scripting; but I’ve left enough of the old data there that it should be easy enough to “reverse engineer” and make sense out of them.
-
If you have the time, we can go on voice comms (Skype or TS3) and this can be sorted in 10 minutes.
-
Really appreciate the help guys.
Yeah I’d be up for a chat on TS3 Ice, just let me know what time you would be available.
