Morphine's Profile
-
“Just change the name of SimRadar to do nothing. That somehow sneaked in over all the changes. I’m not even sure it’s a valid call back, so changing it wont effect anything. You’re just telling the sim, when in shifted state the paddle doesn’t do anything.”
Hi Gastone.
Thanks for your answer. Gonna give it a try after work. I’ll let you know how it goes.
Just to make sure; after changing the “SimRadar…258…” line to “SimDoNothing…258…”, do I still need to swap it with the “SimHotasPinkyShift…259…” line or leave it as it is?
I’m asking cause that’s how I understand it when reading the instructions from post 215."2. Change the following lines:
Pinky/S3 (Win DX3 = BMS DX2+256 = BMS DX258)
SimHotasPinkyShift 258 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimDoNothing 259 -1 -2 0 0x0 0
To:
Pinky/S3 (Win DX3 = BMS DX2+256 = BMS DX258)
SimDoNothing 258 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimHotasPinkyShift 259 -1 -2 0 0x0 0"
Thanks for your attention and help Gastone.
-
“Just change the name of SimRadar to do nothing. That somehow sneaked in over all the changes. I’m not even sure it’s a valid call back, so changing it wont effect anything. You’re just telling the sim, when in shifted state the paddle doesn’t do anything.”
Hi Gastone.
Thanks for your answer. Gonna give it a try after work. I’ll let you know how it goes.
Just to make sure; after changing the “SimRadar…258…” line to “SimDoNothing…258…”, do I still need to swap it with the “SimHotasPinkyShift…259…” line or leave it as it is?
I’m asking cause that’s how I understand it when reading the instructions from post 215."2. Change the following lines:
Pinky/S3 (Win DX3 = BMS DX2+256 = BMS DX258)
SimHotasPinkyShift 258 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimDoNothing 259 -1 -2 0 0x0 0
To:
Pinky/S3 (Win DX3 = BMS DX2+256 = BMS DX258)
SimDoNothing 258 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimHotasPinkyShift 259 -1 -2 0 0x0 0"
Thanks for your attention and help Gastone.
I just made a Keyfile and target script to do what you wanted. Tested it and works along with all the shifting functions. Just an fyi this totally swaps the function of the Paddle and pinky switch. So the AP disconnect feature is now on the pinkie button and vice versa.
You can download it from the dropbox here, just run the target script and load the keyfile in game.
https://www.dropbox.com/sh/ok1rydgqzz04qc3/AAA5zuKPALgU-6r5830IMg1ma?dl=0 -
I just made a Keyfile and target script to do what you wanted. Tested it and works along with all the shifting functions. Just an fyi this totally swaps the function of the Paddle and pinky switch. So the AP disconnect feature is now on the pinkie button and vice versa.
You can download it from the dropbox here, just run the target script and load the keyfile in game.
https://www.dropbox.com/sh/ok1rydgqzz04qc3/AAA5zuKPALgU-6r5830IMg1ma?dl=0Hello again Gastone.
Thank you so much for taking the time to modify the Script and file.
It’s working perfect but when I load the script my Thrustmaster Rudder pedal switches off.
I’ve noticed that when Target is loading the script, the green light on my rudder connector turns off.
When I restart the computer, the green light turns on but when I again load the Target script, the line turns off again.
In my other posts, I forgot to mention the fact that I use Rudder pedals and I’m aware that you have 2 separate profiles; with/without pedals. I’ve been using the latest profile, in other words, not the “Legacy” one.
Could this be the problem?
I can’t thank you enough for your assistance Gastone.
Kind Regards.
J -
I saw this issue in one of the other threads, Mud’s profile. Here is a snip from it;
_The issue has to do with the limit of axes that can be in a TM virtual device. You need to add
Configure(&TFRPRudder, MODE_EXCLUDED) ;
to the profile to get them to be excluded from the virtual device, then BMS will recognize them as their own controller._
See if that helps.
-
Hello again Gastone.
Thank you so much for taking the time to modify the Script and file.
It’s working perfect but when I load the script my Thrustmaster Rudder pedal switches off.
I’ve noticed that when Target is loading the script, the green light on my rudder connector turns off.
When I restart the computer, the green light turns on but when I again load the Target script, the line turns off again.
In my other posts, I forgot to mention the fact that I use Rudder pedals and I’m aware that you have 2 separate profiles; with/without pedals. I’ve been using the latest profile, in other words, not the “Legacy” one.
Could this be the problem?
I can’t thank you enough for your assistance Gastone.
Kind Regards.
JThat’s my bad. I based the the target script off the legacy version. Updated the file to reflect the current build and dropbox. Please feel free to re-download.
-
I saw this issue in one of the other threads, Mud’s profile. Here is a snip from it;
_The issue has to do with the limit of axes that can be in a TM virtual device. You need to add
Configure(&TFRPRudder, MODE_EXCLUDED) ;
to the profile to get them to be excluded from the virtual device, then BMS will recognize them as their own controller._
See if that helps.
Thanks Sarge.
I’m afraid that I’m a bit Newbie with the Target script so could you show me the exact place in the Script where I need to add that line?
I’ve also tried the original profile to see if the Pedals work and they work fine.
Thanks. -
That’s my bad. I based the the target script off the legacy version. Updated the file to reflect the current build and dropbox. Please feel free to re-download.
Hello once again Gastone.
Great news. New updated “Paddle” profile works perfect now.
Rudder pedals up and running again.
As I already stated in a previous post, this profile is the best one IMO, and even though I got used to the “Pinky” shift button I always felt that when pressing it, I was using more force than required.
Plus my hand sometimes ended in an awkward position.
This way, I only have to worry about recentering the Trackir once in a while and it’s no bother with the “Pinky”
Thanks once again for your time and patience.
Yours gratefully.
J. -
Thanks Sarge.
I’m afraid that I’m a bit Newbie with the Target script so could you show me the exact place in the Script where I need to add that line?
I’ve also tried the original profile to see if the Pedals work and they work fine.
Thanks.Me to, I’m really lost when working with TARGET script. I just remembered reading something about it in another thread. Here is a link to the first post about it;
https://www.benchmarksims.org/forum/showthread.php?8844-Mud-s-Profile&p=413282&viewfull=1#post413282There are a few follow up posts which further explain.
-
Me to, I’m really lost when working with TARGET script. I just remembered reading something about it in another thread. Here is a link to the first post about it;
https://www.benchmarksims.org/forum/showthread.php?8844-Mud-s-Profile&p=413282&viewfull=1#post413282There are a few follow up posts which further explain.
Thanks for the link although Gastone fixed my Pedals issue. Was using the “Legacy” profile instead of the proper one.
That’s why my Pedals weren’t being recognised by the programme.
Thanks once again Sarge. -
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=0Thanks for your work!
-
Running script: C:\Users\USER\Desktop\Warthog_BMS_Full_4.tmc
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Script stopped!Runtime Error: Symbol not found: TWCSThrottle in main ( line 11 in Warthog_BMS_Full_4.tmc )
-
Running script: C:\Users\USER\Desktop\Warthog_BMS_Full_4.tmc
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Script stopped!Runtime Error: Symbol not found: TWCSThrottle in main ( line 11 in Warthog_BMS_Full_4.tmc )
If on line 11 it says:
Configure(&TWCSThrottle, MODE_EXCLUDED);
then disable that line like so:
//Configure(&TWCSThrottle, MODE_EXCLUDED);
And do that for any other lines similar to that one if they cause that error.
Mud
-
Running script: C:\Users\USER\Desktop\Warthog_BMS_Full_4.tmc
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Script stopped!Runtime Error: Symbol not found: TWCSThrottle in main ( line 11 in Warthog_BMS_Full_4.tmc )
I had the exact same problem, downloaded a newer Target software (3.x, I had 2.x before), problem gone. Which version do you use?
-
I had the exact same problem, downloaded a newer Target software (3.x, I had 2.x before), problem gone. Which version do you use?
I provided 2 versions of the script and profile, one for legacy builds of target and one for the current. I’ll repost those links again.
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/4l2j2sbbk…vr7bi5bia?dl=0 -
above link for the latest version is dead.
Also, I sometimes experience TARGET SCript editor crashes upon stopping the script.
My computer then still thinks it’s seeing the combined hotas. Also, joystick input is then not recognized.
A system restart solvs the issue, but not always. -
The links work below:
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=0For me, the profiles in TARGET always worked flawlessly until I downloaded the Latest Version, and after my upgrading TARGET again work flawlessly, so Thank you very much, Morphine and Gastone!
-
above link for the latest version is dead.
Also, I sometimes experience TARGET SCript editor crashes upon stopping the script.
My computer then still thinks it’s seeing the combined hotas. Also, joystick input is then not recognized.
A system restart solvs the issue, but not always.I fixed the link above and will post here again too.
The script editor crashing ect, is a problem with windows. If u installed the newest version of target without uninstalling all of the thrustmaster software and drivers then windows will fail to re enumerate the joystick when the script stops. Even after the clean install, you must be sure to run target as an administrator. I’m pretty sure this was broken in the latest windows update. Are you running windows 10?
Profile for latest version of Target.
https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0 -
I fixed the link above and will post here again too.
The script editor crashing ect, is a problem with windows. If u installed the newest version of target without uninstalling all of the thrustmaster software and drivers then windows will fail to re enumerate the joystick when the script stops. Even after the clean install, you must be sure to run target as an administrator. I’m pretty sure this was broken in the latest windows update. Are you running windows 10?
Profile for latest version of Target.
https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0I have the exact same problem and yes I’m running Windows 10… Guess I’m going to have in uninstall everything and start over.
-
Morphine profile and Vac issue:
Hello, I am trying to use the Mic press button that provides F11 as an output for talking to VAC. I looked at the profile and wanted modify Morphine’s profile and to replace the Micpress pulse+f11 by press+f11 or hold+f11 but it doesn’t work.
Sorry to be a beginner in term of programming but could someone help ? My concept is simple: When I press the button and hold it, VAC would listen, when I release the button, it would stop listen
thank you in advance for your help
best,
Cobra -
IIRC you use the “Down” and “Up” commands to make a key press stick.
You need to have both, the “Down” will cause a keypress, the “Up” will release it. Without the “Up” the key is stuck.Edit:
Actually all you have to do is remove the PULSE+ in front of F11 and it will function like you want. Shift layer will still pulse F12.
MapKeyIO(&Throttle, MSP, PULSE+F12, F11);