Target woes on new Rig.
-
Hi,
Using Target for many years with out any problems, save the .fcf and keyfile between installs no problem until I built this new Ryzen rig with Win7 as apposed to Win10 (Win 7 does not support new Intel or AMD formats)First thing I noticed was this ……Although this file is from today’s rearranging of USB ports. But seem OK for consecutive Runs.
So in Falcon with Target running I cant get the stick to use DX sequence 0-31. It get assigned to use 33-64 or some times 65-96. But occasionally I do see Button 1 flash up for some milliseconds before displaying Button 65 as the input to Falcon.
The Throttle is even weirder still while being asgined 65-96 and at times jumping back to the 32-63 range.
My system is as follows:
Ryzen5 1600
Gigabyte AX370-Gaming K7
16GB of G.skill 3200 @ Cl 14-14-14
RX480 8GB Gaming X
Two Samsung SSDs and a few WD Terabyte drivesAs expected without Target Falcon finds the Stick & Throttle where they should be DX 0-63 and 64-95.
And Target Device Analyzer & Event Tester all look OK.
Even though I use Target, All the Stick and some of the Throttle is setup in Falcon directly. Up to Button 32.
The base of the throttle as well as the China Hat and Boat Sw use Target.Found a post from a few years back with similar problems but no solution. https://forums.frontier.co.uk/showthread.php/33932-Guide-Getting-the-most-of-your-Thrustmaster-Joystick-HOTAS-with-TARGET-Software Half way down the page.
"
I am having a major problem with using the Thrustmaster TARGET GUI and loading configuration files for games to my HOTAS Warthog setup.
The software detects my TM Warthog HOTAS and 2 x MFD’s when in the main TARGET GUI editing environment but upon trying to load ANY config file for use in a game i get the following result after the software attempts to load the 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[4]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
3: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
4: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
Error: (internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_0404”
Error: (internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_0402”
Virtual HID devices managed by script!
Connecting virtual joystick…DoneDevice name FAILED (0x00000002) - using default.
Connecting virtual keyboard…Done
Connecting virtual mouse…Done
main returned 0
This happens with every config file i have and that includes the stock ones included with the TM hardware such as DCS Black Shark etc.
"
-
Hi Shad, are you running TARGET executable and service as administrator?
Had a similar problem associating the filter to USB devices and solved it with that. -
Wow that is a quirky one. I checked my own TARGET executable shortcut after what BlueRaven mentioned but mine is not set to admin or to any compatibility mode and runs just fine on my Win 7 x64 Home.
One thing I did notice that wasn’t mentioned by you or by the post you referenced was anti virus. I’d disable that and test again to verify it isn’t throwing a monkey wrench in.
-
Thanks for the suggestions Blue & Stubbies but no effect.
I am seeing some buttons flashing the correct DX number then on subsequent presses registering +64 away, I have learn’t how to provoke this happenstance.
It’s Sunday morning here so I have all day to yell at my Hog.
-
I am seeing some buttons flashing the correct DX number then on subsequent presses registering +64 away, I have learn’t how to provoke this happenstance.
Happened to me, too, when I was trying to use virtual keyboard emulation.
Thanks to Frederf I discovered it was not going to work and switched to DX buttons mapping, no hassle since then (except for TARGET not hiding my phisical devices, but that’s another story and I found how to workaround it).
See my thread for T.16000M FCS HOTAS profile and look at my v1.1 setup, I think you’ll find some useful hint. -
Do you have it on a USB hub ? On my end it can causes problems, at least for the throttle.
-
Thanks but No.
I use a pair of Expansion Brackets that make use of the additional USB headers on the base of the Mobo.
I have tried using the “Back Panel” ports also.
Device Sorting.txt manipulation is no solution either.
-
I have had a similar problem, sometimes my script launches fine from the GUI other times it takes forever to load and then doesn’t hide the physical devices. I’ve found using the script editor to launch my scripts to be more reliable. I will load the script in the editor then compile and run. This method results in the physical devices being hidden from the os. Not sure whats up with the TARGET GUI, but sometimes it works, other times it doesn’t. Sometimes the GUI works if I restart and launch target before any other program, other times not. Though launch from the script editor always seems to work even after the GUI fails to hide the physical devices from the system.
-
Shadow,
Had the same issue, can’t remember exactly what fixed it, but remember what I basically did.
Started from as scratch as possible.
Removed Target software via Control Panel
Disconnect the throttle and stick.
Removed the Warthog hardware using the Device Manager as follows:
Open Device Manager, under the View menu select Show hidden Devices
Removed all the light grey devices under Human Interface Devices. (This will remove any hardware, flash drives, disconnected devices, multiple entries, etc…)
Removed all the entries under Thrustmaster Devices (Uninstalling Target should have, but didn’t, remove these entries)
Removed all the light grey entries under Universal Serial Bus Controllers (Same as above, will remove anything not currently connected)Reboot (Without Warthog connected still)
Installed the Warthog drivers from https://support.thrustmaster.com/en/product/hotaswarthog-en/ following the instructions in the Release Notes about rebooting and when to connect controller etc. (IIRC, didn’t bother with firmware update)
Installed Target from same place following the instructions in the Release Notes same as above.Hope this helps, it was really frustrating trying to figure out what happened but haven’t had any issues since then.
-
Thanks Tex
I’ll give it a shot in the morning. I think/hope your pointing Me in the right direction.
Much appreciated.
-
Are you using TeamSpeak? I cannot get TARGET to apply filter driver when TS3.exe is running. When it is not running I can.
-
@ Tex, had no effect.
@ Fred, TS3 has no impact with or without.
-
Can you post your target profile / script. I’d like to take a look at it.
-
The point of the filter driver is to enable-disable devices to enact it’s proper changes. This almost certainly requires admin rights held by the program doing it which might include the background TM software as well as the Script/GUI EXE. What happens to me when I try to run script with TS3 is that it successfully creates or unmasks the virtual device but does not successfully hide the standard devices. And so I get all the joysticks, virtual and physical and I can’t remember if the virtual actually works or not.
If TS3 can disrupt the party then so can probably some other programs we don’t know about. I would close everything remotely optional first to test and see if it still fails.
TARGET GUI/Script should be run as admin.
The entire TARGET software package should probably be installed from an installer exe with elevated admin rights (including the creation of directories which also have associated rights). So any reinstall should delete as much of the previous structure including directories before reinstalling with elevated installers.
That’s all I can really think of. Win10 is strict and getting stricter on preventing any old program doing funnybusiness and this is the result.
-
@ Fred, Some good points.
I have tried with as much (as practicably possible) uninstalled, shutdown or Disabled.
I’m still on Win7 , and this might be part of the problem as it is officially only supported by Win10.
This is the first “topline” mobo I have ever splurged on, so I’m a pit peeved or more correctly confounded.
Other then this Target problem its a great performer.
If I cant find the conflict I may have to go full DX and lose some functions.
-
Sorry that didn’t help Shadow.
I’ll second what Frederf said, I have the Target stuff set with the compatibility tab set to run it as admin.
I don’t actually use the gui to load and launch the script manually, use a shortcut that runs it automatically, and it is set as admin under compatibility also.Shortcut Properties are:
Target: “C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe” -r “C:\Program Files (x86)\Thrustmaster\TARGET\scripts_Warthog_BMS_Full_Paddle_swap.tmc_”
Start in: “C:\Program Files (x86)\Thrustmaster\TARGET\x64”And the compatibility tab is set to Run as Administrator
-
Its not a rights or compatibility issue. One of the first things checked.
Its not a keyfile, Target user created script or .fcf problem either. (created empty items)
It has something to do virtualization.
My Logitech G900 also uses virtual devices, that’s the next item to eliminate. It’s also a recent addition.
-
Its not a rights or compatibility issue. One of the first things checked.
Its not a keyfile, Target user created script or .fcf problem either. (created empty items)
It has something to do virtualization.
My Logitech G900 also uses virtual devices, that’s the next item to eliminate. It’s also a recent addition.
Well damn, I had the exact same problem. I remember getting that same filter error. Once it’s solved, we will remember forever next time…
-
I’m still on Win7 , and this might be part of the problem as it is officially only supported by Win10.
It certainly is NOT an issue of running it on Win 7 as I am also still running Win 7 and using TARGET version 3.0.16.615 and I am not having that virtualization problem at all. I always run installers as admin so the install can go smoothly but I do not run TARGET as admin even if doing so might be best practice and it works fine for me.
-
Win7 should be the best at this. It’s Win10 that increased my number of problems with TARGET.
This is what my output log shows when I run with TS3 active. I get:
Running script: B:\Desktop\Gaming Support\Combat Flight Sim Aux\TARGET\DuckBMSv7.tmc *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** 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: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" ```which hangs for ~5 seconds and completes with
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\8&1BECBDEA&0&4) 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_0400” cannot be found
USB HID device with hardware id “VID_044F&PID_B10A” 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)…Donemain returned 0
On the other hand if I run without TS3 running I get:
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
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: “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\8&1BECBDEA&0&4) 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_0400” cannot be found
USB HID device with hardware id “VID_044F&PID_B10A” 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)…Donemain returned 0
I wonder how that compares to your experience. Does it hesitate in the same spot with the same kind of output text or not?