Morphine's Profile
-
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); -
How can i make the T Rudder work with this script?
-
How can i make the T Rudder work with this script?
Not sure what you mean by “work with”, but make sure you are using the latest version in post #619 on the previous page and should be good.
-
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);Hi TxMtb,
Thank you for your help but unfortunately, it doesn’t work. This is the last line
//Mic Switch
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27));
MapKeyIO(&Throttle, MSR, CHAIN(PULSE+‘q’, D(), PULSE+‘q’, D(), PULSE+‘2’), DX28);
MapKeyIO(&Throttle, MSD, DX29, CHAIN( SCRLCK, DX29));
MapKeyIO(&Throttle, MSL, CHAIN(PULSE+‘q’, D(), PULSE+‘q’, D(), PULSE+‘1’), DX30);
MapKeyIO(&Throttle, MSP, F11); -
Hi TxMtb,
Thank you for your help but unfortunately, it doesn’t work. This is the last line
//Mic Switch
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27));
MapKeyIO(&Throttle, MSR, CHAIN(PULSE+‘q’, D(), PULSE+‘q’, D(), PULSE+‘2’), DX28);
MapKeyIO(&Throttle, MSD, DX29, CHAIN( SCRLCK, DX29));
MapKeyIO(&Throttle, MSL, CHAIN(PULSE+‘q’, D(), PULSE+‘q’, D(), PULSE+‘1’), DX30);
MapKeyIO(&Throttle, MSP, F11);If set like the last one that way above, it will only output the F11 when holding the shift button, not the regular.
The MapkeyIO command is looking for 2 variables. So syntax would look like MapKeyIO(&Throttle, MSP, x, y); where x = shifted layer, and y = unshifted layer.
So for the MSL button in your code above, it would output q then q, then 1 when shifted, and DX30 button when unshifted.Try MapKeyIO(&Throttle, MSP, F11, F11); and it should output F11 on both the shifted and regular layers.
This is kinda redundant though as MapKey(&Throttle, MSP, F11); would do the same thing. Notice it’s MapKey and not MapKeyIO. It only looks for 1 variable and doesn’t use a shifted layer so would always output F11. -
If set like the last one that way above, it will only output the F11 when holding the shift button, not the regular.
The MapkeyIO command is looking for 2 variables. So syntax would look like MapKeyIO(&Throttle, MSP, x, y); where x = shifted layer, and y = unshifted layer.
So for the MSL button in your code above, it would output q then q, then 1 when shifted, and DX30 button when unshifted.Try MapKeyIO(&Throttle, MSP, F11, F11); and it should output F11 on both the shifted and regular layers.
This is kinda redundant though as MapKey(&Throttle, MSP, F11); would do the same thing. Notice it’s MapKey and not MapKeyIO. It only looks for 1 variable and doesn’t use a shifted layer so would always output F11.Thanks a lot TxMtb, it works perfectly.
Have a good night
-
Wanted to give much thanks to Gastone for helping me find a good link. Right under my nose, well I do lose my glasses sometime
only to find them on top of my head. It takes Guts to get old. Will someone please tell me how to use the joystick button S3 or S4 paddle in Morphine’s
profile to use or make double commands.God Bless
-
Wanted to give much thanks to Gastone for helping me find a good link. Right under my nose, well I do lose my glasses sometime
only to find them on top of my head. It takes Guts to get old. Will someone please tell me how to use the joystick button S3 or S4 paddle in Morphine’s
profile to use or make double commands.God Bless
To use the shift state press and hold the shift button then press the button you wish to use. With the default profile you use the nose wheel steering button. For example if you want to increase the HSD range you press and hold nose wheel steering and then hit DMS up.
If you’re talking about adding shifted commands you’re getting into directx shifting. The Key file manual covers this topic in detail. The short of it is, when you shift your creating a virtual joystick button whose value is the base joystick number + 256. So if you Shift button 1 the sim reads button 257. Since you can’t assign very high joystick buttons in game, the only way to assign a function to them is to edit the key file manually. Which you’ll want to consult the Keyfile manual for instructions.
-
This post is deleted! -
To use the shift state press and hold the “keyboard” shift button an press and hold nose wheel steering and then hit
DMS joystick button you wish to use. I have tried it both ways the shift button will cause the black out screen.For example if you want to increase the HSD range you press and hold nose wheel steering and then hit DMS up. Will simply not work with in-game or target for me…
Thanks but cannot get target gui to do anything but mess up with Morphine’s or Mud profiles. Have to use in game setup and even then my 8 way on joystick and throttle replicate each other. Not sure why BMS is so unstable for me.
-
Have you tried the updated version of morphine’s profile? The profile he posted hasn’t worked since 4.33, the updated one does. You can download it here. https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0
You have to load the keyfile in game too. Make sure you edit your devicesorting.txt so that the thrustmaster combine is at the top of the list too. it’s located in the install under User -> config. -
can’t we just sticky a new thread with the correct way of setting the controls written in the first post. it’s been a long long read now and i still can’t get my t-rudder work. i’m really close to give up completely and uninstall.
-
can’t we just sticky a new thread with the correct way of setting the controls written in the first post. it’s been a long long read now and i still can’t get my t-rudder work. i’m really close to give up completely and uninstall.
You need the latest version of the profile and the newest version of target for the t-pedals to work. You can get the profile from here https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0. Older versions of target won’t work with the t-pedals; as they can’t be excluded from the script.
The big issue with the profile is that is no longer maintained by Morphine. So updates and the latest help tend to be at the bottom of the thread.
-
Is it possible that the air brake (Speedbrake) does not work? With me nothing happens on the button.