Morphine's Profile
-
Nice idea but unfortunately that is beyond my programming skill level as you would need to be able to capture the SB position in the game and send it back to the TARGET software. The LED solution I implemented for the throttle position just uses info from the physical position of the throttles.
Perhaps one of the other smarter programmers around here might try to implement your idea.
Yeah, I can imagine that it is hard(or impossible) to monitor the (exact) SB position ingame and send it back to the TARGET software.
-
Morphine, I can’t get PSKeys to work. Could you please post all your keyboard functions.
-
Fuzzysham sent me a PM with a problem he is having that I think others are also having. I’ve posted his PM here and my response so all can address their similar issue.
Unfortunately, your device is being recognized as the 4th DirectX device attached (when TARGET is running) rather than the 1st. First thing I would try is to unplug all other USB Game devices, reboot, and then plug your WH Joystick directly into a Motherboard USB port (the ones on the back of your computer near your Ethernet port, etc.) and not to any external USB hub or other front or back USB ports on your computer (as these are also considered hubs). Reboot your computer and do the same with the WH Throttle putting it right next to the Joystick. Reboot again. Now add your other devices to any other USB ports and one last reboot. Now if you got lucky, this may have re-ordered your devices so that the WH Joystick is now Device 0 and the Throttle is Device 1. You can see what the Device order is by going to using DxDiag.exe. To start DxDiag, go to your Start Menu and in the Search box at the bottom, type DxDiag and it should appear in the list above and you can launch it. The last tab called INPUT will list all your DirectX (DirectInput) devices attached. Under the column CONTROLLER ID, it will list the ID number and thus the order they appear to games (remember ID# 0 is the first device and so on). So if our trick worked above, the Joystick is ID# 0 and the Throttle is ID# 1. When the TARGET script is run the Thrustmaster Combined device should now get Controller ID# 0 in DxDiag.
If that didn’t work then you will need to edit the Warthog_DX.key file (with Notepad++) and the TARGET script (with Script Editor). In the keyfile you only need to edit the Joystick mappings. I’ve attached a spreadsheet that shows how the numbers are calculated. Since your Thrustmaster combined device is Device #4 then you need to add 128 to every number from 0-32. For example:
TG1 (Win DX1 = BMS DX0)
SimTriggerFirstDetent 0 -1 -2 0 0x0 0
Would be changed to:
TG1 (Win DX1 = BMS DX0)
SimTriggerFirstDetent 128 -1 -2 0 0x0 0
Same for the shifted layer buttons as well:
TG1 (Win DX1 = BMS DX0+256 = BMS DX256)
SimDoNothing 256 -1 -2 0 0x0 0
Would be changed to:
TG1 (Win DX1 = BMS DX0+256 = BMS DX256)
SimDoNothing 384 -1 -2 0 0x0 0
In the TARGET script, anywhere there is a DX# button, you will also need to add 128 to that number. For example:
//Paddle/S4
MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX4, 500));Would be changed to:
//Paddle/S4
MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX132, 500));If you have other DirectX devices like the TM MFD’s attached you will probably have the same problem and have to edit the key file to fix their numbers as well using the same process. However, you may need to experiment with the numbering as when you run TARGET the MFD’s don’t move to DirectX ID 1 & 2 in DxDiag, but that is how the game sees them and how the keyfile controls them. You may also need to experiment with your numbering for your DirectX devices as it may also have some differences in how the game sees it versus how DxDiag reports it. A quick test is to go into the Controller Setup screen in the game (with TARGET script running) and push the first trigger button on the Joystick (just to the first detent) and see what the game reports that button number to be (e.g. 128 ). The same can be done with the MFD’s but use the upper far left button. You will then you will know where to start your numbering for each device.
Hope that helps and good luck.
Okay…. I’ve tried this as a solution to the problem I was having however when editing the target script to use the now correct DX buttons I keep getting runtime errors saying that the key hasn’t been defined, not sure if I’m missing something or if I’m just doing it wrong, but this does mean I can’t get my shifted layer to work.
-
Hello. Morphine,thank you for your profile. It was a great base for mine I learned a lot.
Here I propose some LED works that are pretty useful.
- Initialize LEDs off and a Low Throttle Light Intensity.
- LED 4 Lights on MIL thrust and LED4+5 Light on Afterburner
- LED 1 Lights ON when shift key is active.
- Control backlight on Throttle with Shift+ Left Engine Operation “IGN Up”
NOTE: I changed Shift to Paddle (S4) when Held, and added TIR Center when pulsed.
1) Initialize LEDs off and a Low Throttle Light Intensity.
//LED WORKS: ALL OFF AND INTENSITY LOW ActKey(PULSE+KEYON+LED(&Throttle, LED_INTENSITY, 49)); // LED INTENSITY INITIALIZE ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //Initialize LED1 off ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //Initialize LED2 off ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3)); //Initialize LED3 off ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //Initialize LED4 off ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)); //Initialize LED5 off
2) LED 4 Lights on MIL thrust and LED4+5 Light on Afterburner (based on Morphine’s)
I chose these LEDS (4 for MIL and 4+5 for AB) because they are the only ones you can see when Throttle is in that position.//LED Throttle Position Indicator; LED 1 - MIL Power; LED 1-5 AB KeyAxis(&Throttle, THR_LEFT, 0, AXMAP2( LIST( 0, 65, 75 ), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED5)) ));
3) LED 1 Lights ON when shift key is active.
//Paddle/S4 MapKey(&Joystick, S4, TEMPO //Tempo for short and long ( PULSE + L_CTL + L_ALT + + L_SHIFT + F1, //Reset FaceTrackNoIR CHAIN (LED(&Throttle, LED_ONOFF, LED_CURRENT + LED1), DX4) //long function: LED1 ON + Shift ,500 ) ); MapKeyR(&Joystick, S4, LED(&Throttle, LED_ONOFF, LED_CURRENT - LED1)); //LED1 off on Release
4) Control backlight on Throttle with SHIFTED + Left Engine Operation “IGN Up”
//Engine Operate Left MapKeyIO(&Throttle, EOLIGN, SEQ( LED(&Throttle, LED_INTENSITY, 129), LED(&Throttle, LED_INTENSITY, 172), LED(&Throttle, LED_INTENSITY, 215), LED(&Throttle, LED_INTENSITY, 1), LED(&Throttle, LED_INTENSITY, 43), LED(&Throttle, LED_INTENSITY, 86) ), PULSE + L_SHIFT + 'j'); //MapKey(&Throttle, EOLIGN, PULSE+L_SHIFT+'j'); // original MapKey(&Throttle, EOLNORM, PULSE+L_SHIFT+L_CTL+'j'); MapKey(&Throttle, EOLMOTOR, PULSE+L_SHIFT+L_ALT+'j');
4B) EXTRA- in the same order of ideas, I made the SHIFTED -> “RIGHT eng oper IGN” to change HUD color (something I use frequent)
//Engine Operate Right MapKeyIO(&Throttle, EORIGN, L_CTL + L_ALT + L_SHIFT + 'c' , PULSE + L_SHIFT + 'j'); //MapKey(&Throttle, EORIGN, PULSE+L_SHIFT+'j'); //original MapKey(&Throttle, EORNORM, 0); MapKey(&Throttle, EORMOTOR, DX26); ç
I hope with these ideas I can return to the community. cheers!
-
Hello. Morphine,thank you for your profile. It was a great base for mine I learned a lot.
Here I propose some LED works that are pretty useful.
- Initialize LEDs off and a Low Throttle Light Intensity.
- LED 4 Lights on MIL thrust and LED4+5 Light on Afterburner
- LED 1 Lights ON when shift key is active.
- Control backlight on Throttle with Shift+ Left Engine Operation “IGN Up”
NOTE: I changed Shift to Paddle (S4) when Held, and added TIR Center when pulsed.
Cool stuff and thanks for sharing!
-
I was wondering if someone can help me out with this. I’ve tried everything but I can’t figure it out yet.
What I’m trying to do is assign my Shift Coolie Up as F10 (altimeter increase) and Shift Coolie Down as F9 (altimeter decrease). Shift Coolie Right will be F6 (course increase) and Shift Coolie Left will be F5 (course decrease). When I hold down the Coolie switch, I want the program to keep pulsing (not hold) the corresponding key-press (F9 or F10 or F6 or F5) until I release the Coolie switch. I’ve tried REXEC commands but I guess I’m just not getting it. Any help would be great.
Thanks!
-
Hi Morphine
I used your profile for a long time with my old Win7 system. No problems at all.
Recently I bought a new system with Win8 and my Windows recognizes my Warthog as Gamecontroller (1) instead of (0).
Now the hole Keyfile is wrong and useless.I tried to set the warthog to (0) but with no luck at all.
Maybe I am doing something wrong.Is it possible to adjust the keyfile to match the warthog as gamecontroller (1)?
Or how can I set my warthog as controller (0)?Phil
-
Hi Morphine
I used your profile for a long time with my old Win7 system. No problems at all.
Recently I bought a new system with Win8 and my Windows recognizes my Warthog as Gamecontroller (1) instead of (0).
Now the hole Keyfile is wrong and useless.I tried to set the warthog to (0) but with no luck at all.
Maybe I am doing something wrong.Is it possible to adjust the keyfile to match the warthog as gamecontroller (1)?
Or how can I set my warthog as controller (0)?Phil
Does it mean this profile is not working with Windows 8.1 ? I am installing Falcon 4.32 and I wanted to use this wonderful profil with my clean installation.
Thanks for your answer.
PS : Why are you using Target script instead of classical target software program ? It will be easier for us to modify it instead of using script language.
-
It does work without problems as long as the warthog is recognised in Win8 as game controller (0).
-
It does work without problems as long as the warthog is recognised in Win8 as game controller (0).
Where are you seeing the game controller number ?
-
Hi Morphine
I used your profile for a long time with my old Win7 system. No problems at all.
Recently I bought a new system with Win8 and my Windows recognizes my Warthog as Gamecontroller (1) instead of (0).
Now the hole Keyfile is wrong and useless.I tried to set the warthog to (0) but with no luck at all.
Maybe I am doing something wrong.Is it possible to adjust the keyfile to match the warthog as gamecontroller (1)?
Or how can I set my warthog as controller (0)?What device is in the Controller 0 spot?
I’d try unplugging all other USB game controllers and plugging in the Warthog controller into the USB ports attached to the motherboard. Then run the script and see if Thrustmaster Combined combined now appears as controller 0. If it does, then you can plug in any other game controllers and reboot, run the script and see if it stays at 0.
Assuming you can’t get the Thrustmaster Combined controller to show up as Controller 0, then you are going to have to renumber the assignments in the key file using a text editor. See this post for an explanation on how to do that. https://www.benchmarksims.org/forum/showthread.php?8147-Morphine-s-Profile&p=202779&viewfull=1#post202779
-
Where are you seeing the game controller number ?
In the BMS Setup-Page, Axis Control.
The number in brackets after “Thrustmaster Combined”.
Sorry, I can’t explain it any futher because I am not at my flight pc at the moment.
Have a look in the pictures comming with Morphines profile as well. -
What device is in the Controller 0 spot?
My Saitek Rudder Pedals are set to Controller 0.
Thanks for your advises, l will give them a try later.
-
Thank you very much fot this information Takamba.
-
Where are you seeing the game controller number ?
You can also get additional info about the controllers by running the dxdiag.exe utility.
-
I’d try unplugging all other USB game controllers and plugging in the Warthog controller into the USB ports attached to the motherboard. Then run the script and see if Thrustmaster Combined combined now appears as controller 0. If it does, then you can plug in any other game controllers and reboot, run the script and see if it stays at 0.
That helped.
My Thrustmaster Combined is now set as controller 0.Thanks Morphine
-
Hi,
I installed your profile (.key file) and the Target file through the script editor (load it and run it without compiling it) but I just only have the right MFD working. When I am pressing on buttons of my left MFD, nothing happens. Do you have any idea about resolving this issue ?
Thank you very much.
-
Thanks for your hard work Morphine.
I tried to use the LED functionality for MIL power and AB By placing your script between the lines as directed. It didn’t work for me. I am not the most qualified to be doing this sort of stuff but I figured it was easy enough to cut and paste your script between 2 lines. One of the lines in your script scrolls way off to the right, it didn’t look like the rest. Is that right? Any help would be awesome. -
Hi,
I installed your profile (.key file) and the Target file through the script editor (load it and run it without compiling it) but I just only have the right MFD working. When I am pressing on buttons of my left MFD, nothing happens. Do you have any idea about resolving this issue ?
Thank you very much.
I also have another problem : For example the gun trigger is not working whereas trim button on the joystick is ok. It’s like tthere are some buttons working and some others not.
I followed every step of Morphines’s tutorial.
Thanks for your help.
If it can help, my entries running Dxdiag. On BMS,Warthog is seen as “0” device :
-
Morphine, is there a way for me to put my TeamSpeak talk button on the throttle or joystick?