Also, if you have not already done so...go take a look in the HCS Forums and join their discord @major7079

Also, one common remedy as mentioned on the discord is:-

Make sure that you have voice attack target dropdown set to "Active window"

Hope this helps.

Clicker
 
Last edited:
Also, if you have not already done so...go take a look in the HCS Forums and join their discord @major7079

Also, one common remedy as mentioned on the discord is:-

Make sure that you have voice attack target dropdwon set to "Active window"

Hope this helps.

Clicker
Hi Clicker,

Two minds, one thought. This was exactly my thought and indeed this target dropdown was set to "Elite Dangerous". So I have switched it immediately to "Active Window" but sorrily this was not the solution. The delay is still present and commands are not processed correctly via voice attack.

But thanks, anyway.

Now I will try out your and AD's suggestions as other mentioned forum and discord tips did not help either.

Kind regards,
major7079 aka CMDR E.P. Cole
 
Hi Klicker and AD,
I have got my problem fixed by Gangrel on HCS Discord channel.
I do not now but somehow my keyboard press settings *durantion were all changed.
Now as I have set them back all to 0.050sec in the Voice Attack Profiler everything worked as intended so far I could see on my first attemps out in the black.
Thanky you for your patience and support.
Take care and o7,
major7079 aka E.P. Cole
 
I promised to report back when I get it and...here I am....I fnally received the slew upgrade and fitted/exchanged it in the Warthog throttle:
Source: https://www.reddit.com/r/hoggit/comments/bfh2fm/ive_upgraded_my_tm_throttles_slew_control/


And...OMG...this is such a great upgrade! A missing good analouge mini-stick is the only weak spot the Warthog has...it has it no longer.
Replacing it took around 10 minutes, but I was rather overcautious. Remove 4 screws, unplug the old slew thingy, replace and ta-da.

WORTH
EVERY
PENNY!
:D
 
Looks like an awesome improvement over the original.

I am tempted although the cost (~53UKP = NZ$110+) plus a three month wait is a tad sobering.

I admit, due to the relative uselessness of the current slew stick, I do not use it for anything.
What function, in game do you use the slew joystick for?

Cheers
Clicker
 
‘Kit...just ordered one anyway!

@M. Grey , while you had your throttle apart, I dont suppose you noticed if you could swap the mike switch with slew switch?

If this is possible, I’d rather use my thumb for the slew control.

Clicker
 
Last edited:
Wise decision...you'll love it! ;)

Hmmm...did not rly look. I can check later since I swapped the slew switch and replaced one broken hat switch TM sent me. Can compare both if the seem same/similar.
If they have same dimensions and the "key" at same position it should work. Taking the throttle apart is very easy.
 
Last edited:
I promised to report back when I get it and...here I am....I fnally received the slew upgrade and fitted/exchanged it in the Warthog throttle:
Source: https://www.reddit.com/r/hoggit/comments/bfh2fm/ive_upgraded_my_tm_throttles_slew_control/


And...OMG...this is such a great upgrade! A missing good analouge mini-stick is the only weak spot the Warthog has...it has it no longer.
Replacing it took around 10 minutes, but I was rather overcautious. Remove 4 screws, unplug the old slew thingy, replace and ta-da.

WORTH
EVERY
PENNY!
:D

OMG, I replaced a defective slew sensor with an original spare part from Thrustmaster a couple of years back. It works, but is still pretty much unusable. As you said, it's the only weak spot on the Warthog. Ordered!
 
Since replacing the stick and re-calibration, my profile sometimes stops, the Warthog not working anymore. Have to restart TARGET, reconnect Stick & Throttle.
Sometimes it works all day without issues though.
Any ideas?

Update:
Disabled this for most USB controllers/input devices and USB Hubs in:
Device manager > USB controller/device/Hub >power management > allow the computer to turn off this device to save power

Seems to work so far, no bugging out...yet.
 
Last edited:
I promised to report back when I get it and...here I am....I fnally received the slew upgrade and fitted/exchanged it in the Warthog throttle:
Source: https://www.reddit.com/r/hoggit/comments/bfh2fm/ive_upgraded_my_tm_throttles_slew_control/


And...OMG...this is such a great upgrade! A missing good analouge mini-stick is the only weak spot the Warthog has...it has it no longer.
Replacing it took around 10 minutes, but I was rather overcautious. Remove 4 screws, unplug the old slew thingy, replace and ta-da.

WORTH
EVERY
PENNY!
:D

MATE! That looks awesome. Thanks for looping back and sharing your experience with it. Oh boy am I tempted even more now!


Since replacing the stick and re-calibration, my profile sometimes stops, the Warthog not working anymore. Have to restart TARGET, reconnect Stick & Throttle.
Sometimes it works all day without issues though.
Any ideas?

Update:
Disabled this for most USB controllers/input devices and USB Hubs in:


Seems to work so far, no bugging out...yet.

Oh no! Not sure what might be happening there. Is there a way to contact the seller? Just thinking if its something with the upgrade that he may have seen it or know a fix, outside of something obvious like a pinched wire or loose connection.

Cheers, AD
 
Yep, he answers and is active on:

