Hmm, maybe it needs to be done with S Curve not J Curve (might need to look back on the manual to see what may be best). I know I had a lot of back and forth trying to get things work properly for the 80% limited range one, until I changed it to a J Curve but perhaps the trimming of the throttle doesn't play well with it.
 
I'm looking for some suggestions on getting this up and running. I have the Warthog and Saitek Combat pedals. Here is what I've done:

Copied the Binds to the Elite binds folder and selected it in Elite.
Ran the script i Target Script Editor reports that compile successful.
Load Elite and throttle, thrusters not working plus some others. There are some things that work like landing gear, scoop, TrackIR pause center, etc.

I open device analyzer and throttle axis is alive as are all of the other buttons.

Any suggestions? Sorry to be a pain it seems like this is a slam dunk for everyone else but me :)
 
I'm looking for some suggestions on getting this up and running. I have the Warthog and Saitek Combat pedals. Here is what I've done:

Copied the Binds to the Elite binds folder and selected it in Elite.
Ran the script i Target Script Editor reports that compile successful.
Load Elite and throttle, thrusters not working plus some others. There are some things that work like landing gear, scoop, TrackIR pause center, etc.

I open device analyzer and throttle axis is alive as are all of the other buttons.

Any suggestions? Sorry to be a pain it seems like this is a slam dunk for everyone else but me :)


Hi there CrackerJack,

It's not a pain. Happy to help if I can mate.

First thing, if I can check, are you running the latest 2.2.7 version? Reason I ask is there was a bug in 2.2.6 and earlier where the throttle would be dead in ED until you lifted the arm and locked it in the down position. This in the game cuts the throttle to 0%, but previously it would not work until it was activated for the first time. If running an older version please update and retry, else you can try to use the downwards locked position on the throttle once to unlock (but would recommend updating :)).

Can you be specific what other buttons may not be working?

Please be aware as well, that the pedals will likely need to be mapped on your first setup as I am using a different brand. This shouldn't take long to do in ED bindings config.

Cheers,
AD
 
Thanks for you script. :D

I just buy my new warthog and seem target set my joy stick roll left little bit so I use software calibrate fix and my joystick point to center perfectly in target.
but after I run your script and map roll to my joystick then ship make slow roll to right and I have to fix but increase dead zone in ED setting and it is ok now.


I'm learning in target script , Do target has command script to trim roll ? I don't want to use dead zone.

ps. I use saitek pro flight rudder pedals for yaw.
and sorry for my bad english


EDIT:

seem I found the command :D
TrimDXAxis(DX_X_AXIS, 50);
 
Last edited:
Thanks for you script. :D

I just buy my new warthog and seem target set my joy stick roll left little bit so I use software calibrate fix and my joystick point to center perfectly in target.
but after I run your script and map roll to my joystick then ship make slow roll to right and I have to fix but increase dead zone in ED setting and it is ok now.


I'm learning in target script , Do target has command script to trim roll ? I don't want to use dead zone.

ps. I use saitek pro flight rudder pedals for yaw.
and sorry for my bad english


EDIT:

seem I found the command :D
TrimDXAxis(DX_X_AXIS, 50);

Cool you found it .. yes you can trim if you need, but it shouldn't really be required. From memory I didn't have deadzones setup in the ED profile side as I found no issues personally... but anyways thank you!
 
Since the last big Win 10 Update I have a bug with TARGET. Warthog works fine, so does the TARGET profile.
When I "STOP PROFILE" the software crashes, have to kill the task. This results in the PC not shutting down correctly.

Tired some of these fixes, still not fixed.
http://theairtacticalassaultgroup.com/forum/showthread.php?t=18557

Anyone experiencing this too?

Did you use the last Target version? 3.0.16.615v2 : https://support.thrustmaster.com/en/product/hotaswarthog-en/
Did you use TS3 at the same time?
Try to running ts and/or target as administrator to see if that change something. (Right click / Run as administrator)
If you use TS3 and that still crashes, try to close Ts3 before closing script to see.
If you use TS3 and previous "try to fix" don't work, don't use TS3 (or target) any more while waiting for a fix from thrustmaster / teamspeak (thrustmaster are aware of the problem)
If you use TS3 you can also try to desactivate Gamepad and joystick hotkey support plugins to see..
 
