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.Originally Posted by imacken(Source)
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!Originally Posted by Aussiedroid
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
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.Originally Posted by imacken
No worries, but sorry to hear you are still having issues.Originally Posted by ploepfe
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.
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
Originally Posted by AussiedroidNo 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.
Fly Safe CMDRs!
** Please visit the ModDB link to get the latest version *** Steam Guide can be found here **
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
Hey CMDR Cole,
Hadn't heard back from you in a while so assumed you managed to get it all working
In regards to the missing devices showing when running in Script Editor, this is to be expected (I get the same results my end so it is nothing to worry about). I believe this output is showing the devices that have been excluded from the virtual device. This is the code around line 60 in the main script tmc file. It may not appear in the GUI as it may handle this internally, ie not something you need to call out to get the virtual device created properly. Not 100% sure, but as long as you are getting 'main returned 0' then your script is running correctly.
The issues Drag0nfire had unfortunately seem to be a little common. Once everything is working its a treat but sometimes just has issues & wont compile correctly or find hardware. They should be unrelated to the Voice Attack issues you were having previously though & seeing your script is running ok it might no longer be an issue. With the script running ok, then you should only need to select the bindings from within ED (assuming you have sorted out the VA issues you were having).
Cheers, AD
Hello AD,
Yes, Voice Attack (VA) is currently no issue as VA is detecting the binds from inside the game as you said. Thanks for that hint!
But I would like to know what the correct controller status should look like.
Should Thrustmaster (TM) warthog stick and TM warthog throttle be shown up in addition to the TM combined hid or not?
It is really a pita when it starts showing up or disappearing. Especially now when only the TM combined is there and at the same time your Aussiedroid bind mapping is not available in-game any more where I made all the keybind mappings. Is that behavior related or did it just happen by accident?
Currently I do not know how to get it back your bindings. They are still in the folder on the drive as before.
I hope you understand my dilemma.
I can explain in detail but I am typing on my mobile right now.
Lots of thanks in advance,
CMDR E.P. Cole
Ah ok, so you are saying that the bindings in game are disappearing even though the rest is running fine and they are in the bindings folder?
If yes, this may relate to the GUID issue mentioned a page or so back in the thread which was introduced in 3.0.x and has not been fixed yet.
In my latest download version, you will see there is two folders under the ED bindings section. One with and one without MFG Crosswind included. If you choose the MFG Crosswind version but do not have this device plugged into your computer then when you start Elite, it will not show any custom bindings file and only show the default (also defaulting you to keyboard and mouse). If you have older versions of the bindings file you still want to see and use, then you will need to go into the bindings file in a notepad text editor and remove the device references '16D00A38' for the Crosswind and replace with '{NoDevice}', save and restart game.
Cheers, AD
Hi AD,
I would like to know what the correct controller status should look like. Should Thrustmaster (TM) warthog stick and TM warthog throttle be shown up in addition to the TM combined hid or not?
[IMG]C:\Users\Markus\Pictures\Controller after TARGET launch.JPG[/IMG]
And depending if they are separately shown in the bindings look completely different and do not work any longer if set at a stage where they warthog components were not available at setting the keybinds.
Can you maybe send me you bindings file after you have made the in-game bindings. I know you are not playing with Voice Attack but it might help me to set up an appropriate config myself when the rest is working.
In the meantime I have installed Aussiedroid V3.1.0 and guess what, now I can at least choose the Aussidroids binds file in-game again.
Now I have to do the keymapping in-game without the TM warthog stick and throttle showing up separately in the controller menue.
I hope it will stay this way. ... Nevertheless my previous questions are still valid. How has the controller settings look like?
As I am playing the game with English keyboard settings despite my keyboard hardware Logitech G910 is an German style (QWERTZ) one, because Voice attack is waiting for English commands.
I would like to know if I have to stick with "define KBLayout KB_ENG" or do I have to change it to "define KBLayout KB_GER"? I changed it to KB_GER. Is it correct?
Running script: C:\Users\Markus\Downloads\ELITE Dangerous_current\Aussiedroid-ED-Warthog-Script-3.1.0\Warthog Script\AD_ED_v3.1.0.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[2]:
1: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&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&3) selected
USB HID device with hardware id "VID_044F&PID_b351" cannot be found
USB HID device with hardware id "VID_044F&PID_b352" cannot be found
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.1.0 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 = 1 AUTO Repeater Fire = 1
Ship Utility Mode = 0 MFD Active = 2
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]
-----------------------------------------------------------------------------------------------------------------------------------------------
Right MFD Configured
Left MFD Configured
Done... Enhanced ED Script Engineered by Aussiedroid is now running... Fly Safe CMDR! <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
main returned 0
I have chosen as before the binds from folder "WITHOUT MFG Crosswind" as I am using the pedals from MS Sidewinder Force Feedback Wheel.
kind regards,
CMDR E.P. Cole
Hey CMDR Cole,
The picture you linked didn't come through, so not sure what you are displaying. From memory, the separate joystick and throttle do not show in the device list in the bindings file selection. It only shows the TM Warthog combined (if script wasn't loaded it would likely show two devices separately). The bindings file I use is exactly the same as the one I share in the public profile, I just change a couple of user preferences to suit how I like to play.
I have a feeling the issue you were having is what I mentioned previously, so hopefully now that it is displaying properly you should be fine.
Yes, you will need to update your keyboard language/layout to KB_GER. Some keys will not map correctly otherwise.
Cheers, AD
