A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
Having an issue here, I just reinstalled windows and BMS with it, and now when I run the TARGET script, I’m not seeing “Thrustmaster Combined” in the setup menu or in my windows devices list. I’m only seeing “Thrustmaster Virtual Game Controller (root).” Using the most recent version of TARGET and have never had Teamspreak installed. Any help appreciated, thanks.
Just to note that I too am running in this issue and investigating the solutions pointed by Gastone.
-
Uninstall target, uninstall all the devices, and start from scratch. it’s the only way I’ve figured out how to keep it working.
Win 10 is being a bear nowadays along with the Nvidia drivers.
Just have to deal with it the best we can. -
Just to note that I too am running in this issue and investigating the solutions pointed by Gastone.
solved!
-
solved!
How? I have exactly the same problem. Currently only some of the buttons work and some buttons do pretty weird things.
EDIT: Got it working too! Just downloaded the new files from the 1st page as directed. Now I feel stupid
-
Good Job bro, thank you …
I installed your profile and config and everything was just fine, until suddenly when I click TQS UHF button, which is the right hat switch on the throttle, when i pull it up, it also presses on left MFD OSB 3 at the same time, I closed the game, closed YAME, and just let the profile running, when I press TQS UHF on desktop, the mouse changes it’s location and presses on the same place where OSB 3 on my second screen… -
Check that device sorting is setup properly, the Thrustmaster combine should be at the top. Next, verify that the target software is working properly. With the profile running hit the Windows start button and type joy.cpl This opens the joystick control panel. You should only see Thrustmaster Combine, the software should be hiding the actual joystick and throttle when a profile is running.
-
This post is deleted! -
Check that device sorting is setup properly, the Thrustmaster combine should be at the top. Next, verify that the target software is working properly. With the profile running hit the Windows start button and type joy.cpl This opens the joystick control panel. You should only see Thrustmaster Combine, the software should be hiding the actual joystick and throttle when a profile is running.
I checked everything, and all was OK…
I checked the Throttle mapping to figure out what is the name of this switch that is responsible for TQS UHF, and it was MIC Switch up, so in .tmc text file, I found this line
"//Mic Switch
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27)); "
I thought that this “Mouse_Center” is doing something wrong, so i took a copy of the file, and erased this word
Of course that ruined everything, so i undo the modification I made, but it didn’t help …
So I removed Target, removed the profile text file and key mapping file, and installed everything from scratch…
Guess what, the problem still exist -
I checked everything, and all was OK…
I checked the Throttle mapping to figure out what is the name of this switch that is responsible for TQS UHF, and it was MIC Switch up, so in .tmc text file, I found this line
"//Mic Switch
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27)); "
I thought that this “Mouse_Center” is doing something wrong, so i took a copy of the file, and erased this word
Of course that ruined everything, so i undo the modification I made, but it didn’t help …
So I removed Target, removed the profile text file and key mapping file, and installed everything from scratch…
Guess what, the problem still existSomething else is going on outside of the profile causing your issue. The profile sends one of two commands, depending on if the shift button is pressed. The profile sends either Joystick button 27 or Joystick button 27 and the middle mouse button. It sounds like you have OSB button 3 bound to joystick 27 button in YAME or middle mouse button. Check the callbacks tab in YAME to see what’s going on. Also, just make sure you have all the most recent files for the profile. They are on page 1 of this thread. If you really think the middle mouse button is causing your problems, you should be able to comment out that line of code and have the profile work just fine. Change```
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27));to
//MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27));
-
It sounds like you have OSB button 3 bound to joystick 27 button in YAME or middle mouse button. Check the callbacks tab in YAME to see what’s going on. Also, just make sure you have all the most recent files for the profile. They are on page 1 of this thread.
Thank you for the quick response, well it’s a good point of view as I was playing with Helios and I found a key map or something that ties YAME, Helios with joystick profile, I’ll try to find it and then delete it.
But I wanna say that this issue happens even if YAME is not running, Like if I started Hotas profile and clicked on this MIC Switch Up ( on desktop), the mouse moved to the same place of OSB3 on my second screen and clicks …
so, does YAME have something to do with it ? -
Thank you for the quick response, well it’s a good point of view as I was playing with Helios and I found a key map or something that ties YAME, Helios with joystick profile, I’ll try to find it and then delete it.
But I wanna say that this issue happens even if YAME is not running, Like if I started Hotas profile and clicked on this MIC Switch Up ( on desktop), the mouse moved to the same place of OSB3 on my second screen and clicks …
so, does YAME have something to do with it ?Here’s the bottom line, unless you’ve messed with script, the only thing the joystick sends is Joystick button 27 or Joystick button 27 + middle mouse button. It does not manipulate mouse position in anyway, and therefore the profile can not be the cause of you’re issue.
With each additional post you keep telling me about more third party software that could be sending commands based on joystick button presses. You need to debug that software on your own. Troubleshooting the profile and 2 pieces of third party software goes beyond the scope of support I’m willing to provide. Just as one last sanity check, please post the contents of you’re devicesorting.txt here.
-
Just as one last sanity check, please post the contents of you’re devicesorting.txt here.
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Virtual Game Controller (root)”
{C215046D-0000-0000-0000-504944564944} “Logitech Extreme 3D Pro USB”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{076406A3-0000-0000-0000-504944564944} “Saitek Pro Flight Combat Rudder Pedals (USB)” -
Based on your Devicesorting.txt, I can tell target is not functioning properly. In your device sorting, you should have “Thrustmaster Combined” at the top. “Thrustmaster Virtual Game Controller (root)” means the profile did not complete it’s setup correctly. The number 1 cause of this issue is the teamspeak bug. You’ll have to remove the joystick addon and restart. Detailed instructions are on page 1 of this thread.
There may also be numerous other causes of the Target Bug. It’s been reported that it maybe caused by performance monitoring software like MSI afterburner, power management settings, registry settings, ect. Review the last few pages of the thread and you’ll see numerous people struggling with the problem also.
I run a pretty clean system, Windows 10, and I have zero issue with the script or target. And since there is an infinite combination of system configurations and software, the problem is not something i can feasibly debug for everyone. The only way to eliminate causality is to do a clean install of target and warthog drivers, including deleting any registry entries for the devices. Remove as much of the 3’rd party software as u can, until you get Thrustmaster Combine to appear in the joystick control panel. Click start and type joy.cpl to view it. However before you going doing that, try fixing the teamspeak bug first. It’s generally the most pain free fix.
-
Based on your Devicesorting.txt, I can tell target is not functioning properly. In your device sorting, you should have “Thrustmaster Combined” at the top. “Thrustmaster Virtual Game Controller (root)” means the profile did not complete it’s setup correctly. The number 1 cause of this issue is the teamspeak bug. You’ll have to remove the joystick addon and restart. Detailed instructions are on page 1 of this thread.
There may also be numerous other causes of the Target Bug. It’s been reported that it maybe caused by performance monitoring software like MSI afterburner, power management settings, registry settings, ect. Review the last few pages of the thread and you’ll see numerous people struggling with the problem also.
I run a pretty clean system, Windows 10, and I have zero issue with the script or target. And since there is an infinite combination of system configurations and software, the problem is not something i can feasibly debug for everyone. The only way to eliminate causality is to do a clean install of target and warthog drivers, including deleting any registry entries for the devices. Remove as much of the 3’rd party software as u can, until you get Thrustmaster Combine to appear in the joystick control panel. Click start and type joy.cpl to view it. However before you going doing that, try fixing the teamspeak bug first. It’s generally the most pain free fix.
Man, I really appreciate you efforts of sorting everyone’s problem out, including me, I know also that it’s an annoying task to think and troubleshoot these problem remotely …
I just made a trick and it did work for now, I changed the location of the MFD where the mouse was clicking, cuz I noticed that it clicks in a fixed point over the screen, so now it clicks in a non clickable gauge, So… problem solved although I will try to fix the issue of “Thrustmaster Combined” line
Thanks bro, cheers -
This post is deleted! -
Hi everybody,
Not sure if this is the right place to post the issue I have. I am using Hotas warthog with the profile Warthog_BMS_Full_Paddle_Swapp.tmc and BMS_Full_&_Morphine_paddle_swap.key. When I load through Target everything works correct except the datalink Activation. I use TQS: COMS swith Left - IFF out during around 10s with “CONT” at the MFD screen and nothing happen until all the flights are flying. If I Use the option to send back to base 3 and 4 flights through the Keyboard, Datalink in “CONT” mode shut down until the flights arrive to the Airport. The Other two datalink Options works fine. I share this issues with my colleagues and they told me that is strange, they can activate Datalink if they are even at ground pending to take off.Any idea how to solve this issue?
Thanks in advance -
Hi everybody,
Not sure if this is the right place to post the issue I have. I am using Hotas warthog with the profile Warthog_BMS_Full_Paddle_Swapp.tmc and BMS_Full_&_Morphine_paddle_swap.key. When I load through Target everything works correct except the datalink Activation. I use TQS: COMS swith Left - IFF out during around 10s with “CONT” at the MFD screen and nothing happen until all the flights are flying. If I Use the option to send back to base 3 and 4 flights through the Keyboard, Datalink in “CONT” mode shut down until the flights arrive to the Airport. The Other two datalink Options works fine. I share this issues with my colleagues and they told me that is strange, they can activate Datalink if they are even at ground pending to take off.Any idea how to solve this issue?
Thanks in advanceI looked at both files on the dropbox, they both setup properly. So the issue is either a bug in BMS or user error.
Are you holding the com switch button for 1/2 second or more? You need to hold com switch left, which is back towards the user on the coms hat on the warthog. You should hold it till you hear the system chirp.
Is anyone one else hosting the link in continuous mode while you’re attempting to use it. Only one person can host in continuous mode, if others are hosting a link the system wont work.
Also make sure you have both the ADLINK and GDLINK enabled in the HSD CNTL page. They are on by default so this shouldn’t be an issue unless you’re mucking about in the HSD CNTL page.
If you are using the system correctly and still are having issues. I think what you’re reporting is more related to how the AI manages the DATA link, and the question would likely be answered more thoroughly in another section of the forum. Since it really doesn’t pertain to operation and function of the Profile.
-
Thanks Gastone, I just arrived. I will Follow your recommendations and let see.
-
Just found this post . . . Thank for providing this information.
-
had trouble (not seeing rudder axis in bms) when plugging my new TPR pendular rudder and its updated TARGET v.3.0.18.328, but adding the following line to the beginning of the script made it work like a charm again:
Configure(&TFRPHARudder, MODE_EXCLUDED);