I haven't had time to read all the posts in this thread but this Warthog scripting looks fantastic. I have a Logitech X56 which serves me pretty well, I just wish its programming app was as in-depth as this T.A.R.G.E.T software. There are 3 modes but you can't tie specific axis curves to each mode.

I'm considering buying the Warthog throttle to start with but I'd like to confirm that the software will allow multiple throttle modes. From what I see you have 3 modes, forward only, full-range and precision. So I would be able to switch between a -100 to 0 to +100 throttle and a forward only 0 to +100 range as well as a 3rd mode for precision? If that's the case that's enough for me to buy the Warthog and use this scripting.

On my X56 I can use the landing override for precision but switching from full range to forward only isn't possible without modifying the throttle, which would invalidate the warranty. I could split the throttle and use one axis for full range and the other for forward only but it's really cumbersome.
 
Hey there CMDR TCW | Jocki,

Everything looks fine from the code side of things. I've seen this too! I'm not sure of a solution unfortunately, but to share what I have found, since I introduced the software startup to my script is that it seemed to work fine when I was running Win7, but trying it since I upgraded to Win10 a few months back it just doesn't seem to work properly. Going by your screenshots I gather you are running Win10 too?

What I have noticed as well is that some exes seem to fire fine, but others do not. IIRC, things like EDMC & TrackIR still worked, but EDLaunch and few others didn't (I've had them disabled in my own version for a while so not 100% sure which worked and which didn't, but you could probably test the same your end). I was thinking it might be a permissions/security issues being it worked on Win7 but not 10, but could be completely wrong. Maybe its some other complexity/dependency with how EDLaunch loads?

I had a hunt around to see if there are any solutions, but didn't find anything myself. Doesn't seem to be many who use it. If the script file can run a .bat file, perhaps worth a try to create a quick batch file to trigger the exes externally to the script? I've been a bit too lazy to try it myself :p

Cheers,
AD

============

Hey there Brian of Ardagh,

Thank you! Does the Warthog scripting allow for multiple throttle modes? Absolutely! Could setup as many as you want in theory. There is a basic manual online which goes through all the actions you can perform on an axis curve (around page 27-> ). Useful for changing between SRV/Ship and the like or setting hard limits such as when you are using a cargo scoop or heading into station (this is what I use precision mode for myself).

One small thing to note, is that having multiple throttle axis curves set will be managed outside of ED (ie via the script). So if you change to a forward only setup for example, your conventional button to go into reverse will not work. Easy to overcome, by mapping digital back thrusters to your reverse button or somewhere else. :)

As a general comment on programming with a Warthog, the only thing I have found I cannot do is a quick 'double press' action (no biggie). The scripting is very powerful & really has few limitations other than a bit of a steep learning curve if not familiar with programming such things (ie me lol). As someone who also came from an X55 to a Warthog, I am still fond of the throttle on those kits & liked the setup overall, but once I got going with the Warthog it was a game changer! No regrets ... certainly couldn't go back.

Cheers,
AD
 
Last edited:
OK, I tested with a .bat file and get the same errors:

-> running the bat files directly works fine
-> running the bat files from tmc script throws the same errors as listed above
-> running the target service as admin also doesn't help.

since the launch from the .bat-file works fine it seems to be some kind of permission thing as mentioned above. Maybe I'll contact the thrustmaster customer service directly, maybe they can help. In that case I'll report back here ;)
 
OK, I tested with a .bat file and get the same errors:

-> running the bat files directly works fine
-> running the bat files from tmc script throws the same errors as listed above
-> running the target service as admin also doesn't help.

since the launch from the .bat-file works fine it seems to be some kind of permission thing as mentioned above. Maybe I'll contact the thrustmaster customer service directly, maybe they can help. In that case I'll report back here ;)

Thanks for testing it all out! Definitely pointing to some restriction or permission issue with the script then. Curious issue, will be interested to know what TM say about it.

Cheers,
AD
 
Hey there Brian of Ardagh,

Thank you! Does the Warthog scripting allow for multiple throttle modes? Absolutely! Could setup as many as you want in theory. There is a basic manual online which goes through all the actions you can perform on an axis curve (around page 27-> ). Useful for changing between SRV/Ship and the like or setting hard limits such as when you are using a cargo scoop or heading into station (this is what I use precision mode for myself).

One small thing to note, is that having multiple throttle axis curves set will be managed outside of ED (ie via the script). So if you change to a forward only setup for example, your conventional button to go into reverse will not work. Easy to overcome, by mapping digital back thrusters to your reverse button or somewhere else. :)

As a general comment on programming with a Warthog, the only thing I have found I cannot do is a quick 'double press' action (no biggie). The scripting is very powerful & really has few limitations other than a bit of a steep learning curve if not familiar with programming such things (ie me lol). As someone who also came from an X55 to a Warthog, I am still fond of the throttle on those kits & liked the setup overall, but once I got going with the Warthog it was a game changer! No regrets ... certainly couldn't go back.

Cheers,
AD

Thanks for the reply, I'll probably be replacing the throttle sooner rather than later. Will need to buy new mounting plates for the MonsterTech mounts before ordering the throttle. I'd buy the stick as well but I'm not ready to buy pedals.