Last edited:
Hi Aussiedroid,
I need help for use TARGET to mapping keyboard to run macro text chat ... like

F1 = "Hali cmdr. Sorry for fancy meeting out here but you have 10 second to cut your engine for cargo scan , we just need stuff in your cargo , this is fancy pirate operation :p "
F2 = ....
F4 = "Fly save out there , thank for your corporation and have a nice day Cmdr."

I have Razer keyboard but software to make macro mapping has virus so I think target can do this job ,
I try to use command MapAxis(&Input device, physical axis name, dx_axis name, option1, option2);
but I don't know &input device name for keyboard device

can you please give me simple coding sample for this fun macro :p

Thank you.
 
Last edited:
Since the last big Win 10 Update I have a bug with TARGET. Warthog works fine, so does the TARGET profile.
When I "STOP PROFILE" the software crashes, have to kill the task. This results in the PC not shutting down correctly.

Tired some of these fixes, still not fixed.
http://theairtacticalassaultgroup.com/forum/showthread.php?t=18557

Anyone experiencing this too?

Ha... Yep, I'm getting the same thing. Same target script I've been running for a couple of years, works fine but clicking the stop button to stop it running sometimes fails and the Target script app needs to be end-tasked to be closed. Then, as you say, when I try to shut down, it doesn't shutdown, have to switch off or reset.

Hadn't considered a Windows change, thought it may have been the Tobii 4c Eye Tracker that I've recently installed conflicting with it.
 
Hi Aussiedroid,
I need help for use TARGET to mapping keyboard to run macro text chat ... like

F1 = "Hali cmdr. Sorry for fancy meeting out here but you have 10 second to cut your engine for cargo scan , we just need stuff in your cargo , this is fancy pirate operation :p "
F2 = ....
F4 = "Fly save out there , thank for your corporation and have a nice day Cmdr."

I have Razer keyboard but software to make macro mapping has virus so I think target can do this job ,
I try to use command MapAxis(&Input device, physical axis name, dx_axis name, option1, option2);
but I don't know &input device name for keyboard device

can you please give me simple coding sample for this fun macro :p

Thank you.

Hey Karost,

Interesting idea, I like it, but I think this would be a bit involved. As in it wouldn't be a code sample/one liner, likely more a macro needs to be written.

Not sure if you could map back out to a keyboard key though using the Target software, but should be able to map to a button on the HOTAS using Target, maybe a hat switch or something may be appropriate.

The first part of the macro would need to navigate to the Comms panel and select the chat box. Then once selected, I think you would need to spell out the phrase to say with a series of key presses. Then finally 'Enter' the chat text and exit the comms panel. I think it would be doable, but might take me a little time to nut it out.

I will add it to my list of improvements I want to do and if I can I will get back to you with some further ideas in the mean time. :)

Also appreciate your feedback on if you could have 3-4 predefined chat lines, what would you choose? Would a different set per 'task' be needed or more generic ones might be fine?

I don't PvP/Multiplay etc much so not sure what would be best to include other than the obligatory wave :p


ALSO

For everyone, I am working on an updated version for the 2.3 release. Lots of small changes, code cleanups and improvements, and some cool new features I hope you will all like. Still testing eagerly awaiting the beta to see if there is any new commands to add as well. Keep an eye out :)



Cheers
 
Last edited:
Ha... Yep, I'm getting the same thing. Same target script I've been running for a couple of years, works fine but clicking the stop button to stop it running sometimes fails and the Target script app needs to be end-tasked to be closed. Then, as you say, when I try to shut down, it doesn't shutdown, have to switch off or reset.

Hadn't considered a Windows change, thought it may have been the Tobii 4c Eye Tracker that I've recently installed conflicting with it.

It is good to know that it is not just my script (although that doesnt really help on a solution lol), but perhaps something more on the software side in Win10?

It sounds like it is failing to unmount the virtual device, and restore the separate devices. If its not the Target software, perhaps it is the USB drivers causing the issue (worth checking if mainboard manufacturer has any updates)? Does running the script in Target GUI help?
 
Last edited:
Did you use the last Target version? 3.0.16.615v2 : https://support.thrustmaster.com/en/product/hotaswarthog-en/
Did you use TS3 at the same time?
Try to running ts and/or target as administrator to see if that change something. (Right click / Run as administrator)
If you use TS3 and that still crashes, try to close Ts3 before closing script to see.
If you use TS3 and previous "try to fix" don't work, don't use TS3 (or target) any more while waiting for a fix from thrustmaster / teamspeak (thrustmaster are aware of the problem)
If you use TS3 you can also try to desactivate Gamepad and joystick hotkey support plugins to see..

