Release Aussiedroid's Enhanced Thrustmaster Warthog Script

MALjCE

M
Aussiedroid, first off thanks for the great script!

I haven’t tried that yet. I wasn’t sure exactly what I needed to replace. Can you specify which sections of code I would replace with {NoDevice}? Everything that references {16D00A38}? The referenced link was shut down by steam.

As far as hardware, I’m just using a warthog HOTAS and joystick combo. Nothing else.
 

Sarge788

S
Hi Aussie,

Thanks for the the great script, but now I have a problem. I have loaded the latest bings file in the correct place but I start ED there is no sign of your script anywhere and when I check the bindingloadingerrors file I see this

There where errors when loading preset file: Aussiedroid Warthog Enhanced 2.4.0.binds
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38


There where errors when loading preset file: Aussiedroid Warthog Enhanced 2.4.3.binds
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38


There where errors when loading preset file: Aussiedroid Warthog Enhanced 3.0.2.binds
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38
Failed to find GUID for device: 16D00A38


Can you help please

Thanks in advance
 

CMDR Touille

CMDR Touille
MALjCE said:
Aussiedroid, first off thanks for the great script!

I haven’t tried that yet. I wasn’t sure exactly what I needed to replace. Can you specify which sections of code I would replace with {NoDevice}? Everything that references {16D00A38}? The referenced link was shut down by steam.

As far as hardware, I’m just using a warthog HOTAS and joystick combo. Nothing else.
Click to expand...

If you just using HOTAS (without rudders) try this :

in AD_EDSettings_v3.0.2.tmh :

find

Code: 
define UseRudders             1

replace with

Code: 
define UseRudders             [FONT=arial black]0[/FONT]



FD seem to be working on a FIX since 01/02/2018 : https://forums.frontier.co.uk/showthread.php?p=6373767&viewfull=1#post6373767
 
Last edited:

CMDR Touille

CMDR Touille
Sorry didn't checked the binding file.... [where is it]

Open Aussiedroid Warthog Enhanced 3.0.2.binds (in \Users\<User>\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings )

Find All the (8*):

Code: 
<Binding Device="16D00A38" Key="............." />

Replace
Code: 
16D00A38
with
Code: 
{NoDevice}


Like this (for each instance 8*):

Code: 
<Binding Device="16D00A38" Key="Joy_RZAxis" />

to

Code: 
<Binding Device="{NoDevice}" Key="Joy_RZAxis" />



You can also find the modified file here : https://www.dropbox.com/s/uy0ierx8auyioa2/Aussiedroid Warthog Enhanced 3.0.2.binds?dl=0
 
Last edited:

MALjCE

M
CMDR Touille,

That's exactly what I needed!!! Thank you, I'll try later after work.


It worked beautifully, thank you!!!
 
Last edited:

Aussiedroid

Aussiedroid
CMDR Touille to the rescue! Thanks mate!

Apologies to everyone else, I didn't get to test this out last night :(

I think given the age of the issue raised during beta and still no resolution that I may need to exclude the MFG Crosswind mappings in the bindings file for the time being (or in future updates) to ensure those without the device can load the bindings. In mean time, if anyone else experiences this then please download CMDR Touille's updated bindings file from the previous post.

Still I will hold out hope that Frontier can resolve this.

Cheers, AD
 

Aussiedroid

Aussiedroid
Mar 2018 'Live' Update!

Update 3.0.2.1: CHAPTER 1 BINDINGS HOTFIX

-> ** March Update: As discussed above, an issue has been found in 3.0 for CMDRs using the script WITHOUT MFG Crosswind Rudder Pedals. ED will NOT show any bindings file. Till Frontier fix this, I have another binds file version where the GUID for the MFG Crosswinds have been removed, for users of no or other pedals. Download now contains 2 .binds file versions. Please choose the appropriate one for your setup. **


List of Changes:

FIXED: Show CQC Scoreboard keybind updated to ALT+F5 to prevent conflict when use ~ for voice comms (Discord).



