Release Aussiedroid's Enhanced Thrustmaster Warthog Script

Aussiedroid · Jul 24, 2017

Hey Leo,

Thank you, I really appreciate the feedback! I don't think you are doing anything wrong

Just to state up front, I don't have Thrustmaster pedals myself, so I have tried to add the code to support excluding (UseRudder=1) them essentially so they can still be used/mapped in ED. The issue may be at my end

Hard to test off course, but I do recall some user comments a while back saying that it worked. Now I think the pedals I am referring to as T16000 are one in the same to what you are using. I think TM only do the one set, but include it in a bundle with the T16000 too, so I think it should be the same code/config.

What I can see from the error, is that the script seems to be failing at the start where it is initialising the hardware. I'll take a closer review of the code after work and see if I may have made an error. Essentially, all it should be doing is telling TM Software that this hardware is not to be included in the virtual device created when the script runs, so it can be configured externally.

Let me look into it further Leo and will get back to you.

Cheers,
AD

=========
Hey CMDR Corleone,

Thanks for getting back to me. Yeah I really struggled with the lack of dent for the full range throttle too. When I need to be really precise I need to look still or use the Precise throttle control if appropriate. Still took me many months of practice to get decent at it! Option is there if you change later though.

Glad to hear the mappings are starting to become second nature. Few more sessions and I bet you will not need the maps open! Oh and no detracting at all. Always happy to help, and besides, I have had nothing but nice people asking questions

Cheers,
AD

Leo Sagan · Jul 24, 2017

Aussiedroid said:
Hey Leo,
Just to state up front, I don't have Thrustmaster pedals myself, so I have tried to add the code to support excluding (UseRudder=1) them essentially so they can still be used/mapped in ED. The issue may be at my end Hard to test off course

Oh I see. Well, if you need logs, diagnostics or any info I might find on my machine, I'd be glad to oblige.

Aussiedroid said:
, but I do recall some user comments a while back saying that it worked.

So there's still hope for me then

Aussiedroid said:
Now I think the pedals I am referring to as T16000 are one in the same to what you are using. I think TM only do the one set, but include it in a bundle with the T16000 too, so I think it should be the same code/config.

I concur.

What I can see from the error, is that the script seems to be failing at the start where it is initialising the hardware. I'll take a closer review of the code after work and see if I may have made an error. Essentially, all it should be doing is telling TM Software that this hardware is not to be included in the virtual device created when the script runs, so it can be configured externally.

Let me look into it further Leo and will get back to you.

Subscribed to the thread !

Thanks for the quick reply AD, but please take your time : while I'm litteraly drooling when I read your script features, I also understand that this is essentially free hard work you're doing here

Aussiedroid · Jul 24, 2017

No worries at all

In the mean time, not to be 'that IT guy', but if you can, turn off the PC, unplug all your Thrustmaster devices and any other game controllers you have connected. Restart PC without them plugged in. When windows is started, plug in the Joystick, then Throttle, then Pedals and give it time for it to install device between each plug in. Start the TARGET software etc and try it again.

Seen it quite a few times now, where new users have issues getting it working initially. Sometimes a simple restart helps, other times it may be the devices have the wrong hardware IDs and the virtual device just screws up when trying to create it (my assumption).

That error that you are seeing is the same error I would get for example when no pedals are plugged in, so I wonder if it might just not be 'seeing' the device properly from windows side when trying to run. Had a quick look back at some of the comments on the Steam guide, and does seem others have got it working with the pedals (well they never came back with more issues so I assume a positive outcome).

As I mentioned, I'll double check the code later as well. Let us know how you get on

Leo Sagan · Jul 24, 2017

Aussiedroid said:
In the mean time, not to be 'that IT guy', but if you can, turn off the PC, unplug all your Thrustmaster devices and any other game controllers you have connected. Restart PC without them plugged in. When windows is started, plug in the Joystick, then Throttle, then Pedals and give it time for it to install device between each plug in. Start the TARGET software etc and try it again.

It's always good to turn it off and on again

Unfortunately, I just tried that and it did not change anything this time : bizarre ...

Aussiedroid · Jul 24, 2017

Worth a try

I've taken a look at the code and everything seems to be setup correct (from what I know).

Just to go over it quickly, this is the main code sections from the files related:

AD_EDSettings:
=========
define UseRudders 1