Tried everything™:

  • Latest TM drivers and TARGET installed.
  • Run as Administrator
  • Different USB Ports
  • USB 2.0
  • USB 3.0
  • NOT use the USB Hub
Have TS3 installed but not using it.
So TM is aware of the problem? I'll submit another ticket then. :D

Ha... Yep, I'm getting the same thing. Same target script I've been running for a couple of years, works fine but clicking the stop button to stop it running sometimes fails and the Target script app needs to be end-tasked to be closed. Then, as you say, when I try to shut down, it doesn't shutdown, have to switch off or reset.

Hadn't considered a Windows change, thought it may have been the Tobii 4c Eye Tracker that I've recently installed conflicting with it.

I have the 4c too, worked before with TARGET. Don't think it's realted to 4c.

---

When I deinstall and reinstall TARGET (and/or the Warthog drivers) it works for one reboot.
Also seems to work when I start the PC with Warthog disconnected, again also till next reboot.

TARGET combines the physial devices to one logical device. Seems to be the "speperation" of the logical device back to 2 physical devices that does not work correctly.
Not in the mood currently to try if a clean install would solve it. :p
 
Last edited:
Tried everything™:

  • Latest TM drivers and TARGET installed.
  • Run as Administrator
  • Different USB Ports
  • USB 2.0
  • USB 3.0
  • NOT use the USB Hub
Have TS3 installed but not using it.
So TM is aware of the problem? I'll submit another ticket then. :D



I have the 4c too, worked before with TARGET. Don't think it's realted to 4c.

---

When I deinstall and reinstall TARGET (and/or the Warthog drivers) it works for one reboot.
Also seems to work when I start the PC with Warthog disconnected, again also till next reboot.

TARGET combines the physial devices to one logical device. Seems to be the "speperation" of the logical device back to 2 physical devices that does not work correctly.
Not in the mood currently to try if a clean install would solve it. :p

Under Search Windows : search for "game controllers" then launch "Set up USB game controllers" (without target runing and all your stuff connected)... how much controller windows see and in what order?
Did you use an AIO with software control?
 
Last edited:
Under Search Windows : search for "game controllers" then launch "Set up USB game controllers" (without target runing and all your stuff connected)... how much controller windows see and in what order?
Did you use an AIO with software control?

Thx for the response!

There's just the controllers I use, been using for +1 year, no changes to controllers.
From "memory"...

  • vJoy - Tried once for JoystickCurves, not using, could deinstall, was installed before TARGET, used to work with TARGET; Also left-over from Saitek Software I think.
  • G13
  • CH Pro Pedals
  • TM Warthog Joystick
  • TM Warthog Throttle
When TARGET running I see in device manager the new combined TM Devices.

Did you use an AIO with software control?
All-in-One with software control?
 
Watermods AIO (like corsair H80i, H110i.... with software management corsair link if corsair aio..)

In game Controllers, click advanced and put TM Warthog Joystick or Throttle as prefered device. restart PC and give a try with stop script in target script editor.
If that don't work, try to disconnect G13, desinstall vJoy and give another try. (be sure one of TM device is always prefered device)

ps: Sry Aussiedroid to be off topic :( just trying to help
 
Last edited:
No AIO Watermods.
Will try the prefered device thing and deinstalling vJoy.
Weird thing s is NOTHING was changed, it suddelny started to bug. Only thing was the major Win 10 Update on 7.02.2017, seems to have started then.
Seems not that uncomon though. I contacted TM.

And this:

Sry Aussiedroid to be off topic and hijacking the thread. It's over soon and you can "hint" me anytime to open a new thread.
 
Last edited:
Hi Aussiedroid,

Thanks for reply :D

I agree to use button on the HOTAS using Target, there has many combine key to get this jobs done and it easy to do.

for version 2.3 if your code cleanups that will have a lot of new coming for try to use it because your work has a big advantage for dynamic curve profile switching.
It is a deep learning curve for players who don't have coding experience but payoff is a big advantage :D


Cheers
 
Back
Top Bottom