Target Profile

Hi,

I have a TWCS and sometimes when I run one of my profiles in target, I get the Thrustmuster Combined device and also the TWCS. But some other times I get only the Thrustmaster Combined one which is how it is suppossed to work.

Any ideas?

anyone?

Although I don't know if this will help, sometimes I alter the control settings

and the controls are there. Just in a different place or order.

Down the bottom of the control bindings is a hard to spot grey slider.

Try moving it left and right to see if the controller your looking for is just out of sight. That's what tripped me up a few times.

Good luck.

Although I don't know if this will help, sometimes I alter the control settings

and the controls are there. Just in a different place or order.

Down the bottom of the control bindings is a hard to spot grey slider.

Try moving it left and right to see if the controller your looking for is just out of sight. That's what tripped me up a few times.

Good luck.

Sorry pocket, maybe I didnt express myself correctly.

The thing is that when you run a profile you should only have one device called Thrustmaster Combined and the actual device is removed.

My issue is that I get both devices listed and the profile launch takes several seconds to apply. If I unplug and replug the device then I get the one and only combined device.

Thanks!

Ok, I regret being unable to help you. At least there is coffee.

I get this when TeamSpeak is running. Other people get this because of admin rights issues or generally Windows 10 preventing the proper enabling/disabling of devices. That's how the exchange of devices is happening normally, as if it goes into device manager and enables one while disabling the other. This is a security-hazardous process and Windows often tries to prevent if it was a malicious program.

There are various fixes around, such as:

1. Ensuring no USB power saving is occuring

2. Setting all relevant EXEs have administrator rights compatibility (TmService.exe, DeviceManagementApp.exe, TARGETScriptEditor.exe)

3. Ensure TeamSpeak program is not running at the moment of script start or stop.

With these steps I have stopped having TARGET problems which I had commonly before!

I get this when TeamSpeak is running. Other people get this because of admin rights issues or generally Windows 10 preventing the proper enabling/disabling of devices. That's how the exchange of devices is happening normally, as if it goes into device manager and enables one while disabling the other. This is a security-hazardous process and Windows often tries to prevent if it was a malicious program.

 

There are various fixes around, such as:

 

1. Ensuring no USB power saving is occuring

2. Setting all relevant EXEs have administrator rights compatibility (TmService.exe, DeviceManagementApp.exe, TARGETScriptEditor.exe)

3. Ensure TeamSpeak program is not running at the moment of script start or stop.

 

With these steps I have stopped having TARGET problems which I had commonly before!

Hi and thanks!

The thing is that this never happened to me before and started happening a couple of weeks ago.

I have done the 3 steps and no luck.

Any idea?

Oh wait, I have not done the admin rights with the DeviceManagementApp.exe I dont know what or where it is.

Thanks

And anyway, why would it work perfectly after unplug and plug?

Its driving me crazy :(