Maybe one you can help me with my Thrustmaster TARGET problems

[Mot]

So my t16000m FCS Flight Pack arrived last week, unfortunately I've been too sick to give it much use until yesterday. I had a quick go when it got here, it worked out of the box fine - with no Thrustmaster software running, ED detects the entire system and it works fine, but I want (need) to use some curves to get the best out of it. I have spent most of the past day, barring sleep, trying to get the TARGET software to work with ED. After setting up the basic curves and dead zones in Target (I know ED has dead zones in game), running the script and booting ED, for some reason the 'Thrustmaster Combined' profile is not detected in game, there is not response from the stick in menu screens either.

The profile I downloaded from the Thrustmaster website works when installed and run, but for some reason unknown to me I am having problems rebinding the controls in game to something I prefer. Which is a pity because now after tasting the curves and dead zones I am determined to find a solution

I have contacted Thrustmaster support and they "can not provide support on custom scripts". (they also only recommend using silicon based grease/oil/lube on plastic components if anyone is interested). My Thread in the Frontiers support Forum has gone unanswered. Social media has been no help. Most people seem to poo poo TARGET here and elsewhere on the web, but I have seen some people using it with no problems.

I have tried fixes and registry tweaks and uninstalling and reinstalling. I have tried different USB ports as my HOTAS is plugged into one of those Inateck USB expansion cards Oculus recommends. I have tried all sorts of things.

I understand there is axis limitation thing when using TARGET, but if TARGET worked I could probably find work arounds. I would like to use something similar to the default ED t16000m HOTAS binds (with some modification of course), only with some curves and small dead zones to stop drift while using the other axis.

Short of the dreaded wipe c: and reinstall windows... I'm out of ideas. I'm going to try some other Joystick Curve programs tomorrow, but that will mean learning how to use more programs and from my short trials today, I had no success.

Thanks in advance.

 

[Orvidius]

I have the same HOTAS, but instead of TARGET, I'm using Joystick Curves to get my curves on the mini-stick on the throttle. It's a little tricky to get ED to use that instead of pulling input straight from the physical stick, but it works very well.

 

[vic]

I have the t16000 thrust stick and using the target software with no issues. But I don't load any profiles. I just let it detect my stick and then just go directly to the axis properties in the target sofware and manually adjust them to my liking.
edit:: please ignore my post. I was mistaken I dont use the target sw.

 

[Mot]

I have the t16000 thrust stick and using the target software with no issues. But I don't load any profiles. I just let it detect my stick and then just go directly to the axis properties in the target sofware and manually adjust them to my liking.

That is what I have been trying to do....

 

[CylonSurfer]

I created my own profile, never downloaded one so I'd bin that and start again from fresh.

Start a new profile, select your stick and throttle from the gui and then start with your curves and finally the binds.

 

[imski]

Aussiedroid seems to be the TARGET/Scripting guru in these parts.

Check out https://forums.frontier.co.uk/showt...stmaster-Warthog-Script?highlight=aussiedroid

 

[Mot]

I created my own profile, never downloaded one so I'd bin that and start again from fresh.

Start a new profile, select your stick and throttle from the gui and then start with your curves and finally the binds.

That is how I tried first. The problem is the 'Thrusmaster Combined' profile it creates when you run the script, does not show in elite, and the stick is unresponsive.

 

[Mot]

Making some progress. Found that it works, just doesn't show up in ED controls. And there was no response in menus because I hadn't bound anything to navigate menus in TARGET... who'd have thought

Does anyone have a script to combine the two toe brakes into one axis so I can use left brake to thrust left and right brake to thrust right? My pedals are plugged into my throttle and apparently this makes a difference with the way the script needs to be.

I'm having other issues now(the buttons have merged and some are present on both joysticks, do I have to bind them as well to not have repeats across my throttle and stick?)... It's going to be a long week I can tell already.

 

[CylonSurfer]

That is how I tried first. The problem is the 'Thrusmaster Combined' profile it creates when you run the script, does not show in elite, and the stick is unresponsive.

It won't. You have to go to the custom profile in Elite and then bind all of your hotas controls to the ingame actions..You may need to use keyboard and mouse to get there until your binds are setup.

 

[Mot]

I've spent another 5ish hours figuring it out so I know that now, but thanks for trying to help anyway. If someone had said 'TARGET is a completely blank slate and needs every little thing, including the game menu programmed' then I might have got it to begin with. Oh well. Making more progress on a basic bind to play with now tho.

 

[CylonSurfer]

I've spent another 5ish hours figuring it out so I know that now, but thanks for trying to help anyway. If someone had said 'TARGET is a completely blank slate and needs every little thing, including the game menu programmed' then I might have got it to begin with. Oh well. Making more progress on a basic bind to play with now tho.

Sorry, I thought you were having issues with your TARGET profile not working, I had no idea that you were trying to use a joystick preset in Elite for a hardware combo that is being hidden as soon as you launch your TARGET profile. Just think of it this way: as soon as you start your TARGET profile Windows will no longer see your original HOTAS, it will see a virtual device instead.

Anyway, good luck with your binds, TARGET can do some pretty cool stuff, it's worth looking at the layers feature so you can create some nice layer shifts which enables you to reuse hats etc for different functions. I have one hat assigned to standard pip management, but when I have another button pressed the very same hat becomes a pip profile selector allowing me to select predefined pip profiles for combat, speed, defensive etc...

 

