Morphine's Profile
-
Thank you. Did you swap both so trackir is on the pinky?
Yes, the entire functions of pinky and paddle switched have been swapped. Meaning you must also use the key file in the dropbox too.
-
Thanks, bud.
-
That is strange…for some reason TARGET is not hiding the physical devices, so no matter what I do, I always end up with below:
{076306A3-0000-0000-0000-504944564944} “Saitek Pro Flight Rudder Pedals”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Virtual Game Controller (root)”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”Same here, try to modify devicesorting.txt but not working
-
Mine didn’t hide them but added combined like this.
FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{00F2068E-0000-0000-0000-504944564944} "CH PRO PEDALS USB "
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog” -
If the target won’t hide the physical devices, try this; Open the script editor, load the profile, hit compile, then hit run. For me this always hides the physical joystick. Target has been pretty buggy since they upgraded it a while ago.
-
That’s all I use is the script editor. I did like you said. Compiled it and ran it. When i’m done I shut it down and repeat the next day. It works perfect. I never touch the target icon. Am I doing it wrong?
-
That’s all I use is the script editor. I did like you said. Compiled it and ran it. When i’m done I shut it down and repeat the next day. It works perfect. I never touch the target icon. Am I doing it wrong?
utilizing the script editor and compile method, is it hiding the physical device from your system? After u run the script, go to the windows start button and run joy.cpl to check if they are hidden.
-
I just checked and I get the stick, throttle, and pedals as separate.
Am I doing it wrong? Do I need to go through script and target. It seems to work ok the way i’m doing it.
-
Oops! You said after I run script. I just did that and now I have all three the same as before, but combined is added to the list.
-
Are you looking at the devicesorting file? If so it’s doing what it should.
If you start BMS WITHOUT the script running, it will detect the throttle and stick separately, then if you run the script and start BMS a second time, it will NOT remove the individual entries but will add the combined device.To check:
Delete the devicesorting file, or just change the extension to .bak.
Run the Target script
Run BMS
Exit BMS
Check the devicesorting file and see what is in there.
Adjust the device order in the file, making combined the first line.
Make sure the script runs every time before you enter BMS, or it will add the separate devices back in again. Think you can also write protect the file after you have it set correctly. -
Yes, that’s how it works for me. I know, because I forgot to startup script once.
My question was I never started up Target. I’ve only worked with the script. I guess you only need to run target if you were making the profile.
-
Yes, that’s how it works for me. I know, because I forgot to startup script once.
My question was I never started up Target. I’ve only worked with the script. I guess you only need to run target if you were making the profile.
You don’t need to run the target GUI to run the script. Both methods should work, though I’ve found the GUI to be more buggy than the script editor as the script editor always hides the physical devices from the system.
As per your early replies when you said “I have all three same as before but combine is added to the list”, which list, the device sorting or the joystick control panel?
-
Device Sorting.
-
Device Sorting.
Thanks for the reply. The reason I asked, is I am considering writing a new guide for the profile and want to establish a working methodology for launching the profile. As you can see from the last few pages of this thread, target not hiding the physical devices can be an issue. From the feedback here it looks like the script editor is the only reliable way to get target to hide the physical devices from the system.
The only way to check if the script is hiding the physical devices from the system is through the windows joystick control panel, (joy.cpl at the start menu) Even if the script hides the physical devices from the system they won’t disappear from device sorting.
If everything is working well and you’re not getting any ghost button presses. It sounds the like the script is hiding your physical devices from your system, so it won’t matter if your physical devices are listed in devicesorting.txt because window and BMS doesn’t see them.
-
Why I had to isn’t important, but this morning I had to do a complete reinstall of BMS. So, that also meant I had to reinstall the script too, so I paid more attention this time. I installed your file in script, compiled and ran it. I looked in device sorting and it just showed stick and throttle. No combined. I then started up BMS and loaded the key file and chose the combined as my first controller. After closing BMS I checked device sorting again and now combined showed but was on the bottom. I edited it to show combined on the top. I went back into BMS and had to pick combined again. From that point on going in and out of BMS combined stayed as first controller and device sorting show combined on top. It continues to show stick and throttle too in device sorting.
-
You don’t need to use the editor or gui to launch the script, you can create a shortcut that does it for you.
If you follow the standard target install:
Create a shortcut.
Target field = “C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe” -r “C:\Program Files (x86)\Thrustmaster\TARGET\scripts*Warthog_BMS_Full_Paddle_swap.tmc*” (The name of your script)
Start in = “C:\Program Files (x86)\Thrustmaster\TARGET\x64”I’ve never had an issue running them this way.
-
I’ll give it a try. Thanks.
-
Hello. So I’m suddenly getting a drift to the left and up of the cursor set to the XY rotation. I never used to have that and I don’t have that problem if the script isn’t running. I tried increasing The Dead Zone in game and it didn’t help any suggestions?
Edit: Well it’s more than that. Similar to what some folks are posting above. When I run the script (the drop box version) my throttles won’t even work now. Go from full off to full on like a switch. Never had this problem before. Last time I ran the script was probably April or May… Any thoughts on what would have updated between now and then to break this?
-
Maybe the script is choking. Does the script fail when looking at the device analyzer?
-
Any thoughts on what would have updated between now and then to break this?
Windows. MS messed with something in the enumartion process that has rendered target unreliable. Problems with axis and double button presses is most likely related to target not hiding the physical devices from the system.
You can check if this happening by running the script, then going to Windows start menu and running joy.cpl. If both the physical devices and the virtual device are there, then you’re going to have problems. The only reliable way I can run the script correctly is to restart windows then run the target script editor, hit compile and then it run. If I run any other program before I run target the script will often hang, but still run, though it won’t hide the devices. Which results in a faulty profile.
I wish I could provide a more reliable method for running the script but there is something going on with target, that needs to be fixed tby thrustmaster.