The X56 throttle is getting flaky, I was getting close to a planet's surface when all of a sudden the boost kicked in and the FSD wanted to fire off. Luckily I was mass locked so the latter failed. I've contacted Logitech about it and they have a list of suggestions before replacing it.
 
Thanks for the reply, I'll probably be replacing the throttle sooner rather than later. Will need to buy new mounting plates for the MonsterTech mounts before ordering the throttle. I'd buy the stick as well but I'm not ready to buy pedals.

The X56 throttle is getting flaky, I was getting close to a planet's surface when all of a sudden the boost kicked in and the FSD wanted to fire off. Luckily I was mass locked so the latter failed. I've contacted Logitech about it and they have a list of suggestions before replacing it.


No worries at all :)

Those MonsterTech mounts seem pretty good. If the plate is large enough for the X56 throttle it should fit the Warthog Throttle. If mounting holes don't like up, some quality 3M (dual lock I think its called) double sided tape would probably do the trick. Super strong!

I've heard of similar ghosting issues with the X55 when I was using it. Sometimes, it can be a faulty wire inside shorting/moving as the throttle moves causing it to fire. Also heard the same can occur if there is not enough power going through the USB port/hub for the device. Latter you might be able to get around by trying other ports/hubs, unplugging other USB devices, restart/retesting. If its a wire then that could be a bit more 'fun' to resolve. :)

AD
 
Looking good - just one thing. multiple /////// ?

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////Hi AD.
Script is looking good. All single person controls are fine. Haven't yet tried any ED Crew fighter options, but should be in combat soon.

However, I have found that after compile and run, whilst Target Script Editor is running the profile. I get an unusual problem.

If I left mouse click on any open browser, text editor, word processor text window, e.g. browser address bar, I get the following:-
(This example is with TSE running).
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// and on and on.
The only solution is to stop running the script.
Pressing the right mouse button causes a simple // .
I have looked through the various .ttm and .tmh files for a single '/' without finding anything that l///////////////////////////////////////ooks out of the ordinary/////////////////////////////
oops. //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
I have gone back to the original zipped files and still have the problem.
This occurs whilst in w////////////////////////////////////////////////////////i//////////////////////////////////////////ndows, not playing ED.
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Oh. This is not a sticky / key either on keyboard or numpad.

I think this is one for the worzel gummidge's thinking head :)
 
Last edited:
There are a lot of // in your post ;) .. are you sure its not your keyboard mate haha! I joke ofc :)

When you start running the script, if you have the Event Tester window open, are you seeing anything outputting to the window? If yes, check your toggle positions and see if any may be in an ON position. Toggle the toggles, and see if anything changes in the Event Tester window. Loosing focus (such as tabbing out or selecting another window on second screen) would result in any held key presses from the script outputting to whatever is active. I don't think I have anything mapped to mouse at all, but that may be just what you see when selecting/activating a text box (its probably still 'pressing' in the background).

If the Event Tester is empty on run, then start the game and tab out before loading into a session and see if anything is triggering in Event Tester. If no, then load a game and repeat and see if anything changes.

Has it worked in the past? Does it happen 100% of the time? or are there any particular patterns to when it happens (such as when in SRV or Ship, docked, after combat etc)?

I had a quick look at the mappings in the script, and I only saw the Supercruise mapped to the / on the numpad, so not 100% sure what might be triggering. Hopefully the above can help narrow it down :)

As an alternative, I do not seem to get it occurring when I use the Steam Overlay Web browser. Not everyone is on Steam or wants to use it but I find it easy playing in a cockpit and might give you another way around it. I have my game running in Borderless mode too for reference.

Cheers,
AD


PS - You had me looking up Worzel Gummidge :) ... Then that OMG moment when I realised I recognised him from TV as a kid decades ago! Totally forgotten LOL
 
I've decided to buy the MonsterTech Warthog specific plates. Not cheap but I'd rather get the right plates.

I think the phantom button issue might be my USB hub. It is powered, 4 ports, but it's very old. I've got the X56 throttle and joystick as well as a TrackIR and an Xbox One controller. I've unplugged the TrackIR and the controller, so far no problems.

Still will prefer the Warthog.
 