[Mot]

Aussiedroid seems to be the TARGET/Scripting guru in these parts.

Check out https://forums.frontier.co.uk/showt...stmaster-Warthog-Script?highlight=aussiedroid

Cheers.

 

[Mot]

All working now! Thanks to all who helped. I had a long Modular Terminal Grind sesh with CMDR ESB yesterday, and it works well. And today I solved my combined toe brake woes. So just to sum up:

*The reason TARGET wasn't working was I had nothing bound in TARGET. I didn't know that I had to bind *everything*. After binding all the buttons on my Joystick and Throttle in TARGET to the USB Keys and such, and assigning some of those to menu functionality it works fine. The curves I set up did wonders for the sensitivity- moving the stick slightly now results in more subtle control of my ship.

*The reason no controllers were appearing is when you run a TARGET Script it hides the devices and replaces them with a single combined 'virtual device' that doesn't appear on the ED Controller drop down, but still works in ED, I just had nothing bound in TARGET.

*Combined toe brakes into one axis: After speaking with Aussiedroid (who had used someone elses script which didn't work for me, but sent me in the right direction) and Frank G (because he mentioned it in another of my threads, who suggested another program) I stumbled across one of Gruffta's posts (here it is: https://forums.frontier.co.uk/showt...Flight-System-T-A-R-G-E-T-Script-v1?p=5396408 it doesn't seem to always show on search so I'll share) while searching the forum for information, which had exactly what I needed. The script Aussisdroid used was for when the pedals are connected via USB, and this wasn't working for me as my pedals are connected via the throttle (there is an RJ12 plug on the pedals, and I didn't get the USB adaptor in my Flight Pack). Grufta had figured out how to code the specific instance of the pedal connected to the throttle for the combined axis toes. Which is great, because it frees up an axis and you need all the axes you can get with the DirectX axis limit of 8.

*I didn't look further into why the profile from the Thrustmaster website was behaving strangely when trying to rebind in ED.

Now that I had some experience with TARGET, it is making much more sense to me now. I'm still working on my TARGET script and binds, although it is much easier now and I'm making progress. Now for some layers...

By the way, it's a great bit of kit for the price. I think with some Nyogel on the throttle rails it'll be even better.

(This post is coming up on google fairly high when searching the issue so if anyone who is having similar issues wants my work in progress TARGET script, or even my ED .binds file, PM me and I'll hook you up)

Thanks again.

 

[Mot]

Sorry, I thought you were having issues with your TARGET profile not working, I had no idea that you were trying to use a joystick preset in Elite for a hardware combo that is being hidden as soon as you launch your TARGET profile. Just think of it this way: as soon as you start your TARGET profile Windows will no longer see your original HOTAS, it will see a virtual device instead.

Yeah, I should have read the manual, but that is pretty big and I've got a nasty flu and was stressed... and I usually only refer to documentation when I really need it. I'm a 'dive in and try and work it out first' kind of guy. Then I'm a 'ask the interwebs' kinda guy. Then maybe a manual reader.

Anyway, good luck with your binds, TARGET can do some pretty cool stuff, it's worth looking at the layers feature so you can create some nice layer shifts which enables you to reuse hats etc for different functions. I have one hat assigned to standard pip management, but when I have another button pressed the very same hat becomes a pip profile selector allowing me to select predefined pip profiles for combat, speed, defensive etc...

I'm thinking of doing something similar and a '1 press auto-dock-request' to start with.

 

[MajorPeabody]

Request config files

<snip>

*I didn't look further into why the profile from the Thrustmaster website was behaving strangely when trying to rebind in ED.

Now that I had some experience with TARGET, it is making much more sense to me now. I'm still working on my TARGET script and binds, although it is much easier now and I'm making progress. Now for some layers...

By the way, it's a great bit of kit for the price. I think with some Nyogel on the throttle rails it'll be even better.

(This post is coming up on google fairly high when searching the issue so if anyone who is having similar issues wants my work in progress TARGET script, or even my ED .binds file, PM me and I'll hook you up)

Thanks again.

I'm just re-entering the game with the Oculus Rift and Thrustmaster T16000M stick & Throttle.
Configuring things has been....challenging. I'd be very interested in what you've ended up with.

Should I continue trying to use the combined virtual device (TARGET), or let ED detect the devices directly? I'm NEVER gonna be a crack combat pilot, but would like to control things without having to remove teh headset to find the keyboard.

Thanks!!

MajorPeabody,
Carebear - n00b

 

[lausianne]

My T.16000FCS arrived a couple of weeks ago, no luck with TARGET. A mate simply said "it's crap". And that matches my experience with it. I had it figured out, and eventually all seemed to be working. Then it started crashing, just stopped responding, suddenly joystick and/or throttle were no longer recognized mid-game. Updates, restarts, no luck. Eventually I gave up and set the HOTAS up without TARGET. That works fine, basically, but I need curves ...
Will try Joystic Curves now, but really don't want to go through all the keybinds setup again.
Ingame setup is no use, unfortunately, that's only for deadzones, or am I overlooking something?

EDIT: Joystic Curves works well. Cannot download latest drivers due to Sourceforge issue, but the old ones seem ok. This is just what I'd hope would be delivered with a HOTAS, simple and effective. Not praising Saitek quality here, but at least I never had a problem with their software ...