TARGET weirdness, please help!
-
Hi guys, I definitely need help with TARGET.
Until a few days ago it was completely not working, it did never hide physical devices and that’s why the initial version of my profile - see this thread for the complete story - relied on this incorrect behavior… funny thing is, it was working with no hassle for me.
Then, after having upgraded all my rig drivers with Driver Booster (excellent stuff), it finally started working properly.
“Excellent!”, I thought, “let’s update my configuration the right way” and I released a new version just a few days ago, again it was working perfectly and I hope it will be useful to the many who struggled with my initial profile due to TARGET working right for them.
A couple of evenings ago I was ready to start flying with my VFW mates, I fired the Target Script Editor, run the profile and… BOOM!
Suddenly it was no longer able to mask physical devices - when it happens the script takes long to run, normally it’s istantaneous - with obvious consequences: all mappings in my keyfile did no longer match the right axes and buttons on stick and throttle… needless to say, absolutely no change on my part.
So I started investigating and, after a 2h long trial and error session (uninstall/reinstall drivers and TARGET, reboot, try this, try that), I disabled Windows 10 USB power management by editing my power plan advanced options and the matter seemed solved.
Yesterday afternoon I got back home from work, turned on the PC and tested the thing… all perfect, script immediately beeped as it usually does when it finishes its work and I correctly saw only the stick (which I no longer manage with it, it is purely DirectX programmed in the keyfile) and ‘Thrustmaster Virtual Game Controller (root)’ that is the virtual twin of my throttle, only with the POV hat and the rudder rocker remapped to DX buttons.
I came back after dinner, I was once more ready to fly with my mates… and guess what?
BOOM! AGAIN!!! No more hidden physical devices and all my mappings wildly remixed.
I tried rebooting, disconnecting the devices, verified that USB power management was still off (it was)… no joy. :shock:
I’m on the point of seriously giving up with it, problem is I can’t avoid using it because I’d lose TWCS throttle POV hat - thanks TM, it was a brilliant idea to put a POV on two different DX controlled devices :evil: - in addition to the rudder rocker remapping (I don’t need it because I use the stick rotation and letting it unused seems a crime to me).
Another thing that looks really strange to me is I checked the TARGET installation directory and the 2 executables of Target GUI and Target Script Editor no longer show their icon… I am sure it was there because I noticed it the first time, too, and explicitly checked for it after the last reinstallation… looks like a sort of corruption to me, but I really have no clue about possible causes.
Anyone willing to try to help me (@Frederf, I would particularly appreciate your thoughts, as you seem quite competent on TARGET), before I stop flying BMS because of frustration?
Thanks in advance! -
I found that TARGET won’t adjust the devices properly for me while TS3 is running. Sometimes it fails when TS3 is not running but always fails if TS3 is (except if I set keys to “Mouse and Keyboard Only”. It seems the DX hooking of TS3 is troublesome.). Often I will close TS3, stop profile, switch profile, run profile, resume TS3.
I have managed to get TARGET virtualization working by restarting the TmWinService (Thrustmaster FAST service) but not always (<50% of the time). Rebooting seems to always enable it. I get spammed by a lot of Windows 10 messages saying I have to restart Windows to complete the hardware change when running/stopping a profile. It does this at times with or without TARGET problems.
I’ve set TmService.exe to admin rights, cleared USB data and upgraded some drivers (Driver Booster 5). And I think I’ll try having TargetGUI with command line launch specific profiles (instead of running from the script editor) to see if that works.
I’m having the same problems as you are despite all the power management changes, etc. that people suggest. Yes, it is annoying.
-
Since Installing Win7 on my new Ryzen board I have also had continual fail to hide devices.
-
The issue is widespread. I’ve opened a support ticket with Thrustmaster detailing the problem and provided a link to my profile. They got back to me yesterday and stated they ran the profile successfully on two of their testing machines and stated the issue must be my machine. I then told them that my machine is up to date and that the profile almost always works if you run Target before running any application.
From my interactions with Thrustmaster support, I get the impression this is the first they have heard of this problem. I would recommend going to the support site and opening a ticket detailing the issue so they know how widespread this bug is. Mention that Target is not hiding the joystick and throttle from the profile when it runs, name the joystick you’re using, your OS and if possible provide a link to you’re profile.
You can file support ticket here.
-
I found that TARGET won’t adjust the devices properly for me while TS3 is running.
Then maybe we found the smoking gun: in fact, both times when I started TARGET and it failed I was already in TS with my mates, while when I made my quick test TS wasn’t on.
I’ll check this immediately and report… I really would never think of this by myself, thanks a lot!!!Since Installing Win7 on my new Ryzen board I have also had continual fail to hide devices.
Interesting… was it working correctly before switching to Ryzen?
IIRC Ryzen gives its best with Windows 10, maybe this adds to the problem?I would recommend going to the support site and opening a ticket detailing the issue so they know how widespread this bug is.
Yes, thanks, I filed a ticket yesterday immediately after posting here (I needed something to nearly cut 'n paste :D).
In order to be most effective, would you mind giving me the ticket # you were assigned by TM support, so that I’ll update mine referring to yours for them to establish a link?
Mine is [659380], maybe this will make them not underestimate the matter.Thanks all guys, BMS community is invaluable!!! :drink:
-
SMOKING GUN found.
Teamspeak3 is the offender here.
I’ll need to do some thorougher testing tomorrow. But for now its applying the filter as it should.
Thanks Fred
Post back latter.
-
Yes, thanks, I filed a ticket yesterday immediately after posting here (I needed something to nearly cut 'n paste :D).
In order to be most effective, would you mind giving me the ticket # you were assigned by TM support, so that I’ll update mine referring to yours for them to establish a link?
Mine is [659380], maybe this will make them not underestimate the matter.Thanks all guys, BMS community is invaluable!!! :drink:
Mine is 657989
@Shadow:SMOKING GUN found.
Teamspeak3 is the offender here.
I find that if I run any program which uses a joystick before I run target results in the profile failing to load properly.
-
SMOKING GUN found.
Teamspeak3 is the offender here.
I’ll need to do some thorougher testing tomorrow. But for now its applying the filter as it should.
Yes, it’s definitely TS to cause the trouble: I just checked (sorry for the delay) and can consistently reproduce both the incorrect (with TS running) and the correct (with TS not running) behaviour.
Let’s mass switch to Discord, which is in any case better. :headb:Mine is 657989
I find that if I run any program which uses a joystick before I run target results in the profile failing to load properly.
Thanks, TM still has not answered to my ticket, I’ll point them to yours as soon as they follow up.
Have you got any example of other programs that could use the joystick, so to further test the bug?
I am thinking about filing a bug with TS too (I really wonder why the hell TS needs to mess with joystick, by the way…) -
Thanks, TM still has not answered to my ticket, I’ll point them to yours as soon as they follow up.
Have you got any example of other programs that could use the joystick, so to further test the bug?
I am thinking about filing a bug with TS too (I really wonder why the hell TS needs to mess with joystick, by the way…)TS has a plugin for push to talk for the joystick. It’s been buggy for awhile. They attempted to fix it with the last patch. I would say it’s still problematic. They are doing something wonky with the enumeration process. Target won’t run properly if TS has been run, even after it has been shut down. I don’t think their enumeration process stops when u quit TS. Which is why the throttle and joystick keep reappearing after u launch the script. The TS process joystick plugin keeps querying them.
Then again there are still reports that target is still buggy, without TS.