Issue with TARGET script

[AstonMartinDBS]

According the instructions in the Thread https://forums.eagle.ru/showthread.php?t=210857 I've managed to bind every switch position of my Warthog Throttle. It generally works well with DCS, but there's a little issue in the script which causes the following strange behaviour:

 

When I start the TARGET-script for the first time

 

• immediately (within first minute) after the windows-login it works as intended: the virtual device "Thrustmaster Virtual Game Controller (root)" is created and the native "Throttle - HOTAS Warthog" will be removed/hidden (screenshot #2)
  
• after a few minutes after windows-login it doesn't work correctly: the virtual device will be generated as well, but the native device is still there (screenshot #3)
  

Any ideas to fix this behaviour? The native "Throttle - HOTAS Warthog" device should be removed, otherwise it would be preferred against the virtual device in DCS and the script would be useless.

 

I've attached my slightly modified script, where I just added the lines for excluding not connected and unneeded devices (TFRP) in comparision of the original script in the referred Thread. But the described behaviour occured in the original script as well.

 

I'm not able to locate the code which removes or hides the native device from the gamecontroller list.

targetdx128 20200425.zip

[Bobik2002]

I have same problem, I have it about year....

My solution is delete all config of throttle in game.

[AstonMartinDBS]

I have same problem, I have it about year.... My solution is delete all config of throttle in game.

I use the same workaround, but it's not a satisfying solution for me.

 

I think that this issue can be fixed by an expert.

Edited April 25, 2020 by AstonMartinDBS

[Ant0ine]

otherwise it would be preferred against the virtual device in DCS and the script would be useless

 

In DCS you could just clear the the Warthog throttle category. Problem solved, for other game however it could be a real issue indeed.

 

I never experienced that issue. Or maybe I did, but I didn't noted that it was only occurring just a few minture after reboot.

 

I can think of two thing, the windows store, and bad Target installation. Target must be installed while no target compatible device are connected :

 

And about windows store problem you can find more info here :

https://forums.eagle.ru/showpost.php?p=3925050&postcount=20

 

Good luck.

[Frederf]

I get the same behavior. Windows is protecting the system from some of the changes TARGET is trying to do: virtually remove devices. I have to physically unplug and replug the device before running the script for the remove/add process to work properly. If I don't the virtual device doesn't work, the real device doesn't get removed and it's unworkable.

 

I have tried reinstalling and every trick. I'll try removing Windows Store and I guess one more reinstall of TARGET. If I have success I'll post again.

[AstonMartinDBS]

I can think of two thing, the windows store, and bad Target installation. Target must be installed while no target compatible device are connected :

Thx for the hints, I'll first give the correct reinstallation of the TARGET software a try.

[Thermal]

You could try excluding the Target executable from Windows Security, under "Virus & threat protection settings". This is an untested guess, I have seen other app's be impacted by this, it might help, it might not.

[AstonMartinDBS]

I can think of two thing, the windows store, and bad Target installation. Target must be installed while no target compatible device are connected :

 

And about windows store problem you can find more info here :

https://forums.eagle.ru/showpost.php?p=3925050&postcount=20

 

The proper re-installation of TARGET following the steps

 

• "disconnected my controller,
  
• uninstalled Target,
  
• Rebooted,
  
• reinstalled Target,
  
• rebooted,
  
• plugged controller"
  

didn't solve the issue for me. Uninstalling the Microsoft store isn't an option for me (several windows core-applications will be updated by the store frequently).

 

 

You could try excluding the Target executable from Windows Security, under "Virus & threat protection settings". This is an untested guess, I have seen other app's be impacted by this, it might help, it might not.

Excluding the whole thrustmaster- (c:\program files (x86)\thrustmaster\) and script directories (%appdata%/thrustmaster) from Windows Security didn't help... :(

 

Thanks anyway for your suggestions!

Edited April 26, 2020 by AstonMartinDBS

[AstonMartinDBS]

I've now also tried to deactivate the enhanced USB Powermanagement, according to https://forums.eagle.ru/showpost.php?p=3808285&postcount=6.

 

But when I reached the correct registry-entry I was surprised, that this option already was deactivated by default...

[Svend_Dellepude]

Let windows boot up before plugging in your controllers. That should work 99% of the time.

[AstonMartinDBS]

Let windows boot up before plugging in your controllers. That should work 99% of the time.

I did (after TARGET installation). Or should I do that after each windows boot up process? In that case I prefer the other workarounds... ;)

Edited April 26, 2020 by AstonMartinDBS

[Svend_Dellepude]

I did (after TARGET installation). Or should I do that after each windows boot up process? In that case I prefer the other workarounds... ;)

 

After each boot.

I got so tired of it that i bought a 8 port powered hub with an on/off switch, that i switch on after boot.

Works 98% of the time.

[AstonMartinDBS]

After each boot.

I got so tired of it that i bought a 8 port powered hub with an on/off switch, that i switch on after boot.

Works 98% of the time.

Well, in order to avoid other (esp. USB power) issues, all my gaming peripheral devices are connected either directly to the mainboard or to my 7 port PCIe Card.

Edited May 1, 2020 by AstonMartinDBS