[alien] Fly Safe CMDRs! [alien]

** Please visit the ModDB link to get the latest version *** Steam Guide can be found here **
 
Last edited:

the100thmonkey

the100thmonkey
Quick question - I'm trying to map a button on my T16000m to hold until pressed again. How do I go about this?

FD broke the flight assist toggle with the latest update. The issue was reported in beta 1, but hasn't been addressed yet.

edit
Never mind - I got it sorted

edit 2
And it doesn't work anyway.
 
Last edited:

Aussiedroid

Aussiedroid
the100thmonkey said:
Quick question - I'm trying to map a button on my T16000m to hold until pressed again. How do I go about this?

FD broke the flight assist toggle with the latest update. The issue was reported in beta 1, but hasn't been addressed yet.

edit
Never mind - I got it sorted

edit 2
And it doesn't work anyway.
Click to expand...

ooO hearing stuff like this gets me nervous that I have other things broken in my script :p

How were you going about the mapping previously?

Thinking there might be a few ways to do it, but probably good to start to look at what is not working first.
 

the100thmonkey

the100thmonkey
After a supercruise exit, flight-assist now defaults back to on. Previously, it would stay off.

I was trying to set a function that would basicaly hold down the flight-assist key so that when set to "hold" in the control options it would keep pressing the key so that FA would turn itself off the moment you left supercruise. I did this with the press/release functions in a sequence in the GUI.

It works, except when you drop out of supercruise, it doesn't - you have to press the button again to release the key, and press it again to start it working.
 

Aussiedroid

Aussiedroid
the100thmonkey said:
After a supercruise exit, flight-assist now defaults back to on. Previously, it would stay off.

I was trying to set a function that would basicaly hold down the flight-assist key so that when set to "hold" in the control options it would keep pressing the key so that FA would turn itself off the moment you left supercruise. I did this with the press/release functions in a sequence in the GUI.

It works, except when you drop out of supercruise, it doesn't - you have to press the button again to release the key, and press it again to start it working.
Click to expand...

I'm not too familiar with using the GUI to program things, but from a script side of things, you could have a release 'UP' action added after each supercruise trigger press. It would then always release the key when supercruise is pressed even if it may not be held down. This would ensure it is always released before you return to normal space.

Hopefully Frontier fix it though, so it keeps your flight assist status between instances, but above might give a workaround for now.

AD
 

major7079

major7079
Hello Aussiedroid,

thanks a lot for your extraordiary efford and work with your programming and scripting. But I am lost.
Maybe I mixed too many things at the same time but first I do not know in which order I have to make the settings for my HW and SW to make it all running in the end.

My hardware and software I am dealing:
Hardware: Oculus Rift or alternatively TrackIR 5; Thrustmaster HOTAS Warthog; pedals from MS Sidewinder Force Feedback Wheel;
Software: Voice Attack with HCS voicepack A.S.T.R.A. / the new SINGULARITY update and T.A.R.G.E.T. v3 software and your Script Configs v3.0.2.; Windows 10 Pro 64;

After all the research in the web and as I finally could not make all running as expected I was so frustrated with all the configuring that I had stopped playing since 2.4. Because with every major Game update or new PC I had to rework all over again.
With the new ED Season 3 I wanted to give it a try again as I really love the ELITE from the beginning in 1985 and therefore I also backed this ED.

I compared different GUI Config files (one which was once running and your new v3.0.2). They look completely different for me. And the also behaved completely different.
Sorrily I am not a programmer and I do have my problems in understanding the provided config files, e.g. for the T.A.R.G.E.T. script editor.

I can image you are pretty busy as well, but if you could help me with the setup to get ED up and running with VR, I would show my appreciation, if it would give me back the joy of this awesome game again.
Right now I have no choice but to watch great youTube reports from other commanders while I'm still grounded.
Voice attack: Singularity Profile is not working with my old commands which I tried to import and the Voice attack tells me that the chosen profile in ED itself must be different than the Assiedroid v3.0.2 binds version. So what to do and in which order.

