Since the latest update i get this error during loading when Thrustmasters TARGET Script is running.
It runs just fine, showing Thrustmaster Combined in the compiler but then all of a sudden:

Error:One of the selected USB devices (0) has been unplugged. Aborting script!

This results in 2 separate Warthog controllers instead of one combined and then makes the controllers useless in MSFS. Only option is restart and hope for the best.

I have been looking through the internet to find a solution because my first thought was a USB or controller hardware problem. 
Most of the solutions found point to the USB power management letting the device go to sleep but i have turned these all of (and rechecked again cause you'll never know).
Also, un-installing/re-installing drivers and target as i found somewhere is not the solution.

It then occurred to me that it only happens in MSFS, not in my other sims (DCS, IL-2, X-Plane).
For this i've been running tests all afternoon and evening. It never failed in DCS, IL-2 or X-Plane (tried each 10 or more times) but only in MSFS and that in around 85% of the cases, the 15% other times it was fine.
It happens always during the loading of the sim into the main screen, just before the loading ends and just before the main screen becomes live, never in any flight.
If i have Target open on 2 second monitor, the script then suddenly stops, gives the error and i always can run the script again (but then the Thrustmaster Combined isn't recognized in game) and then it never fails again.
Also, when it happens, i always loose the Numpad 7 key on my keyboard (wireless). Tested with another wireless keyboard that i have lying around, same story when the error shows up so it's not the keyboard.
And... i'm also looking my Warthog Combined setup within the sim each time. Have to set it up again each and single time the error occurs.
Been running, loading and quiting DCS, IL-2 and X-Plane for the last 1,5 hours, not an single problem.
I just loaded MSFS again, bang....Error:One of the selected USB devices (0) has been unplugged. Aborting script!

It's always device (0) that gets "unplugged". Device 0 is the throttle (i get the same error when i physically unplug the throttle (when i unplug the stick, it's device 1).
That it isn't really unplugged in reality is also viewable because after unplugging the throttle physically the LED's always come on and that is not the case.

So i'm a bit and the end of my line here....

 

Edit: Forgot something
I can let the script running for hours, not a single problem. But the moment i run MSFS: unplugged error.
If Thrustmaster Combined within the sim has nothing assigned to it, it always loads fine, no error.

Edited October 10, 20223 yr by Lange_666

Think i solved this one:
Because each time the script stopped, MSFS came with the message that a new device was connected (due to the script being stopped, the "combined" setup changes back to 2 separate devices) and if wanted to load default or customize the new device.
When i then reloaded the sim and i was lucky and the script didn't got interrupted, all the setting i entered the previous time where gone again. Each and every time my combined setup was set back to default.
Then when i needed to set it up once again i made a copy of the setup through the preset manager.
Next time the error occurred and i lost my just made setup again, i then could select the backup and move on.
This made me think that could have a corrupt Warthog combined configuration file within MSFS which, when it was loaded made the Target Script editor think the combined device disconnected briefly giving the error and load an 2 separate Warthog devices instead.
I then deleted every configuration file for the Warthog combined setup through the sims preset manager, including the default one (which was empty anyway).
After this action, each and every time i loaded the sim the script kept running, no more device unplugged errors.

Edited October 12, 20223 yr by Lange_666

PS: For the Numpad 7 key problem MSFS wasn't the cause but TrackIR was. Setting an action key "enabled" in a profile makes the key non-responsive from the keyboard while TrackIR is running.

Edited October 12, 20223 yr by Lange_666