ADEliteDangerous:
===========
if(UseRudders == 1) Configure(&TFRPRudder, MODE_EXCLUDED);
...
if(UseRudders == 2){
initTFRPRudder(); }

AD_EDFunctions:
==========
int initTFRPRudder() {
MapAxis(&TFRPRudder, TRUDDER, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
MapAxis(&TFRPRudder, TRPLEFT, DX_X_AXIS, AXIS_REVERSED, MAP_ABSOLUTE);
MapAxis(&TFRPRudder, TRPRIGHT, DX_Y_AXIS, AXIS_REVERSED, MAP_ABSOLUTE); }

Option 2, will go and use initTFRPRudder(), but I am not sure if that is working. That doesn't matter though as we need Option 1 to work, which should exclude the device so you can configure it in ED.

I did some googling around the error. Didn't find a lot, but there were some references back to the device order that I mentioned previously. If you powered down and unplugged everything before, that should have resolved it unless another device is still plugged in before you attempted. One post mentioned you can see this from the 'Game Controller' panel in windows. The order here is important I believe. Things like other gamepads/controllers may also interfere.

Example, on my PC it looks like this: (Note the Joystick & Throttle at top of list - Pedals last)

Should be able to get to this window via Search 'game controller' and pick first option in list.

Can you check if you are getting the same order for your devices, or if there is anything else in the list above your Warthog?

Also to check if you are running latest TARGET software, and also if a reinstall may fix the issue (yes .. I am running out of ideas if the above doesn't work lol)

Cheers,
AD

Dar|{cyde · Jul 24, 2017

Code:

AD_EDFunctions:
==========
    [COLOR=#1e90ff][B]int[/B][/COLOR] initTFRPRudder() {
        MapAxis(&TFRPRudder, TRUDDER,  DX_Z_AXIS, AXIS_NORMAL,   MAP_ABSOLUTE);
        MapAxis(&TFRPRudder, TRPLEFT,  DX_X_AXIS, AXIS_REVERSED, MAP_ABSOLUTE);
        MapAxis(&TFRPRudder, TRPRIGHT, DX_Y_AXIS, AXIS_REVERSED, MAP_ABSOLUTE); }

Just pointing out... If you map the rudders to Thrustmaster Combined X, Y, and Z you're gonna have a bad time. There's only one axis left on thrustmaster combined. Its best to Exclude(&TFRPRudder) unless you want to do differential toe brakes. Then you have to do my code from Eventhandle, or something similar.

Leo Sagan · Jul 24, 2017

Hi Aussiedroid,

Thanks for the quick reply

I had 4 devices listed in the Game Controllers window, in that order :

---------------------------------------------
Controller (XBOX 360 For Windows) OK
T-Rudder OK
Throttle Hotas Warthog OK
Joystic HOTAS Warthog OK
---------------------------------------------

After unplugging => reboot => pluging in the correct order, I got :

---------------------------------------------
T-Rudder OK
Throttle Hotas Warthog OK
Joystic HOTAS Warthog OK
Controller (XBOX 360 For Windows) OK
---------------------------------------------

Every time I tried to plug the XBOX cobtroller, it would appear on line 1 or 2. I switched between different usb ports, I also tried to plug them directly on my computer, not on a hub, with more or less the same results, but couldn't obtain another result.

In the end I decided to leave the XBOX out for the time being and retried with TARGET to compile/run (I checked the version, it is the newest one).

Unfortunately with the same results again :-/

Aussiedroid · Jul 25, 2017

Dar|{cyde said:
Code:

AD_EDFunctions: ========== [COLOR=#1e90ff][B]int[/B][/COLOR] initTFRPRudder() { MapAxis(&TFRPRudder, TRUDDER, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&TFRPRudder, TRPLEFT, DX_X_AXIS, AXIS_REVERSED, MAP_ABSOLUTE); MapAxis(&TFRPRudder, TRPRIGHT, DX_Y_AXIS, AXIS_REVERSED, MAP_ABSOLUTE); }

Just pointing out... If you map the rudders to Thrustmaster Combined X, Y, and Z you're gonna have a bad time. There's only one axis left on thrustmaster combined. Its best to Exclude(&TFRPRudder) unless you want to do differential toe brakes. Then you have to do my code from Eventhandle, or something similar.

Thanks mate! Yes I assumed it might be an issue, given Clicker's earlier comment too on the limitations he found when combining in pedals too. It is more of an option there for those that want to customise the script themselves as I don't really support it, but might take a look at your toe brake code and see if its easy enough to add in for UseRudder=2 option.

PS - I took a go at your PIP code last night. Have now got it integrated into my script. Seems to work well!! Thanks again.

Leo Sagan said:
Hi Aussiedroid,

Thanks for the quick reply

I had 4 devices listed in the Game Controllers window, in that order :

---------------------------------------------
Controller (XBOX 360 For Windows) OK
T-Rudder OK
Throttle Hotas Warthog OK
Joystic HOTAS Warthog OK
---------------------------------------------

After unplugging => reboot => pluging in the correct order, I got :

---------------------------------------------
T-Rudder OK
Throttle Hotas Warthog OK
Joystic HOTAS Warthog OK
Controller (XBOX 360 For Windows) OK
---------------------------------------------

Every time I tried to plug the XBOX cobtroller, it would appear on line 1 or 2. I switched between different usb ports, I also tried to plug them directly on my computer, not on a hub, with more or less the same results, but couldn't obtain another result.

In the end I decided to leave the XBOX out for the time being and retried with TARGET to compile/run (I checked the version, it is the newest one).

Unfortunately with the same results again :-/

Hey Leo,

OK, well I think we may have found where the issue lies. Now the challenge of getting these in the right order

. As far as I know you cannot manually change the order, and as you have seen unplugging and plugging back in gives the same order. What I think would need to be done is to disconnect, shut down PC, restart without any controllers and plug in from a fresh start. I think in events like a wireless controller for example, if a controller has been registered, then it will regain the same controller number when it is found again. From the sounds of it though, you have tried this already?

Need to find a way to get that T-Rudder entry below the Throttle/Joystick. I'll see what I can find out online, if there are any other ways to resolve this.

Cheers,
AD

Aussiedroid · Jul 26, 2017

Hey Leo,

Looked a bit further into the issue. Firstly, there is an option to select the preferred device by pressing the Advanced button in the Game Controller window. See if you can select Joystick or Throttle or try changing them in a sequence to get the order you need.

Secondly, I found a windows article on it. One user said that cycling his usb devices in different orders, different combos, different ports eventually changed it to the right order he needed. Also another suggestion was to unplug the PC all together. Ensure the power is completely out of the PC, then try again. This apparently resets the USB assignment. I haven't tried any of this myself, but a few suggestions that might resolve your issue.

Let us know how you get on

Cheers,
AD

Leo Sagan · Jul 26, 2017

Hello Aussiedroid,

Sorry for the delay : I tried a few other solutions and wanted to double-check, etc. I also googled a bit.

Aussiedroid said:
Firstly, there is an option to select the preferred device by pressing the Advanced button in the Game Controller window. See if you can select Joystick or Throttle or try changing them in a sequence to get the order you need.

Indeed, and I tried it : sadly, no luck. I also found on the MS support website the (allegedly) correct procedure to do it :

1) assign your preference to the device
2) remove the device then plug the real 'favourite' device in the same usb port the previous one was
3) again, set the new one as your favourite, which will flush the former settings

According to MS, this should reset the all thing and make sure the preference is kept later on as well. Guess what, it didn't work for me and reading further in the same thread, it seems it didn't work for a lot of other people too

Aussiedroid said:
Also another suggestion was to unplug the PC all together. Ensure the power is completely out of the PC, then try again. This apparently resets the USB assignment. I haven't tried any of this myself, but a few suggestions that might resolve your issue.

I didn't think of that. I usually just shut down the PC, wait a few seconds and turn it on again. This time I made sure the thing was off the hook for good (unplugged the whole damn socket strip from the wall

) and I waited 5 minutes at least (made some tea). It did not work either.

Then I found another MS support post suggesting to reinstall the USB controllers. I created a restoration point and did that, and unfortunately it did not work either. To be fair it seems that it is a common problem, and an old one at that : I found a looooong thread dating back to 2004, about the very same issue on Windows ... XP !

I'll leave it at that for now : it's yet another good reason to buy the Crosswind pedals (I have been dreaming of these for months now, I'm almost done saving the billion dollars I need for them.)

Thanks for all your help, and rest assured that when I get the MFG CW, I'll be back in the thread to bug you with tons of questions

o7 CMDR Aussiedroid

Aussiedroid · Jul 26, 2017

Damn u Microsoft! [mad]

Sorry to hear its still not working. Was hoping something may trigger the order change. Wish there was something I could code up in the script to help

The MFG Crosswinds are definitely worth the wait.. so good. Hope it will solve the order problem being a different device/different manufacturer, dunno, I certainly will have my fingers crossed for you!

EDIT - One final thing to try .. full uninstall of the Thrustmaster software, do the whole unplug thing again, and go through the reinstall. Worth a try?

AD

Alpenmilch · Jul 26, 2017

Mylord (bends over and kisses the Ring) ... I see you are busy

I had some some nerve wrekking Pc issues, so I was not able to response about Free Camera, sorry Sir.

Free Camera in the SRV only allows you to drive foreward, but nothing else as far as I see it, because almost any drive Key is mapped for the Camera as i understand it.

It would be great to drive with a choosen perspective. Just a wish.

Another little thing is while using the Free Camera in a ship you often run accidently in the Friendslist (left China up with Modi as I remember)

@ Leo:
As far as I understand your Problem:

I had a lot of trouble with the combined /not combined structure of the Warthog, too. The game will not response, but the Buttons are working in Windows.
I had to enable/disable the devicemanagementapp.exe to get things working again.

I have to disable it at last, because otherwise my PC will not shut down properly. You could find it in the Target Folder.

Was not my Idea...

http://forum.teamspeak.com/threads/128245-conflict-with-target-gui-from-thrusmaster

Maybe it could help to try this out until your crosswind (jealous

) arrive

Thanks for having me this fun with your Script!

Aussiedroid · Jul 27, 2017

Hi Alpenmilch,

Sorry to hear you've been having issues with your PC, but thanks for the feedback. I am actually working on a new update/build so will look into the SRV throttle when in free camera. I haven't seen this myself, but in my personal setup I use the rudder pedals for SRV throttle, so I think that would bypass the issue you have mentioned. Was going to suggest using the digital throttle mappings, but then realised these probably don't work as they are also used in the Free Camera mode for blur as well.

Can I ask what you are attempting to do when the Friendslist comes up? The Pinky Modifier I don't think is used on the throttle arm in free camera mode, so I am a little confused how this could occur, unless there is something bugged triggering it.

Cheers,
AD

Alpenmilch · Jul 27, 2017

Fast as ever

Sorry for being not clear about the Buttons I mean.

If you are in free Camera and use Modifier [1] (button 4 on combined as the device analyzer name it) and push on the Throttle the Thumb China hat foreward (Button 4 on the Throttle) I enter the Friends Menu.

This is a little bit confusing, because any other direction with this two Buttons combined in this mode will steer your free camera and I am stupid enough to make this mistake over and over again.

Please forget about it, I pulled the Modifier [1], but I don´t have to do so, to change the Free Camera position. You mapped it right. Tricky to learn not to push and pull always any button like a monkey. [blah]

The Free Camera thing on the SRV is: You could not steer the car in free camera mode, as far as I can see because the free camera is mapped on almost any steering inputs except drive foreward.

Thanks again, again, again Mylord

Aussiedroid · Jul 27, 2017

Yes, I found the issue you were seeing. I have remapped the SRV steering to fix it. Also, I did a bunch of random presses just to see what would pop up. Sure enough, Friends View Menu! It appears that this can be displayed anywhere, even in the Camera mode, so with the mapping it conflicted with Free Camera. I've found a solution for that too .. will have the new version uploaded imminently... just getting it all together.

Thanks for the feedback, I would not have found that myself!!

Aussiedroid · Jul 27, 2017

August Update!

Update 2.4.2: COME TO THE DARKCYDE WE HAVE COOKIES UPDATE

-> Special Note: The blank Warthog Reference Maps have been removed in this download. It is now available via the OP via link.

List of Changes:

NEW: Toggle Position Overrides for Landing Gear & Cargo Scoop (Hold Pinky Trigger + Toggle). This will ensure if you mode switch or log in when toggles out of alignment that you can override directly with the HOTAS.

NEW: Sub-System 'Magic 8 Ball': Fast Skip Prev/Next Sub-System returns! This will skip sub-system selection forward 6 presses, and skip back 5 presses. (Hold CMS Hat Switch Push + UP/DOWN on the Pinky Toggle Switch to use). This should allow quicker module locks, although due to each ship having different modules, it will not always align hence I've named it the Magic 8 Ball due to the random nature (Keep toggling for another module lock). *Beta: Needs more testing. Let me know if this is useful to you [up] [down].

NEW: Start Software with Script Run, such as Elite Dangerous Launcher (+any other 3rd Party apps) (Off by Default - Optional User Preference Added). Application paths may need to be edited in script prior to use. Few commonly run 3rd party apps already added to the list for selection (ED, TrackIR, VA, Discord, EDDiscovery, EDMC).

IMPROVEMENT: Upgraded PIP Management to a Function from Macro Sets. Far more elegant design (by DarKcyde), with cleaner implementation.
IMPROVEMENT: Added StartSoftware & CargoPrecisonMode user preferences to the Target Startup Print Readout.
IMPROVEMENT: Replaced basic code for UseRudder = 2 Option (MODE_FILTERED) with advanced code (by DarKcyde). Allows use of differential combined toe brakes with TFRP Rudders. Remains UNTESTED, and it's still recommended for TFRP Rudder uses to UseRudder = 1 (MODE_EXCLUDED) to avoid DX limitations.

FIXED: Problem with Hardpoint Override switch not working & also integrated CargoPrecisionMode to ensure Throttle is returned to proper range when you turn your Cargo Scoop toggle back in the off position.
FIXED: Conflict with SRV controls when using Free Camera mode. Note, some Free Camera controls have moved: Blur is on L/R of CMS Hat Switch, & digital SRV steering moved to L/R Coolie Hat Switch.
FIXED: Added missing Multicrew controls to reference maps & moved Multicrew 3rd Person Field of View control to U/D on Nipple instead of L/R.
FIXED: Friends View Screen popping up in Camera View. This has now been remapped to CMS Hat Switch Push (Modifier 2) + Mic Switch Push.

CODE CLEANUP: Removed multiple 'if' statements, combining with '&' syntax.

CODE CLEANUP: Returned Next & Previous Sub-System mappings to default VA key mappings.

Fly Safe CMDRs!

** Please visit the ModDB link to get the latest version **

Alpenmilch · Jul 27, 2017

Christmas again [heart]

First look: Amazing!

I love to drive my SRV in third Person, using Thrusters, even shooting following the woobling shadow under the car.

All because of your magic!

Aussiedroid · Jul 28, 2017

Alpenmilch said:
Christmas again [heart]

First look: Amazing!

I love to drive my SRV in third Person, using Thrusters, even shooting following the woobling shadow under the car.

All because of your magic!

Thanks mate! Happy its all sorted for you

Before testing it out yesterday, I had never tried the free camera while using the SRV in motion. I had a lot of fun with it too, and you can get some great angles. I'm still crap at using the camera controls though to get anything cinematic lol. More practice is needed I guess

CMDR Corleone · Jul 29, 2017

I'm now getting comfortable with VR using AD's settings and everything's working out fine except...

I have a set up using VESA 100 brackets on my chair (VESA is an industry standard for monitor brackets), these are the $30 jobbies I am using from Amazon:

These were fine for my lightweight HOTAS X with some heavy duty Velcro and good enough for the Warthog throttle Velcroed down with the back resting on the chair arm:

But with the stick being used a bit more violently at times I didn't want to trust to velcro plus to set the baseplate on the chair arm would leave the stick uncomfortably high, so I came up with an adaptor plate, put the tech drawing together and am having it machined as we speak.

Anyone else who is interested in this solution is welcome to the drawing to have a local shop make up a plate or possibly, if I can wangle it, I'll get the settings they enter into the CNC machine from the shop and make those available early next week, hopefully.

I'll post pictures of how it looks completed and the mounted stick next week.

Fly safe CMDRs, and never fly without rebuy!

Alpenmilch · Jul 29, 2017

Aussiedroid said:
Thanks mate! Happy its all sorted for you

Before testing it out yesterday, I had never tried the free camera while using the SRV in motion. I had a lot of fun with it too, and you can get some great angles. I'm still crap at using the camera controls though to get anything cinematic lol. More practice is needed I guess

Mate!

I am very happy to give you a very little of the fun you gave so many Players in return, by just saying, try your own famos tool in another way.

Position Overrides are brilliant, too.

I am not able to test anything now, because I am still fighting with some terrible Driver Issues, hoping the Target is not the Center of it.