I can provide any kind of files I am working with or a list what I did so far. I tried to follow your guide as much as possible.

Are there any basic information missing?

kind regards,
CMDR Edward Perryman Cole aka Major

P.S.: I do have Skype or WhatsApp and I am located in Germany. Nevertheless I am willing to be available at any time which suits you for your support.

Besides that I am wondering if there is anyone with the same hardware and software in use for E:D?
If yes, please let me know ...
 
Last edited:

Aussiedroid

Aussiedroid
Hey Major,

Let's see if we can work out what the issues are :)

To start off, it should not matter which order you are running things in, as long as they are running prior to the game being launched. So making sure hardware is all connected, and 3rd party software is running, then start the game.

The first time you run a new version of the script, you will need to load the script into Target Script Editor & check the user preferences found in the AD_EDSettings file. This will ensure the VR (or TrackIR) is set correctly for the Throttle toggles. Other things can be changed here too without making further changes to the script code. Once set, save & run.

Start ED. Once in the game, you will need to select the bindings file & also map your pedals. From this point you should have the ED bindings running, linking into the Target Script for the additional functionality & headtracking set.

Regarding the Voice Attack, I actually do not use it myself (I find toggles/buttons more efficient), but maybe there is further configuration needed after the release of the Singularity update you mention. I read on the Voice Attack forums that the default keys are no longer needed as Voice Attack will read your bindings file and map accordingly (so shouldn't be a mapping conflict or change). I came across this too (http://forum.hcsvoicepacks.com/forum/technical-support/18232-elite-keybind-checker). Maybe this checker needs to be run to align the mappings?

Is it just Voice Attack you are having issues with once in the game?

Are you having issues before starting the game, such as with running the script successfully or hardware not being found or something else?

Appreciate any further detail you can provide.


Cheers, AD
 

Betatrialz

B
im using ur most updated verion and love it... but one thing bugs me... why cant i make new profile and attack the script in target gui, that way i can add a curge on the stick..... or is there a way to do this that im not seeing
 

Aussiedroid

Aussiedroid
Betatrialz said:
im using ur most updated verion and love it... but one thing bugs me... why cant i make new profile and attack the script in target gui, that way i can add a curge on the stick..... or is there a way to do this that im not seeing
Click to expand...

Hi Betatrialz,

Thanks a lot mate! :)

I'm not sure what you mean regarding making a new profile. The script can be run from both Script Editor and GUI & can be edited freely.

What are you trying to change (sorry not sure what a curge is)? Do you mean curve?

Cheers, AD
 

Betatrialz

B
YEAH THE ONLY WAY TO EDIT THE CURVE IS TO MAKE A NEW PROFILE IN T.A.R.G.E.T GUI, BUT YOU CANT GET THE SCRIPT IN BECAUSE ITS A THE WRONG FILE TYPE FOR ADDING TO PROFILES... TO RUN JUST THE SCRIPT IN TARGET GUI, IT WANTS A TMC FILE TYPE... TO ADD IT TO A NEW PROFILE SO YOU CAN MAKE CURVES AND WHAT NOT ON THE JOYSTICK, IT WANTS A TTM FILE TYPE

YEAH SORRY MEANT CURVE NOT CUGE
 
Last edited:

Aussiedroid

Aussiedroid
No need to yell bud :p

The profile already has 3 joystick curves baked into the code. If you edit the script you can change one of the presets to whatever you may prefer via the Script Editor, save, close, then run the script in the GUI. I normally run the script via the GUI myself, but don't do any editing in there. As far as I know, GUI profiles are configured differently, so getting a specific function imported separately would be difficult as GUI doesn't support most of the functions used in the script directly (well at least from what I can see).

Have you tried the built in curve profiles?

Cheers, AD
 
You must log in or register to reply here.
Back
Top Bottom