Win10 Creator edition and Target Software Issue
-
Just updated to the creator edition of Win10 Pro and now when I run a target script, it states that it cannot find several USB HID devices with various hardware id’s. In addition, while the device analyzer lists the TM Combined, it will not work. In the device manager, there is no yellow icons so what is the problem?
The QUICK response from TM Support-
We thank you for your reply.We like to inform you that we have received your message and that we have forwarded the info to our R&D department.
As mentioned previously we have received similar reports and we are investigating this problem resulted from the latest update package released by Microsoft. Your info will be of great value to our colleagues.
If any additional details will be needed from you we will contact you immediately.
This might take at least a couple of weeks from now on. We will get back to you as soon as we will have some definitive solutions.
If you have any other inquiries do not hesitate contacting us back by simply replying to this email.Note: Putting the d3d9x.dll from c:\windows\system32 in the traget program folder DID NOT SOLVE THE PROBLEM FOR ME.
-
The issue with Target and windows 10. Is caused by a conflict between a piece of the target software called DeviceManagaementApp, and the OS. When the program quits they are both trying enumerate the USB devices simultaneously. It can cause a system lock up which requires a hard restart. A simple fix exists, just delete the program. It’s located in Program Files (x86)\Thrustmaster\TARGET\x64. Credit for solution goes here https://forums.eagle.ru/showpost.php…95&postcount=1
The only issue with this fix is that your physical devices no longer remain hidden from the OS.
Since there is no way for BMS to ignore or hide devices you can get conflicting joystick buttons. As you BMS sees you hitting you stick button 1 on two devices simultaneously, i.e. the physical stick and the virtual device target creates.I’m pretty sure target has know of this since Nov of last year and had done nothing about it too.
-
Gastone
Your suggestion has been tried and no joy on win10 creator update. -
Helios is running fine in Win10 Creator, but not so with Target. For some reason, Target keeps dropping my TM USB rudder from the script. So as long as I exclude the rudder from any script, I have been having NO issues.
-
I recently updated to Creator Edition, I’ve had no issues with Morphine’s profile with the latest version.
Devices switch automatically back and forth in Device Mangler. -
TxMtb
If I recall correctly, Morphine’s profile excludes the rudder so it should work ok. -
TxMtb
If I recall correctly, Morphine’s profile excludes the rudder so it should work ok.I believe you are correct, IIRC, Gastone is the one making the latest versions of it.
-
Morphine’s original does not exclude the rudders. The version I’m keeping up to date does. If you’re getting warnings about HID devices not be being found, it’s because the script is trying to exclude devices that are not connected, it’s not really an issue as the script will keep running anyway. The original Morphine’s excluded the cougar stick and MFD’s. My latest version excludes all those plus all T-1600’s TFRP, and TWCS gear. You can download it here.
https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0
-
Gastone
You are technically correct. While Morphine’s profile did not exclude the TM rudder, this was because it had not existed at the time he did his profile. My problem is different. When I run a target profile that includes the TM rudder, it does not work. This has only happened since the Win10 CE. Thankfully, Ice’s BMS target profile and my DCS A10-c Helios profile do not use the TM rudder so they work fine. In addition, HomeFries target profiles for DCS planes specifically excludes the TM rudder and they seem to work fine (so far). -
Gastone
You are technically correct. While Morphine’s profile did not exclude the TM rudder, this was because it had not existed at the time he did his profile. My problem is different. When I run a target profile that includes the TM rudder, it does not work. This has only happened since the Win10 CE. Thankfully, Ice’s BMS target profile and my DCS A10-c Helios profile do not use the TM rudder so they work fine. In addition, HomeFries target profiles for DCS planes specifically excludes the TM rudder and they seem to work fine (so far).So have to ask, why would you include the TM rudder to start with?
-
In some games, I like to program the rudder to perform certain functions that can only be done by Target so I do not use some axis’ on the warthog.
-
In some games, I like to program the rudder to perform certain functions that can only be done by Target so I do not use some axis’ on the warthog.
Understood, hadn’t thought about that.
-
Today’s response from TM:
We thank you for your reply.Under these circumstances then the problem is caused by the latest update you have installed for the OS, the “Creators Update”.
We are currently investigating this problem ourselves, analyzing the updates this patch brought to the actual OS and the modifications it made to various sub-systems so that we can determine what might be interfering with the TARGET’s normal performance.
For the moment we do not have any additional details to provide you with.
-
I wonder if it is safe now to upgrade to the creators edition or are there still issues with target?
-
Still an issue at least with me.
-
Not an issue with me. I don’t know what the cause of the difference between sobe and me is.
-
Not an issue with me. I don’t know what the cause of the difference between sobe and me is.
Not having any issues here, yet, either. I think Sobe is including the new TRFP’s in the script and that is what causes the issue.
-
After installing Win10 Creator ed., I continue to have problems with Target. The following is a target script in which the only controller programed is the TM rudders. What does the line Error: (internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_B679”
mean?Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Physical USB HID devices managed by script!
Currently plugged USB HID devices[5]:
1: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
2: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
3: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
4: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
5: “T-Rudder” - “USB\VID_044F&PID_B679&REV_0110”
Installing filter driver to VID_044F&PID_B679. Please Wait…Done!
Error: (internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_B679”
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
-
VID is vendor ID, PID is product ID.
And those numbers are for the TM rudder pedals. First I would make sure I was running the latest TARGET because if memory serves there were updates with regards to rudder compatibility. I’m running 3.0.16.520 and you don’t have to turn the calendar back too long to go back 1 or 2 versions.
https://www.reddit.com/r/starcitizen/comments/4zxrud/tm_trudder_pedals_issues_in_sc/ might be helpful.
I’m curious if you get different behavior if the pedals are/are-not excluded from device integration. If the problem goes away with excluded pedals then happy days because in 99% of cases you want pedals excluded.
-
I downloaded version 3.0.16.615 V2 and got the following :
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Physical USB HID devices managed by script!
Currently plugged USB HID devices[5]:
1: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
2: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
3: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
4: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
5: “T-Rudder” - “USB\VID_044F&PID_B679&REV_0110”
Installing filter driver to VID_044F&PID_B679. Please Wait…Done!
USB HID device “T-Rudder”(USB\VID_044F&PID_B679\6&1454EE2&0&7) 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)…Donemain returned 0
I had version 615 before, but maybe not the second version. Will see what happens.