Hi AD.
Well, I had a fully detailed step by step evaluation already typed out, then managed to lose it all. About 3hours of tests and re tests.
So, I shall summarise instead.
The event handler gave a clue.
You see that when the profile starts it runs state checks on some of the control switches.
The states checked for are slightly different depending upon whether the profile is run via Target GUI (see event-hander-1-.jpg) or Target Script Editor (see event-handler-2.jpg)
In both cases the Key Release: / (which I think is Numpad /) command is not actioned until the profile is stopped!
The control switches that are checked are Flight Assist (Z - Speedbrake), Galaxy Map (LeftShift SemiColon - Boat Switch), FSD (Numpad /), Landing Gear (Key L - EAC toggle) and Cargo Scoop (Home - RDR Toggle)
I repositioned the toggle switches to 'landed in station' positions. Landing Gear down, Cargo Scoop up, Map toggle to neutral, FA on (can't do anything about the numpad / key.
Then I began the good old method of try each one in turn.
The problem is related to the cargo scoop switch (RDRALT) state. If it is RDRNMR (ie Cargo Scoop up) there is no problem. If it is RDRDIS (ie Cargo Scoop down) I get the string of repeated '/'s.
The order of the state checks suggests that if the Cargo Scoop is 'deployed', the state checks are not completed, so the numpad / remains pressed until the profile is stopped, then the Key Release : / is actioned as part of the profile termination sequence (see event-handler-1.jpg)

What do you think?
I don't know where the initial control switch state checks are carried out, so i can't check it through :-(
Looks like a fairly quick fix though.
Over to you, good Sir.
https://1drv.ms/u/s!AnjIfzcFRXK_hlGnrJvr5TxfDl-5 Event-handler-1.jpg
https://1drv.ms/i/s!AnjIfzcFRXK_hlCExjlj9J2wfh26 Event-handler-2.jpg
 
Hey Paul,

Thanks for the info!

Tried to replicate the issue my end this morning. Can't seem to get the same behavior. Tried various states of the toggles prior to running script and then toggling when running but that mysterious '/' isn't appearing.

Looking into it further, the only key that I could find mapped to the / (and not the numpad version) was the Mic. This is mapped to two commands on the throttle, one in the center push on the thumb hat switch (where your panel access & thrusters are) and also on the left Motor toggle (down position). Those Motor toggles lock in down position to keep mic open rather than using PTT on the thumb hat switch. If that is down I could get the same output into the Event Viewer. Could you double check these on your end please and see if it makes any difference?

If that doesn't help could you let me know what user settings you are using for the CargoPrecisionMode & CruiseOnThrottle. They are the only settings I can think of that might impact here.

Cheers,
AD
 
I've decided to also buy the MFG Crosswinds pedals. I don't really need them as the X56 joystick twists and I'm not replacing it just yet but I've wanted good pedals* and might as well get used to them before replacing the X56 joystick.

I'm assuming I'll have to tweak the binds as the Warthog joystick won't be present. I do have the TrackIR so that's a plus for the scripting.


*I have the CH pedals but never liked them, they felt clunky and aren't wide enough. Selling them off might cover about 1/2 the cost of the Crosswinds.
 
I've decided to also buy the MFG Crosswinds pedals. I don't really need them as the X56 joystick twists and I'm not replacing it just yet but I've wanted good pedals* and might as well get used to them before replacing the X56 joystick.

I'm assuming I'll have to tweak the binds as the Warthog joystick won't be present. I do have the TrackIR so that's a plus for the scripting.


*I have the CH pedals but never liked them, they felt clunky and aren't wide enough. Selling them off might cover about 1/2 the cost of the Crosswinds.

Niiice!! Not that I am an expert in rudder pedals, but I have been super super happy with my set. Precise, comfortable, adjustable. Hope you do not have to wait too long to get yours.

In terms of my Warthog setup, the MFGs are separate, so only mapped in the ED config settings, but I did set a few things in the MFG Crosswind control panel to combine the toe brakes etc. I have a pic in my guide to what I use. Set once and forget. :)
 
Amazing script! but i dont have those Crosswind Rudders, and i got stucked...
Dont know really what exactly to do, cause i am quiet new in the game. i got TM Warthog and TrackIR5 + Cougar MFDs, and HTC VIVE (which i am currently not using).


I did the 1st and 2nd Training Mission. In the second mission, i should go to Azeban City. But i stuck in that "Supercruise" mode. i cant accelerate... Warthog Throttle does not recognise my command...It says: stay in the blue area for distance and speed. but i have no access to the distance? If i hit the "J" Button to exit supercruise, i go to far... see screener: --> https://gyazo.com/fce80517a75e29ef3dc46ed0608c0ce7


may someone help?
thanks & cheers
 
Just a short info about my earlier post (https://forums.frontier.co.uk/showthread.php/293027-Aussiedroid-s-Enhanced-Thrustmaster-Warthog-Script?p=5998681&viewfull=1#post5998681)

Thrustmaster support told me to make an extra shortcut of the game exe and link the script to this shortcut. However this solution is still not working for me. For now I'm leaving this, since I have to get my joystick replaced (weird ghosting on the z-axis of the T.16000M), maybe I will fiddle a bit around with it another time.

o7
 
Thanks for the update CMDR TCW | Jocki!

I had actually already tried that as well. No luck my end either. Seems like its an issue on TM end for this one.

For now, I'll leave the software startup section in my script as it may work for some using Win7 but may need to look to remove it in the future if its not of much use.

Cheers mate!
AD
 
AussieDroid,

Have you heard anyone having this issue? I have a Thrustmaster FCS (stick and throttle - pedals too). I went into TARGET and was able to put curves in and everything. But when I go into ED and try to actually map my buttons the Throttle (gas slider) and the "twist" on my stick end of being the same button from ED. Not sure why this would happen, I went to REDDIT and on the HOTAS page someone else is having similar issues. Any ideas? Is there something I am just forgetting to do?
 
Back
Top Bottom