About my issue...2nd day, around 8h flight time...the issue did no occur again. Very sure it was related to USB controllers/devices/hub being turned off for power saving.
Such a game changer, the new stick feels very good, very intuitive.
As said...
WORTH...EVERY...PENNY! :D

Update: Got to fly a lot on weekend, no more issues...seems the power saving was the reason.
 
Last edited:
For anyone interested...

After upgrading Windows 10 to version 1903, device analyzer now seems to work on my PC (I could never get it to work over the last 2.5 years or so).

NOTE: if you use vJoy for anything and have not upgraded yet, be warned...it'll break vJoy.

Clicker
 
Hi all,

Public Service Announcement

Some time ago I posted some code which can read and process the status.json journal file.
Part of this code was to run a subroutine (function) with a loop to check the "Flags" key value and when this is non-zero, then we know the game is running and then set a bunch of state flags.

The issue I had at the time was that when running a TARGET script, it will time out after one minute if the game hadn't started in this time (which it never does).
Well, I've stumbled across a very old thread in another forum and have found that TargetGUI.exe can accept several command line switches, one of which is "-t" which sets the timeout value in milliseconds.

I've tested this and it still works with the latest version of TARGET and solves my issue.

Example: In the windows batch file I use to run my TARGET Script I now have the following:

Code:
c:
cd "\program files (x86)\thrustmaster\target\x64\"
start targetgui.exe -t 120000 -r "c:\targetscripts\ed_v400_dev.tmc" <--my script name

By the way, running "targetgui.exe -help" from a command line will pop up the following help box.

136298


Cheers
Clicker
 
Howdy y'all,
I've been out for a bit and see there have been some updates. I have the new v4.1.0 and when I went in to the user prefs, I noticed a lot of changes. (awesome work as always)
Where can I change the RepeaterAutoRelease value?
So, the last time I played I had it set in explorer mode and running v4.1.0 it is still set. I have looked to change it but don't know where it's at.
What is happening:
Repeater Fire: EXPLORER-SCANNER [ON] (PRIMARY)
after 10 seconds
Repeater Fire: EXPLORER-SCANNER [OFF] (PRIMARY)

Is there anything I can do other than going back and running v3.3.3, as this is the last version I can find the "define RepeaterAutoRelease 0" variable.
BTW, I posted this question on Steam earlier and you can ignore it there.

ANSWERED ON STEAM
 
Last edited:
Long time listener, first time caller...

I just about had everything working the way I expected and ran into an issue. My HOTAS is sending both the unmodified key and the AD script key. Also, when I run the script, the computer (W10) shows the throttle, joystick, and the TARGET virtual device. Example: If I try to remap the coolie switch, instead of getting [Joy 25] I'm getting [Joy 25]+[Joy POV1-Left]. I'm pretty sure the second button is the physical controller. It was working perfectly yesterday.

AFAIK, I only made one change to the script to alter the slew axes curve, which shouldn't have done anything to result in the effect above. Suggestions as to where I might look to find out why this is happening? (I'm not even sure what the proper term for this is, so my searches have been in vain.)

Edit: I think it may have had to do with something "holding on" to the joystick (possibly Oculus) which I did not exit before running the script. Re-closing everything, resetting the USB interface, and restarting the script seemed to work. (which is odd because I'd even done a re-boot, but with so many moving parts it's possible I started something before TARGET accidentally).
 
Last edited:
I have this same issue. I was never able to find a complete fix just a workaround. What I do is when I know I am going to play, I do a restart and start the scrip within seconds of logging in. As soon as I come to my desktop, I start 'TARGET GUI' and run the script. I always check to make sure only T-Rudder (because I have them) & Thrustmaster Virtual Game Controller (root) are the only controllers running when I open the 'Joystick Controller Panel'.
I have gotten to the point to just start it after I boot, leave it running minimized, just in the event that I may play sometime through the day. The resources are minimal, and it's ready for me when I need it.
If you, or anyone here, find a solution. I am more than interested. As I have been doing this for more than six months...
 
Hi all,

Public Service Announcement

Some time ago I posted some code which can read and process the status.json journal file.
Part of this code was to run a subroutine (function) with a loop to check the "Flags" key value and when this is non-zero, then we know the game is running and then set a bunch of state flags.

The issue I had at the time was that when running a TARGET script, it will time out after one minute if the game hadn't started in this time (which it never does).
Well, I've stumbled across a very old thread in another forum and have found that TargetGUI.exe can accept several command line switches, one of which is "-t" which sets the timeout value in milliseconds.

I've tested this and it still works with the latest version of TARGET and solves my issue.

Example: In the windows batch file I use to run my TARGET Script I now have the following:

Code:
c:
cd "\program files (x86)\thrustmaster\target\x64\"
start targetgui.exe -t 120000 -r "c:\targetscripts\ed_v400_dev.tmc" <--my script name

By the way, running "targetgui.exe -help" from a command line will pop up the following help box.

View attachment 136298

Cheers
Clicker

Great find! Although I know a while back AussieDroid started recommending running from the GUI; all this time I had been ignoring the GUI interface and just running Script Editor. Now I have a reason to use it.
Thanks for sharing!

(I started creating my personal TARGET script around the same time AussieDroid did)
 
Back
Top Bottom