Morphine's Profile
-
EDIT: I fixed the throttle lights, all appears fine for latest version of target while running Warthog_BMS_Full_2_Tpedal.tmc script. Will keep both verison of the script for legacy versions of target. See post below
FYI: Target Version 3.0.16.615 (the latest as of 11/23/16) is a bit buggy in regards to the current version of the script. You should only need to run this version of target if you have the new TFRP pedals, TWCS throttle or the new T.16000M FCS and you need to run a target script in other games. If you do not need any of those functions I highly advise not updating target till a patch comes out. I can confirm that version 1.011.304 works fine.
I have added a new target script to work around the bugs in target for people with the TFRP pedals. The script is called Warthog_BMS_Full_2_Tpedal.tmc and will be found in the dropbox hosting the current working version. Link below
There are still two issues though. The first is that lights indicating the afterburner position will not work in Target 3.0.16.615. Second, The device is not called Thrustmaster Combine, It’s now label in the system as “thrustmaster virtual (root)”, this should be placed at the top of devicesorting.txt. Please let me know if there are any issues running this version of the script and I will do my best to work them out.
Link to the Dropbox: https://www.dropbox.com/sh/4l2j2sbbkkmwoaa/AAAMks8YYDvUsOQ6vr7bi5bia?dl=0
-
I’ve been using 3.0.16 since I came back to BMS (with a new rebuilt Win10 system) and the only issues I’ve seen I thought were due to BMS. Good to know it’s thrustmaster related.
Regarding the afterburner lights, they worked for me, but there didn’t seem to be an accurate relationship between each light step and afterburner position. -
FYI: Target Version 3.0.16.615 (the latest as of 11/23/16) is a bit buggy in regards to the current version of the script.
So I fixed the TFRP Rudder script so that the afterburner lights function as morphine intended with the latest version of target. Tested in 4.33u2 and all functions work. Though the thrustmaster virtual device is still called “thrustmaster virtual (root)”. Select this as your primary device in game and place this at the top of devicesorting.txt, load the keyfile from the drop box in game and setup your axis. You’ll probably have to set the rudder to keyboard as by default it wants to set the throttles there. Same dropbox as above should work.
-
Gastone, I just loaded your new files and works excellent!!. Just one request. I want to use the “PADDLE SWITCH” as Wheel Brakes (k). In march 20th (2012) Morphine wrote that can be done by replace in the Warthog_DX.key:
Paddle/S4 (…and so on…)
SimAPOverride 3 -1 -2 0 0x0 0
by
Paddle/S4 (…and so on…)
SimWheelBrakes 3 -1 -2 0 0x0 0
When I edit your file :BMS_Full_&Morphine.key to make that change I discovered that yours and morphine are not similar, so I am not sure how to follow. Can you please let me know what lines I should add or delete in your BMS_Full&_Morphine.key to use the “PADDLE SWITCH” as Wheel Brakes (k)
Thanks in advance
-
Gastone, I just loaded your new files and works excellent!!. Just one request. I want to use the “PADDLE SWITCH” as Wheel Brakes (k). In march 20th (2012) Morphine wrote that can be done by replace in the Warthog_DX.key:
Paddle/S4 (…and so on…)
SimAPOverride 3 -1 -2 0 0x0 0
by
Paddle/S4 (…and so on…)
SimWheelBrakes 3 -1 -2 0 0x0 0
When I edit your file :BMS_Full_&Morphine.key to make that change I discovered that yours and morphine are not similar, so I am not sure how to follow. Can you please let me know what lines I should add or delete in your BMS_Full&_Morphine.key to use the “PADDLE SWITCH” as Wheel Brakes (k)
Thanks in advance
Edit line 1161, change the callback from SimAPOveride to SimWheelBrakes.
-
Thanks Gastone!!! it works perfect,
-
Hello!
Long time gone, looking to get back into the sim
Thanks for your work Gastone! I have one small question: is there anything I need to change in the profile if I do not have rudder pedals? (I only have the Warthog…so sad…)
Thanks in advance!
-
I get the following message when I run the scrip in the editor. I don’t remember seeing this before. Is this something new? It does appear the script is running okay.
USB HID device with hardware id “VID_044F&PID_B10A” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B679” cannot be foundRunning a Warthog and Saitek Combat Pro Rudders
-
I get the following message when I run the scrip in the editor. I don’t remember seeing this before. Is this something new? It does appear the script is running okay.
USB HID device with hardware id “VID_044F&PID_B10A” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B679” cannot be foundRunning a Warthog and Saitek Combat Pro Rudders
That’s normal, those are the id’s for the new tfrp pedals, throttle and joystick. If u don’t have them then they can’t be excluded from the script, so it returns null, but the script keeps working. The exclusions were included to future proof the script.
For my sake what version of target are u running and what is the title of the script you’re running?
Hello!
Long time gone, looking to get back into the sim
Thanks for your work Gastone! I have one small question: is there anything I need to change in the profile if I do not have rudder pedals? (I only have the Warthog…so sad…)
Thanks in advance!
Nothing really. For convenience you may want to rebind the wheel breaks to paddle switch in the script. Just edit line 1161 in the key file, change the callback from SimAPOveride to SimWheelBrakes.
-
Okay makes sense… Was having some issues but I think it was Windows 10 and USB being weird as usual
-
Okay makes sense… Was having some issues but I think it was Windows 10 and USB being weird as usual
Let me know if things aren’t working for you. Depending on the version of target you’re running there can be some issues.
-
Due to the latest version of Target supporting more hardware. I’m going to host 2 dropboxes for Morphine’s profile. One will support legacy versions of target, the other will support the latest version of Target, 3.0.16.615.
Both are verified working now. If you have an old version of target you should only need to updated it if your using the latest Thrustmaster HOTAS or the TFRP pedals from Thrustmaster.
Morphine’s Profile For Latest Version TARGET download from here:
https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0Morphine’s Profile For Legacy Versions of Target Download From Here:
https://www.dropbox.com/sh/4l2j2sbbkkmwoaa/AAAMks8YYDvUsOQ6vr7bi5bia?dl=0 -
Hello Gastone,
I tried the last profile you posted for the LATEST Version of Target and when I try to run it I receive the following message :
“Compile Error: Type required in Warthog_BMS_Full_2_Target_New.tmc at line 1”Any idea why ?
Thanks -
Hello Gastone,
I tried the last profile you posted for the LATEST Version of Target and when I try to run it I receive the following message :
“Compile Error: Type required in Warthog_BMS_Full_2_Target_New.tmc at line 1”Any idea why ?
ThanksI downloaded the script from the dropbox again to double check and it compiles and runs fine on Target version 3.0.16.615, that is the latest version of the software. The compile error you’re seeing seems to be related to the first of the script include “target.tmh”
If you attempted to edit the script and deleted that line it will not run.
-
I downloaded the script from the dropbox again to double check and it compiles and runs fine on Target version 3.0.16.615, that is the latest version of the software. The compile error you’re seeing seems to be related to the first of the script include “target.tmh”
If you attempted to edit the script and deleted that line it will not run.
Yep…it work.
Sorry…probably I messed up some files.
Thanks -
Greetings all. A great big thanks to all involved in the making of this profile.
I’ve downloaded and installed the lastest version of the software and it works great, although I’ve noticed that the “Master Caution” which was mapped to the Return key has changed to Ctrl-Return. The Return key is now binded to the hardpoints.
Not a problem as such but I thought I should bring it up incase its not normal.
Thanks. Kind Regards.
Jay. -
Greetings all. A great big thanks to all involved in the making of this profile.
I’ve downloaded and installed the lastest version of the software and it works great, although I’ve noticed that the “Master Caution” which was mapped to the Return key has changed to Ctrl-Return. The Return key is now binded to the hardpoints.
Not a problem as such but I thought I should bring it up incase its not normal.
Thanks. Kind Regards.
Jay.Thanks man, there were some legacy issues still lingering from switch to 4.33 and upgrading Morphine’s profile. There was a lot of legacy and dead call backs in the code. So there was some mismatch between the current default layout and Morphine’s old profile. Some of which caused conflicts. I took this report as an opportunity to clean things up a bit.
So I finally took the time and went through legacy code and commented out all of the conflicts (i hope) and legacy / dead call backs. I left the code in place, just in case anyone has a use for it. There is some interesting stuff in there, ie a call back for SimSpeedyGonzalesUp.
I do recommend updating to the newest version of this profile as the key guide will more accurately reflect the bindings. You have to Update both the script and the key map BTW.
Just as an FYI many of the target bindings are not on the Key Guide, like the ext lights. Just something to remember if you do want to rebind.
As always you can download them from dropbox and please feel free to let me know if you have any issues.
Morphine’s Profile For Latest Version TARGET download from here:
https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0Morphine’s Profile For Legacy Versions of Target Download From Here:
https://www.dropbox.com/sh/4l2j2sbbkkmwoaa/AAAMks8YYDvUsOQ6vr7bi5bia?dl=0 -
Thanks man, there were some legacy issues still lingering from switch to 4.33 and upgrading Morphine’s profile. There was a lot of legacy and dead call backs in the code. So there was some mismatch between the current default layout and Morphine’s old profile. Some of which caused conflicts. I took this report as an opportunity to clean things up a bit.
So I finally took the time and went through legacy code and commented out all of the conflicts (i hope) and legacy / dead call backs. I left the code in place, just in case anyone has a use for it. There is some interesting stuff in there, ie a call back for SimSpeedyGonzalesUp.
I do recommend updating to the newest version of this profile as the key guide will more accurately reflect the bindings. You have to Update both the script and the key map BTW.
Just as an FYI many of the target bindings are not on the Key Guide, like the ext lights. Just something to remember if you do want to rebind.
As always you can download them from dropbox and please feel free to let me know if you have any issues.
Morphine’s Profile For Latest Version TARGET download from here:
https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0Morphine’s Profile For Legacy Versions of Target Download From Here:
https://www.dropbox.com/sh/4l2j2sbbkkmwoaa/AAAMks8YYDvUsOQ6vr7bi5bia?dl=0Greetings Gastone.
Thanks for your reply and also a great big thanks for taking the time to check out the bindings. Just read your post and I’ll download and check your new updated profile ASAP. It’s a bit late right now over here were I live you see. I’ll let you know if there’s any issues.
Once again, I would like to thank you aswell as Boxin and obviously Morphine (hope I don’t leave anyone out), for making this profile available for everyone.
Great stuff. Keep you posted.
Yours gratefully. Kind regards.
Jay. -
Thank you very much. Your profile’s update is much appreciated.
-
Hello Gastone, lets see if you can help me with this issue.
I bought a Hotas Warthog a few days ago and I downloaded Morphine’s profile for the latest version TARGET from this link: https://www.dropbox.com/sh/66rd8borl…h322Vw6ba?dl=0
When I was going to try it out I had an issue:
I loaded and started the *.tmc file in the Target scrip editor then I loaded the profile *.key on the BMS 4.33 setup and when I tested it to see how the buttons where assigned they didn’t show up like they did on the Hotas images that were provided with the profile.
For example, when I press the “2” button it shows that I press the number “34”, I press the number “3” and it shows “36” and so on with many others.After that, I checked again how the buttons are assigned on the Device Analyzer and it showed up they were assigned correctly when I tested them.
I would really appreciate if you could help me out since I don’t have any more options to try out.
Thanks in advance.