WELL TAHT SUCKS.... YEAH I DONT KNOW ENOUGH ABOUT CODING TO CHANGE ONE OF THE THREE TO ONE I WANT
Release Aussiedroid's Enhanced Thrustmaster Warthog Script
- Thread starter Aussiedroid
- Start date
THERE IS A BUILT IN TOGGLE! NO PROGRAMMING REQUIRED!
Apologies if the answer is in the 30 pages of thread info, I guess this is the price to pay for such a popular thread. I am waiting for some flight pedals and until then I need to set to left-right to be roll and not yaw. I have configured this in ED config but it gets reset every time I restart so I think the script has this defined. If I want the yaw controls to be roll where to I configure this?
Last edited:
Hi Dabria,
No worries, it should be as simple as changing it in the game bindings and applying to save. The script does manage the curves for the axes to feed into ED (allows the profile changes between the 3 presets for throttle and joystick), but the mappings are bound within the game.
If you look into the bindings folder, can you see the date modified being updated after you reassign the axis? I'm just wondering if it is saving correctly.
If you save the new controls and then exit the game instead of entering the game modes does that remember it for next time?
Regards, AD
No worries, it should be as simple as changing it in the game bindings and applying to save. The script does manage the curves for the axes to feed into ED (allows the profile changes between the 3 presets for throttle and joystick), but the mappings are bound within the game.
If you look into the bindings folder, can you see the date modified being updated after you reassign the axis? I'm just wondering if it is saving correctly.
If you save the new controls and then exit the game instead of entering the game modes does that remember it for next time?
Regards, AD
OK, so I have a stupid question here as I can't get the script working any more!
I had to reinstall Windows, and now, I can't remember how to get your script working in ED!
I have followed in readme instructions but am getting nowhere.
I have copied the ED profile to the correct place, i.e. C:\Users\Iain\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings.
I load up TARGET script editor, load and run ADED_v3.0.2.tmc, BUT, the profile doesn't show up in ED!
What am I doing wrong here.?
EDIT: It's OK, I was being stupid, I had copied the Crosswinds profile and obviously, the hardware wasn't being found! Duh!
One other thing, I thought there was a way of getting the script to launch ED. How can I do that?
I had to reinstall Windows, and now, I can't remember how to get your script working in ED!
I have followed in readme instructions but am getting nowhere.
I have copied the ED profile to the correct place, i.e. C:\Users\Iain\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings.
I load up TARGET script editor, load and run ADED_v3.0.2.tmc, BUT, the profile doesn't show up in ED!
What am I doing wrong here.?
EDIT: It's OK, I was being stupid, I had copied the Crosswinds profile and obviously, the hardware wasn't being found! Duh!
One other thing, I thought there was a way of getting the script to launch ED. How can I do that?
Last edited:
Dear all,
the script somehow stopped working:
what was changed on my system is most likely Windows 10 Fall Creators update. aynone saw this behavour as well?
(sorry, i couldn't find any related post)
many thanks for any help!
the script somehow stopped working:
Code:
Running script: C:\Users\gamer1\Documents\Target\Aussiedroid-ED-Warthog-Script-3.0.2.1\Warthog Script\AD_ED_v3.0.2.tmc
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
3: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\5&30AA3CB&0&1) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\5&30AA3CB&0&2) selected
USB HID device with hardware id "VID_044F&PID_B10B" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Script stopped!
Done
Device name set to Thrustmaster Combined
Runtime Error: STOP request received while running main on line 66 in "C:\Users\gamer1\Documents\Target\Aussiedroid-ED-Warthog-Script-3.0.2.1\Warthog Script\AD_ED_v3.0.2.tmc"
Error: Script run timed out!what was changed on my system is most likely Windows 10 Fall Creators update. aynone saw this behavour as well?
(sorry, i couldn't find any related post)
many thanks for any help!
Glad you got it working. Looks like the bindings GUID issue is still not fixed
If you are running Windows 7 or earlier, you should be able to enable 'startsoftware' setting in the settings file. In the main script, you can edit what you want to run. Check the paths are correct for your install and uncomment what you want to start. If you are running Windows 10 unfortunately the feature does not seem to work.
Hey ploepfe,
Failing at line 66 seems to suggest that it is having issues with the hardware to include in the script (first part of the script excludes/includes devices). From what I can read in the startup though, it seems to have found the Throttle & Joystick fine and selected them but might not be including the T-Rudder? Can you double check you have the user preference set to 1 for UseRudder? Does the script load fine if you unplug the Rudders? Do you get the same results after a restart of the computer/Windows?
Cheers, AD
Windows 10, I'm afraid, but thanks anyway.Glad you got it working. Looks like the bindings GUID issue is still not fixed
If you are running Windows 7 or earlier, you should be able to enable 'startsoftware' setting in the settings file. In the main script, you can edit what you want to run. Check the paths are correct for your install and uncomment what you want to start. If you are running Windows 10 unfortunately the feature does not seem to work.
Cheers, AD
No worries imacken
If you run a few other things when starting the game, you could create a batch file (.bat) to start everything up.Thanks AD. I'm embarrassed to say that I have completely forgotten how to use your bindings! I've been away from ED for quite a while and cannot work out what your modifiers are! Is there a simple explanation somewhere? For example, how do I go to the Nav Panel?No worries imacken
Hope it comes back quickly! It's all covered in the guide, but the short version, the Pinky Trigger [1] and CMS Hat Switch [2] both on the joystick are the main modifiers to use. In the reference map any command you see with a [1] or [2] before it means you need to use the modifier. For the panels, you use the [2] CMS Hat Switch modifier plus the hat switch on the thumb of the throttle.
Great, that helped. Thanks for explaining what modifiers 1 and 2 are. What are 3 and 4? Can you tell me where in the guide the modifiers are defined? Can't see it!
Dear Aussiedroid,
many thanks for your reply!
i've tried UseRudder Settings 0 and 1: same effect
unplugged Rudders (UseRudder=1): same effect
unplugged Rudders (UseRudder=0): same effect
Rebooting Computer/Windows: same effect
re-installing Target: same effect
any other things i could try?
your help is much appreciated since i LOVE your plugin and before (like, a few months ago - YES i had other things to do than playing ED it did work just brilliant...
best,
ploepfe
many thanks for your reply!
i've tried UseRudder Settings 0 and 1: same effect
unplugged Rudders (UseRudder=1): same effect
unplugged Rudders (UseRudder=0): same effect
Rebooting Computer/Windows: same effect
re-installing Target: same effect
any other things i could try?
your help is much appreciated since i LOVE your plugin and before (like, a few months ago - YES i had other things to do than playing ED
it did work just brilliant...best,
ploepfe
Cool! The modifiers are highlighted in yellow on the reference maps. Modifier 3 & 4 are the 'situational' modifiers, which are used for changing chat & microphone presets allowing different chat responses on the hat switch or change microphone channel from internal to external. They are not used for anything else.
Dear Aussiedroid,
many thanks for your reply!
i've tried UseRudder Settings 0 and 1: same effect
unplugged Rudders (UseRudder=1): same effect
unplugged Rudders (UseRudder=0): same effect
Rebooting Computer/Windows: same effect
re-installing Target: same effect
any other things i could try?
your help is much appreciated since i LOVE your plugin and before (like, a few months ago - YES i had other things to do than playing ED
best,
ploepfe
No worries, but sorry to hear you are still having issues.
I think given the above results, that the rudders are not the cause here. With or without still failing to run, but where it is failing is suggesting its having issues creating the virtual device. This might mean that the devices are being found in the wrong order or behind other devices in the device list and may be throwing Target out. From memory, Target needs the Throttle & Joystick to be first in the list of devices. If you type 'game controller' into search bar you should be able to open 'Setup a USB game controller' and see the current order. A couple more things to try:
Unplug all devices, and everything you can (ie all but mouse/kb) from your USB ports. Shut down & unplug PC from power for a few mins and then restart. Just plug back in the Joystick & Throttle one at a time. Let them identify and retest running script. Could also try plugging them into another hub such as a USB 2.0 port instead of USB 3.0 port on back of PC. Suggest trying to get it going just with Joystick & Throttle and add the Rudders again once working.
Looking around online at the error, others have also suggested enabling Legacy USB support in your BIOS, and to disable USB power management in Windows settings (or set to max power or whatever it is called). Also removing/uninstalling the TM driver and letting Windows grab the default from its servers.
Let us know how you get on
Cheers, AD
Hi AD,
I followed your guideline and thanks for the tip that ED itself is meanwhile recognizing some entries. There are still some questions but before I go on with this issues I am facing now a different problem after I have done most of the keymappings in your Aussiedroids binds profile in ED itself.
For the cleaning I moved some duplicated profile entries from the designated storage folder and when I started the game again as before there Assiedorid profile was gone.
I instantly moved the files back and nothing changed your Aussiedroid Warthog Enhanced 3.0.2.binds profile is still gone.
I tried everything to get it back according your manual but no chance.
Fyi, in the Game Controller menue I see only 3 controller after starting TARGET software as my "HOTAS Warthog Stick" and "HOTAS Warthog Throttle" are now "Trustmaster Combined". Somethimes before I think there were all controller and the combined controller listed.
Might that be the problem that your profile is not available any more? And if yes how can I bring back your Aussiedroid Warthog Enhanced 3.0.2.binds with all my configured settings?
The different binds profiles are all still in the designated folder available.
I am really frustrated, hopefully you can help me.
Thanks in advance,
CMDR E.P. Cole
update:
Now I removed all binds files besides 3 (Aussiedroid Warthog Enhanced 3.0.2, HCS ThrustMasterHOTASWarthog.3.0, HCSPacks Warthog 2.2.3.0) which I might be able to use. Then I started TARGET and ED again and suddenly your Aussiedroid Warthog Enhanced 3.0.2.binds is available again.
Nevertheless I would like to understand this behaviour and know what I can do if it happens again to avoid starting to configure the bindings from scratch over and over again.
I followed your guideline and thanks for the tip that ED itself is meanwhile recognizing some entries. There are still some questions but before I go on with this issues I am facing now a different problem after I have done most of the keymappings in your Aussiedroids binds profile in ED itself.
For the cleaning I moved some duplicated profile entries from the designated storage folder and when I started the game again as before there Assiedorid profile was gone.
I instantly moved the files back and nothing changed your Aussiedroid Warthog Enhanced 3.0.2.binds profile is still gone.
I tried everything to get it back according your manual but no chance.
Fyi, in the Game Controller menue I see only 3 controller after starting TARGET software as my "HOTAS Warthog Stick" and "HOTAS Warthog Throttle" are now "Trustmaster Combined". Somethimes before I think there were all controller and the combined controller listed.
Might that be the problem that your profile is not available any more? And if yes how can I bring back your Aussiedroid Warthog Enhanced 3.0.2.binds with all my configured settings?
The different binds profiles are all still in the designated folder available.
I am really frustrated, hopefully you can help me.
Thanks in advance,
CMDR E.P. Cole
update:
Now I removed all binds files besides 3 (Aussiedroid Warthog Enhanced 3.0.2, HCS ThrustMasterHOTASWarthog.3.0, HCSPacks Warthog 2.2.3.0) which I might be able to use. Then I started TARGET and ED again and suddenly your Aussiedroid Warthog Enhanced 3.0.2.binds is available again.
Nevertheless I would like to understand this behaviour and know what I can do if it happens again to avoid starting to configure the bindings from scratch over and over again.
Last edited:
Greetings again CMDR Cole,
The behavior you described sounds like the GUID bug described around here. I assume you are not using MFG Crosswind pedals? If not, when you load the bindings file it cannot find the device and instead of ignoring it like it did previously it causes the bindings to disappear. The earlier posts describe how to fix it via a text file editor, but also I did a quick hotfix so if you download the latest version from Moddb then there is a version without the MFG Crosswinds mapped.
Cheers, AD
The behavior you described sounds like the GUID bug described around here. I assume you are not using MFG Crosswind pedals? If not, when you load the bindings file it cannot find the device and instead of ignoring it like it did previously it causes the bindings to disappear. The earlier posts describe how to fix it via a text file editor, but also I did a quick hotfix so if you download the latest version from Moddb then there is a version without the MFG Crosswinds mapped.
Cheers, AD
Last edited:
No worries, but sorry to hear you are still having issues.
I think given the above results, that the rudders are not the cause here. With or without still failing to run, but where it is failing is suggesting its having issues creating the virtual device. This might mean that the devices are being found in the wrong order or behind other devices in the device list and may be throwing Target out. From memory, Target needs the Throttle & Joystick to be first in the list of devices. If you type 'game controller' into search bar you should be able to open 'Setup a USB game controller' and see the current order. A couple more things to try:
Unplug all devices, and everything you can (ie all but mouse/kb) from your USB ports. Shut down & unplug PC from power for a few mins and then restart. Just plug back in the Joystick & Throttle one at a time. Let them identify and retest running script. Could also try plugging them into another hub such as a USB 2.0 port instead of USB 3.0 port on back of PC. Suggest trying to get it going just with Joystick & Throttle and add the Rudders again once working.
Looking around online at the error, others have also suggested enabling Legacy USB support in your BIOS, and to disable USB power management in Windows settings (or set to max power or whatever it is called). Also removing/uninstalling the TM driver and letting Windows grab the default from its servers.
Let us know how you get on
Cheers, AD
Hey, i did unplug all deviced, power cycle unplug etc; only Joystick&trottle directly connected to PC (and keyboard, mouse) - no success
windows powersettings: USB powermanagement has been disabled
check bios settings: Legacy USB Support has been enabled
different USB ports (USB2 and 3): no success
doublechecked: the two Gamecontrollers are first in the "HID" list
de-installed steamvr-usb drivers: no success (ok, i missed pointing this one out; just recently added a vive-pro - which is amazing but without the hotas not really fun)
deinstalling drivers: no success
BUT: finally, i had the idea to re-install TARGET. now, script runs as expected (could have done that before :/
unfortunately, too tired now to re-plugin all devices etc... but, i am sure all fine now (simple button-tests work as per output of the script).
many thanks!
ploepfe
Awesome to hear its working now for you ploepfe! Fly Safe CMDR!
April 2018 Update!
Update 3.1.0: CHAPTER 1 THE EPILOGUE
-> Small improvement & fix to round out the Chapter 1 update. Pending any issues found this should be the last update for a little while. Two versions of the bindings files are provided again in this release, as it seems the GUID issue identified previously from 3.0 launch remains.
List of Changes:
IMPROVEMENT: Updated Combined Primary+Secondary Fire on Trigger to allow Primary Fire to continue firing when Secondary Fire (on dual stage trigger) is released. (Previously you would need to fully release the Trigger and squeeze again to engage Primary Fire after released Secondary).
IMPROVEMENT: Dual PIP Preset, change for 4xWEP now (2xSYS->2xENG).
FIXED: Conflict between Galnet Audio & Escape Vector Sequence. Galnet Audio keys remapped to Mic Hat Switch on Throttle + Pinky Modifier.
CODE: Moved combinePriSecFire variable to User Preference Settings section.
[alien] Fly Safe CMDRs! [alien]
** Please visit the ModDB link to get the latest version *** Steam Guide can be found here **
Update 3.1.0: CHAPTER 1 THE EPILOGUE
-> Small improvement & fix to round out the Chapter 1 update. Pending any issues found this should be the last update for a little while. Two versions of the bindings files are provided again in this release, as it seems the GUID issue identified previously from 3.0 launch remains.
List of Changes:
IMPROVEMENT: Updated Combined Primary+Secondary Fire on Trigger to allow Primary Fire to continue firing when Secondary Fire (on dual stage trigger) is released. (Previously you would need to fully release the Trigger and squeeze again to engage Primary Fire after released Secondary).
IMPROVEMENT: Dual PIP Preset, change for 4xWEP now (2xSYS->2xENG).
FIXED: Conflict between Galnet Audio & Escape Vector Sequence. Galnet Audio keys remapped to Mic Hat Switch on Throttle + Pinky Modifier.
CODE: Moved combinePriSecFire variable to User Preference Settings section.
[alien] Fly Safe CMDRs! [alien]
** Please visit the ModDB link to get the latest version *** Steam Guide can be found here **
Last edited:
Hi AD and ploepfe,
First thank you for your replys to my problem. I really appreciate this!
After some adaptions - I dont know what made this - suddenly I had the Aussiedroid v3.0.2. bind showing up again and I started mapping keys ingame again. I was really happy and thought i made it.
After a restart on the next day when I wanted to continue the script was gone again and after some research I recognized that I was facing the identical issue as in post #268 from drag0nfire of 21/08/2017, 1:43 AM of this thread.
My T.A.R.G.E.T. log from the .tmc file:
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\7&357DB437&0&2) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\7&357DB437&0&4) selected
USB HID device with hardware id "VID_044F&PID_B10B" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device with hardware id "VID_044F&PID_B679" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done
-----------------------------------------------------------------------------------------------------------------------------------------------
ENHANCEMENTS LOADING: v3.0.2 TARGET Mappings, Macros & Functions Decrypted <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
USER PREFERENCES: Run Software on Start = 0 PIP Preset = 2
Supercruise on Throttle = 1 Cargo Precision Mode = 0 Chaff on Escape = 0
Combine External Mics = 0 Text Chat Preset Mode = 1 Boost on Escape = 0
Custom Slider Curve = 1 Headtrack Center Mode = 0 AUTO Repeater Fire = 1
Ship Utility Mode = 0 MFD Active = 0
DEFAULT TOGGLE STATE: LED Backlight Level = 172
Combine Pri+Sec Fire = 1 Rotational Correction = 1 Cargo Scoop = 0
Landing Gear = 0 Classified Camera Mode = 0 Ship Lights = 0
-----------------------------------------------------------------------------------------------------------------------------------------------
Starting Macros... Trigger 2: Set to COMBINED Primary + Secondary Fire
Rotation Correction: ENABLED ^^
-----------------------------------------------------------------------------------------------------------------------------------------------
Initialising Joystick Axis ... Initialising Throttle Axis ...
Setting Throttle Profile: FULL SCALE [-100 -> 100]
-----------------------------------------------------------------------------------------------------------------------------------------------
Done... Enhanced ED Script Engineered by Aussiedroid is now running... Fly Safe CMDR! <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
main returned 0
and the T.A.R.G.E.T. GUI log from the .fcf file, (which I would prefer to use, because I used to do so):
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\7&357DB437&0&2) selected
Installing filter driver to VID_044F&PID_0402. Please Wait...Done!
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\7&357DB437&0&3) selected
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done
main returned 0
Honestly I do not now what is the difference between .tmc and the .fcf as the result / problems in the game turn out the same but the missing 3 lines "USB HID device with hardware id "VID_044F&PID_B10B" cannot be found. etc." as in the .tmc log are not shown here. Can you explain me the difference.
As drag0nfire is not sure what brought him the solutions I will have to try all suggestions made to him myself and hope the best. I am almost through with these.
I checked latest drivers, firmware and software, made testwise script adaptions in the AD v3.0.2 script, excluded / removed USB extensions and all unnecessary USB hardware even my Rift glasses to connect as many necessary Thrustmaster controller directly onto the mainboard and switched USB ports.
So far with frustrating poor results. Now I have to call it a day but I just saw that there is a new version v3.1.0 from AD which I downloaded right away.
Thank you in advance.
If you need any other information or logs from my side please let me know. I will provide all to get to a solutions.
Now I have to call it a day but I just saw that there is a new version v3.1.0 from AD which I downloaded right away. Thank you in advance.
I will go on tomorrow and see if this works. I will keep you informed if I can make it run.
Hopefully we see us soon back in the game,
CMDR E.P. Cole
First thank you for your replys to my problem. I really appreciate this!
After some adaptions - I dont know what made this - suddenly I had the Aussiedroid v3.0.2. bind showing up again and I started mapping keys ingame again. I was really happy and thought i made it.
After a restart on the next day when I wanted to continue the script was gone again and after some research I recognized that I was facing the identical issue as in post #268 from drag0nfire of 21/08/2017, 1:43 AM of this thread.
My T.A.R.G.E.T. log from the .tmc file:
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\7&357DB437&0&2) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\7&357DB437&0&4) selected
USB HID device with hardware id "VID_044F&PID_B10B" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device with hardware id "VID_044F&PID_B679" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done
-----------------------------------------------------------------------------------------------------------------------------------------------
ENHANCEMENTS LOADING: v3.0.2 TARGET Mappings, Macros & Functions Decrypted <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
USER PREFERENCES: Run Software on Start = 0 PIP Preset = 2
Supercruise on Throttle = 1 Cargo Precision Mode = 0 Chaff on Escape = 0
Combine External Mics = 0 Text Chat Preset Mode = 1 Boost on Escape = 0
Custom Slider Curve = 1 Headtrack Center Mode = 0 AUTO Repeater Fire = 1
Ship Utility Mode = 0 MFD Active = 0
DEFAULT TOGGLE STATE: LED Backlight Level = 172
Combine Pri+Sec Fire = 1 Rotational Correction = 1 Cargo Scoop = 0
Landing Gear = 0 Classified Camera Mode = 0 Ship Lights = 0
-----------------------------------------------------------------------------------------------------------------------------------------------
Starting Macros... Trigger 2: Set to COMBINED Primary + Secondary Fire
Rotation Correction: ENABLED ^^
-----------------------------------------------------------------------------------------------------------------------------------------------
Initialising Joystick Axis ... Initialising Throttle Axis ...
Setting Throttle Profile: FULL SCALE [-100 -> 100]
-----------------------------------------------------------------------------------------------------------------------------------------------
Done... Enhanced ED Script Engineered by Aussiedroid is now running... Fly Safe CMDR! <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
main returned 0
and the T.A.R.G.E.T. GUI log from the .fcf file, (which I would prefer to use, because I used to do so):
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\7&357DB437&0&2) selected
Installing filter driver to VID_044F&PID_0402. Please Wait...Done!
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\7&357DB437&0&3) selected
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done
main returned 0
Honestly I do not now what is the difference between .tmc and the .fcf as the result / problems in the game turn out the same but the missing 3 lines "USB HID device with hardware id "VID_044F&PID_B10B" cannot be found. etc." as in the .tmc log are not shown here. Can you explain me the difference.
As drag0nfire is not sure what brought him the solutions I will have to try all suggestions made to him myself and hope the best. I am almost through with these.
I checked latest drivers, firmware and software, made testwise script adaptions in the AD v3.0.2 script, excluded / removed USB extensions and all unnecessary USB hardware even my Rift glasses to connect as many necessary Thrustmaster controller directly onto the mainboard and switched USB ports.
So far with frustrating poor results. Now I have to call it a day but I just saw that there is a new version v3.1.0 from AD which I downloaded right away.
Thank you in advance.
If you need any other information or logs from my side please let me know. I will provide all to get to a solutions.
Now I have to call it a day but I just saw that there is a new version v3.1.0 from AD which I downloaded right away. Thank you in advance.
I will go on tomorrow and see if this works. I will keep you informed if I can make it run.
Hopefully we see us soon back in the game,
CMDR E.P. Cole
Last edited: