Morphine's Profile
-
TIP: How to change the SHIFT function to the Paddle from the S3 button.
You need to make changes in both the script and the key file. Changed text in Red.
Script Changes:
1. Change: SetShiftButton(&Joystick, S3);
to: SetShiftButton(&Joystick, S4);2. Change: MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX4, 750));
to: MapKey(&Joystick, S3, TEMPO(PULSE+F12, DX3, 750));Key file Changes:
1. Change the following lines:
Pinky/S3 (Win DX3 = BMS DX2)
SimHotasPinkyShift 2 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimAPOverride 3 -1 -2 0 0x0 0
To:
Pinky/S3 (Win DX3 = BMS DX2)
SimAPOverride 2 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimHotasPinkyShift 3 -1 -2 0 0x0 0
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
-
The only thing that I would like to change is have the lights on the throttle off when not in burner and then have the lights turn on when I hit the dead zone of the throttle.
Challenge Accepted!
This is also something I’ve wanted to do for a while as well. Add the code below to the TARGET Script and the 1st (Top) LED will come on once you are in the deadzone and the remaining lights will come on once you leave the deadzone and activate the AB. In your controller setup screen set the AB detent when the first light is on and you will be good to go.
Add the code below between the following two lines in the TARGET Script:
SetShiftButton(&Joystick, S3);////////////////// AXIS CONTROLS //////////////////////////////
////////////////// LED CONTROLS ////////////////////////////// //initialize LED status all "OFF" ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //set LED 1 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //set LED 2 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3)); //set LED 3 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //set LED 4 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)); //set LED 5 OFF //LED Throttle Position Indicator; LED 1 - MIL Power; LED 1-5 AB KeyAxis(&Throttle, THR_LEFT, 0, AXMAP2( LIST( 0, 65, 75 ), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED5)) ));
If you’ve changed the deadzone to something other than 65 - 75, you will need to adjust the vaules in the text “AXMAP2( LIST( 0, 65, 75 )” accordingly.
-
Thank you, already contacted TM and wait for response, I tried settings about deadzone and saturation, but its the same thing, it going all way down to 5 miles scan in the corner if Y axis is inverted or all the way up in 160 miles scan when Y axis is normal. The strange about that is in device analyzer going from 512 to 0 and 1023 and after calibration, even if the center is wrong must work with this wrong center as zero position and don’t move without even press the cursor enable function. Anyway thank you for your interest and I want to apologize to Morphine for my offtopic posts.
Edit: Because I will not make it right, can you explain me please how to change the shift to paddle switch and how to assign the cursor function to TRIM switch and make the trim function shifted?
Thanks again
TigerShark.Some questions TigerShark.
Are you saying the Cursor Y axis doesn’t move uncontrollably in the TM Device Analyzer?
And it does begin moving uncontrollably (in the TM Device Analyzer) if you push the Cursor In (cursor enable)?
Are you running these tests with the script running?
Does the cursor work properly in another flight sim like DCS A-10C? -
TIP: Make the Trim Hat control views on the UNSHIFTED layer and Trim Control on the SHIFTED layer.
Near the bottom of the key file, replace the text:
AFElevatorTrimUp 0 -1 -3 0 0x0 0
AFAileronTrimRight 0 -1 -3 1 0x0 0
AFAileronTrimRight 0 -1 -3 2 0x0 0
AFAileronTrimRight 0 -1 -3 3 0x0 0
AFElevatorTrimDown 0 -1 -3 4 0x0 0
AFAileronTrimLeft 0 -1 -3 5 0x0 0
AFAileronTrimLeft 0 -1 -3 6 0x0 0
AFAileronTrimLeft 0 -1 -3 7 0x0 0With the text:
AFElevatorTrimUp 2 -1 -3 0 0x0 0
SimDoNothing 2 -1 -3 1 0x0 0
AFAileronTrimRight 2 -1 -3 2 0x0 0
SimDoNothing 2 -1 -3 3 0x0 0
AFElevatorTrimDown 2 -1 -3 4 0x0 0
SimDoNothing 2 -1 -3 5 0x0 0
AFAileronTrimLeft 2 -1 -3 6 0x0 0
SimDoNothing 2 -1 -3 7 0x0 0 -
Challenge Accepted!
This is also something I’ve wanted to do for a while as well. Add the code below to the TARGET Script and the 1st (Top) LED will come on once you are in the deadzone and the remaining lights will come on once you leave the deadzone and activate the AB. In your controller setup screen set the AB detent when the first light is on and you will be good to go.
Add the code below between the following two lines in the TARGET Script:
SetShiftButton(&Joystick, S3);////////////////// AXIS CONTROLS //////////////////////////////
////////////////// LED CONTROLS ////////////////////////////// //initialize LED status all "OFF" ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //set LED 1 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //set LED 2 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3)); //set LED 3 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //set LED 4 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)); //set LED 5 OFF //LED Throttle Position Indicator; LED 1 - MIL Power; LED 1-5 AB KeyAxis(&Throttle, THR_LEFT, 0, AXMAP2( LIST( 0, 65, 75 ), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED5)) ));
If you’ve changed the deadzone to something other than 65 - 75, you will need to adjust the vaules in the text “AXMAP2( LIST( 0, 65, 75 )” accordingly.
That is fantastic! Thanks Morphine!
-
TIP: How to change the SHIFT function to the Paddle from the S3 button.
You need to make changes in both the script and the key file. Changed text in Red.
Script Changes:
1. Change: SetShiftButton(&Joystick, S3);
to: SetShiftButton(&Joystick, S4);2. Change: MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX4, 750));
to: MapKey(&Joystick, S3, TEMPO(PULSE+F12, DX3, 750));Key file Changes:
1. Change the following lines:
Pinky/S3 (Win DX3 = BMS DX2)
SimHotasPinkyShift 2 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimAPOverride 3 -1 -2 0 0x0 0
To:
Pinky/S3 (Win DX3 = BMS DX2)
SimAPOverride 2 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimHotasPinkyShift 3 -1 -2 0 0x0 0
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
Some questions TigerShark.
Are you saying the Cursor Y axis doesn’t move uncontrollably in the TM Device Analyzer?
And it does begin moving uncontrollably (in the TM Device Analyzer) if you push the Cursor In (cursor enable)?
Are you running these tests with the script running?
Does the cursor work properly in another flight sim like DCS A-10C?TIP: Make the Trim Hat control views on the UNSHIFTED layer and Trim Control on the SHIFTED layer.
Neat the bottom of the key file, replace the text:
AFElevatorTrimUp 0 -1 -3 0 0x0 0
AFAileronTrimRight 0 -1 -3 1 0x0 0
AFAileronTrimRight 0 -1 -3 2 0x0 0
AFAileronTrimRight 0 -1 -3 3 0x0 0
AFElevatorTrimDown 0 -1 -3 4 0x0 0
AFAileronTrimLeft 0 -1 -3 5 0x0 0
AFAileronTrimLeft 0 -1 -3 6 0x0 0
AFAileronTrimLeft 0 -1 -3 7 0x0 0With the text:
AFElevatorTrimUp 2 -1 -3 0 0x0 0
SimDoNothing 2 -1 -3 1 0x0 0
AFAileronTrimRight 2 -1 -3 2 0x0 0
SimDoNothing 2 -1 -3 3 0x0 0
AFElevatorTrimDown 2 -1 -3 4 0x0 0
SimDoNothing 2 -1 -3 5 0x0 0
AFAileronTrimLeft 2 -1 -3 6 0x0 0
SimDoNothing 2 -1 -3 7 0x0 0I have done it already with a little reading ;)! Thanks for the tip with the TRIM hat, maybe I will try it. Currently I have mapped cursor on coolie throttle switch. As of your questions the slew hat(cursor) in TM Device Analyzer can take value from -1023 to 1023. When I’m testing with the script running goes from zero to zero and from 1023 to 1023 but when I release the hat, always return to 0,0 values. In the sim now (both BMS and FF) configuring the axes as are in the photo that you provide with the profile, but without even press the enable cursor button, the cursor start to slide up if the Y axis is normal and down if the Y is inverted. As of that the cursor make the Radar to stay at 5 miles when Y is inverted or 160 miles when the Y is normal. Its very weird, because the ministick not seem to have center at all in the sim( it can start travel if I move the Warthog Stick without mess with throttle or ministick) but in analyzer always return to 0,0.
TM responded to check the internal cables of throttle but didn’t find something weird.Thanks again and sorry if bothered you with the PM
TigerShark
-
As of your questions the slew hat(cursor) in TM Device Analyzer can take value from -1023 to 1023. When I’m testing with the script running goes from zero to zero and from 1023 to 1023 but when I release the hat, always return to 0,0 values.
That is the normal and expected behavior. However, if you look at the Device Analyzer, you will notice that the LEFT panel reports the raw values for the Hardware (the -1023 to 1023 for the Throttle X & Y axes) and the RIGHT panel reports the values for the virtual Thrustmaster Combined device. The Throttle X & Y cursor axes are named Rx & Ry axes. These values range from -32767 to 32767. Now if you move the cursors (with the Script RUNNING) you should see the Rx & Ry axes moving in the Right panel in addition to the throttle X & Y moving in the Left Panel. They won’t go all the way to their max Rx and Ry values because I have reduced their sensitivity but they will move. In the attached picture, I’ve highlighted the Cursor axes in both the Throttle (raw data), and the Thrustmaster Combined data. I’ve moved the cursor X & Y axes to their physical limit and the Rx and Ry have moved as well. Mine will be a little different than yours as I have reversed my Ry axis in the script so it moves in the opposite direction as the Rx.
Does your Device Analyzer show the same type of response as mine or is the cursor Ry axis moving to the limit and just staying there? If it’s moving, and staying, at the limit of the Y axis, then you have a Hardware problem. If the Y axis is behaving properly and it’s moving, and staying at the Ry limit, then there is a problem with the Script and you should re-download the script. If both the Y axis and the Ry axis are behaving properly then you have a problem in Windows or more likely in BMS. In which case, I would recommend uninstalling and re-installing BMS.
I hope that helps. Good luck.
-
That is the normal and expected behavior. However, if you look at the Device Analyzer, you will notice that the LEFT panel reports the raw values for the Hardware (the -1023 to 1023 for the Throttle X & Y axes) and the RIGHT panel reports the values for the virtual Thrustmaster Combined device. The Throttle X & Y cursor axes are named Rx & Ry axes. These values range from -32767 to 32767. Now if you move the cursors (with the Script RUNNING) you should see the Rx & Ry axes moving in the Right panel in addition to the throttle X & Y moving in the Left Panel. They won’t go all the way to their max Rx and Ry values because I have reduced their sensitivity but they will move. In the attached picture, I’ve highlighted the Cursor axes in both the Throttle (raw data), and the Thrustmaster Combined data. I’ve moved the cursor X & Y axes to their physical limit and the Rx and Ry have moved as well. Mine will be a little different than yours as I have reversed my Ry axis in the script so it moves in the opposite direction as the Rx.
Does your Device Analyzer show the same type of response as mine or is the cursor Ry axis moving to the limit and just staying there? If it’s moving, and staying, at the limit of the Y axis, then you have a Hardware problem. If the Y axis is behaving properly and it’s moving, and staying at the Ry limit, then there is a problem with the Script and you should re-download the script. If both the Y axis and the Ry axis are behaving properly then you have a problem in Windows or more likely in BMS. In which case, I would recommend uninstalling and re-installing BMS.
I hope that helps. Good luck.
Hello again here are my results according to Analyzer and your image:
As it seems there is no problem with device and already I have uninstalled BMS once after discovered the problem but this didn’t solve anything. Maybe I will uninstall TARGET and for sure I will upload a video to youtube. The Raw data becoming 0 for Rx and 0 for Ry after ministick release.
TigerShark
-
Well I’m a bit stumped. I’m assuming if you stop moving the physical cursor that both the Y axis and the Ry axis return to normal. If that’s the case then I think it’s safe to say that there is no problem with the physical device or the TARGET Script. Let’s look at how Windows is seeing/reporting the cursor. With the TARGET Script RUNNING, go to your Control Panel and select “Devices and Printers”. Right Click on the “Throttle - HOTAS Warthog” icon (which should have a little yellow triangle on the lower right corner of the icon) and select “Game controller settings”. Highlight the “Thrustmaster Combined” game controller and click the “Properties” button. On the “Test” tab, does the “Y Rotation” work properly when you move the cursor around and return to center when you stop moving it? See attached.
If that is normal then I’m really inclined to believe something is fubar with your install or there is another DX button or keystroke commanding the Y cursor to move to full deflection on the game. Look for the following text (SimCursorUp) in your keyfile and make sure they don’t have any keystrokes or DX keys programmed. It should look like below.
SimCursorDown -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor down”
SimCursorLeft -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor left”
SimCursorRight -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor right”
SimCursorUp -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor up”One other question, in the game if you switch your SOI to your HSD does the cursor move uncontrollably there as well like it does in the FCR?
-
Well I’m a bit stumped. I’m assuming if you stop moving the physical cursor that both the Y axis and the Ry axis return to normal. If that’s the case then I think it’s safe to say that there is no problem with the physical device or the TARGET Script. Let’s look at how Windows is seeing/reporting the cursor. With the TARGET Script RUNNING, go to your Control Panel and select “Devices and Printers”. Right Click on the “Throttle - HOTAS Warthog” icon (which should have a little yellow triangle on the lower right corner of the icon) and select “Game controller settings”. Highlight the “Thrustmaster Combined” game controller and click the “Properties” button. On the “Test” tab, does the “Y Rotation” work properly when you move the cursor around and return to center when you stop moving it? See attached.
If that is normal then I’m really inclined to believe something is fubar with your install or there is another DX button or keystroke commanding the Y cursor to move to full deflection on the game. Look for the following text (SimCursorUp) in your keyfile and make sure they don’t have any keystrokes or DX keys programmed. It should look like below.
SimCursorDown -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor down”
SimCursorLeft -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor left”
SimCursorRight -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor right”
SimCursorUp -1 0 0XFFFFFFFF 0 0 0 1 “RADAR-cursor up”One other question, in the game if you switch your SOI to your HSD does the cursor move uncontrollably there as well like it does in the FCR?
These was my results: , but I figured it out, I had done calibration through Windows before the calibration with the Throttle tool from TM. When calibrated with tool I had set to default settings the controller in controllers menu in Windows but as it seems nothing changed… Now with your idea of script running alongside with controller properties the reverting to defaults seem to done properly. So I tested three ways after that one in Windows controller properties that now seem right, one in Device Analyzer in TM Script editor that seem to respond right and finally in SIM under controller setup, now the X and Y axes both return to half full after cursor move. so is centered. I haven’t tried in flight yet but I will try it soon. I have modified the keyfile to assign the cursor to coolie switch but downloaded your original keyfile and I will try both ( I assume I have to revert the coolie switch in case of mapping collision with the modified profile…)
Thank you again for your valuable information and great help
TigerShark
-
I’m having an issue with the key bindings due to how windows seems to be setting up the controller after running the script, instead of getting the usual “Thrustmaster Combined (0)” listed in BMS, I now seem to have it listed as “Thrustmaster Virtual Game Controller (root)”. I did recently move my set-up to another room and thus had to disconnect everything but I hooked my rig up as it was before and am now faced with this.
I have no clue what I’m doing wrong :S
-
@TigerShark… Glad to hear you may have found the solution.
-
I’m having an issue with the key bindings due to how windows seems to be setting up the controller after running the script, instead of getting the usual “Thrustmaster Combined (0)” listed in BMS, I now seem to have it listed as “Thrustmaster Virtual Game Controller (root)”. I did recently move my set-up to another room and thus had to disconnect everything but I hooked my rig up as it was before and am now faced with this.
If just the name has changed from “Thrustmaster Combined” to “Thrustmaster Virtual Game Controller” and the functionality is still ok, then I wouldn’t worry about it. If the functionality isn’t working as before then the controller may have been renumbered and is no longer the first DirectX game controller which the profile relies on. A quick fix might be to unplug all your game controllers, joysticks, USB devices, USB hubs, etc (only mouse and keyboard) and shutdown the computer. Then plug in your Warthog to the exact same USB ports you had them plugged into previously (hopefully they were USB posts attached directly to the motherboard and they were not plugged into a hub) and restart your computer. With the TARGET Script RUNNING, go to your Control Panel and select “Devices and Printers”. Right Click on the “Throttle - HOTAS Warthog” icon (which should have a little yellow triangle on the lower right corner of the icon) and select “Game controller settings”. You should now see the “Thrustmaster Combined” game controller as the only device listed. You can now try plugging in the rest of your USB devices and restart your computer again and repeat the process above to see if the “Thrustmaster Combined” game controller is still the first device listed. If that doesn’t fix the problem you will need to note which number device is the “Thrustmaster Combined” or “Thrustmaster Virtual Game Controller” and follow the instructions in this post: https://www.benchmarksims.org/forum/showthread.php?8147-Morphine-s-Profile&p=202779&viewfull=1#post202779
-
@TigerShark… Glad to hear you may have found the solution.
Hello again, just wanted to report that after resetting Windows calibration with script running as mentioned in post #224, the problem disappeared. The cursor now stays where I move it! I’m happy that it wasn’t a hardware problem and I want to thank you once again for your great help.
TigerShark
-
seems I get no response from my Throttle at all. Seems that I get a response ont he Device analyzer but not in the sim. No throttle movement at all.
-
Morphine, I noticed you have your G13 buttons labeled like on the ICP. How or where did you get the labels?
-
Im still cant figure out why I cant get movement in my throttle. I see it in Device analyzer, it works in other flight sims, seem to be a issues inside falcon. All the other functions on the throttle work except for the movement. Can anyone help. I have set in the advance tab for throttle for warthog. HELP!
-
@ Maple
How you have set up the throttle function in Sim? If you done it as it was in the picture with the profile, here lies the problem, so put in the Throttle Axis Z Axis-Thurstmaster combined instead of Z rotation. If that don’t work check device calibration in Windows to see if the Z axis moving correctly. Personally if I had the throttle axis config as they are in the picture FlightControlTab.png in profile folder, the throttle moved once on full AB and didn’t gone back to idle. Once I set up the Z Axis in throttle axis worked normally…TigerShark
-
This post is deleted! -
GOT IT!!! THANKS TIGERSHARK!