Morphine's Profile
-
Hi Venom,
Thanks for the response.
The 3 entries for the Thrustmaster Combined are the same. However as I do not have any rudder pedal pedal installed, the references to the “Saitek Pro Flight Combat Rudder” are replaced by the Z Axis - Thrustmaster Combined (o).
By the way, which tool do you use to do your screen capturing?
Cheers,
Harm88
It was just the screenshot from Morphine’s tutorial on his homepage. I have the Warthog myself so it’s weird it doesn’t work for you.
Have you updated the drivers and firmware for both your throttle and joystick? You can do that with the target profiler program.
Also try and chose keyboard for rudder, since the Z-axis is the throttle. So I don’t understand why you use thas as rudder. -
Have it like I have it in these 3 pictures. Then I don’t see why it shouldn’t work. As long as you are sure you are running his profile with target script while you run BMS.
-
I cannot seem to get your profile to run as I would expect. For example, my Throttle does not respond when using your profile, but the game indicates that the rudder is working fine when using the de-coupled right throttle control, while no response from the left control. I have tried the usual utilities such as the Target Script Editor device analyzer and they all seem to think that the device is working ok. I always start the BMS via the script editor and I have made sure that the “BMS 4.32 - Mud.key” is in the \user\config folder. Also that this key file is loaded in the game I am sure there is something that I have missed, but not sure what.
By “trial and error”, I have had the throttle responding on “Z-Axis Thrustmaster combined (0)”. So far, all other keys seem to be working as expected, just not the throttle. Can you think of what I might have missed so far?
You should only be using the keyfile (Warthog_DX.key) that I provided as many of the mappings are controlled by that. I do not know how Mud mapped his and it may not work with my profile. The keyfiles and the scripts work together so you can’t mix and match unless you know what you are doing.
As Venom has said, you need to make sure the designations in the Advanced Options page in the Flight Control and Avionics Control tabs are the same as mine (minus the Rudder pedals and toe brakes which would be assigned to the Keyboard). Go back to the web page where you downloaded the script and look closely at the Flight Control tab and the Avionics Control tab.
The reason the Throttle is controlling the Rudders is that you have it assigned incorrectly (it’s how BMS defaults). So you should have Throttle Axis assigned to “Z Rotation - Thrustmaster Combined (0)” and Right Engine Throttle Axis assigned to “Z Axis - Thrustmaster Combined (0)”. Anything other than that is not going to work.
Also make sure you check the Reverse button on the Cursor Y axis.
-
Have it like I have it in these 3 pictures. Then I don’t see why it shouldn’t work. As long as you are sure you are running his profile with target script while you run BMS.
I see a couple things in your screenshots that may cause you problems.
1. Your throttle mappings are incorrect. See the post above to Harm88 regarding Z Rotation and Z Axis.
2. You are using a differently named keyfile. If it’s just mine renamed and/or modified… that’s ok… if it’s someone elses keyfile there may be problems.
3. You do not have they Range Knob mapped to the “Throttle - Thrustmaster Combined (0)”. If you do that, you’ll be able to use the red China Hat to zoom the TGP.
-
I see a couple things in your screenshots that may cause you problems.
1. Your throttle mappings are incorrect. See the post above to Harm88 regarding Z Rotation and Z Axis.
2. You are using a differently named keyfile. If it’s just mine renamed and/or modified… that’s ok… if it’s someone elses keyfile there may be problems.
3. You do not have they Range Knob mapped to the “Throttle - Thrustmaster Combined (0)”. If you do that, you’ll be able to use the red China Hat to zoom the TGP.
1. I only fly the F-16 so I have no use for 2 throttles.
2. I just changed some keyboard mappings and renamed it (I use S / Shift + S for steerpoints etc.)
3. Ops! thanks for the reminder
-
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.
I was recently setting up my Warthog to use your TARGET profile. I can run the profile just fine and all the axis’s respond correctly and all switches that send a key command work. However, none of the buttons on the stick or throttle are assigned in the game. I am guessing because the device order wasn’t set properly when the script is run. I assume the number at the end of each axis means the order Windows has put it in. Well, I have noticed in your screenshots and all setup screenshots for you profile that Thrustmaster Combined should be (0). Mine is not, it is (4). The buttons on my stick start in the 140’s.
Could this be why the buttons are not mapped in game? If so, how can I go about fixing it? I cannot even imagine going through the keyfile one by one. I am hoping there is an easy fix if that is indeed the 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.
-
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.
I appreciate the detailed response. That really helped a lot. I knew in theory what had to be done but didn’t know the best way to go about it. Your spreadsheet was very useful. I have used your profile before, last May-ish. It worked flawlessly before. Since then, I have gotten three ten port USB hubs that are full plus all the 12+ ports on my mobo and upgraded to Windows 8 and an FSSB R3 for the Warthog. Makes sense that it did not go so smooth this time for me. I was using the Cougar throttle with the FSSB R3 Warthog but the Cougar throttle is just not cutting it anymore. Yours definitely is the best profile.
I spent from 9am to about 6pm trying to get this to work, as I had nothing better to do today. First it was editing the key file but then the shifting wasn’t working then it was re-ordering the USB inputs, among other things. I finally got it working and now I’m gonna pass out from the mental strain of so many numbers. Ultimately, I did it by re-ordering all the inputs. I actually found the easiest way was to right click and remove a device in “Devices and Printers”. Once I got the stick and throttle working, the MFD’s were not in the correct order so I kept removing and letting it re-add itself until it finally put itself in the right place. Now I know the easier way. I am terrified to reboot my computer for fear of screwing it up again. I can’t even imagine how borked the controls for DCS are now.
Thanks for helping me get it working again.
-
Hello Morphine,
First of all thanks for the profile. For me the Target software is very difficult to understand and with your profile I can fly with the Warthog without knowing the software.
For online flying I want to change the setup of the MIC switch according to my setup of Teamspeak. (there is no Scroll lock on my keyboard and I don’t know what you mean with mouse center)
What do I have to do to change your setup to my default? For UHF I want the Home button and for VHF I want the End button.
Is it only changing the line in de script editor or is that to easy?
In the script editor I see the following lines
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, PULSE+F12, PULSE+F11);
In the explanation of your profile I read about the Mic Switch that we don’t have to have separate Target profiles for TS3 and IVC. So for me that’s a little bit confusing.I also remapped the paddle switch/lever to the wheelbrakes as you explained in this forum. When I edit the .key file in Notepad++ I can’t see the lines where you are writing about. I see the following text without #Paddle/S4 (… and so on…):
In line 12: SimWheelBrakes -1 0 0X58 0 0 0 1 “HOTAS-Wheel brakes”
In line 30: SimAPOverride 1152 0 0XC8 2 0 0 1 “HOTAS-AP Override”I hope that you can help me out.
Thanks again
-
I am having an odd issue with this profile, I have a new Warthog, and for some reason all the buttons are doing what they are suppose to, Except
The Mic Switch is doing the speed break - U: Speed Break Open / F Speed break close
Slew control push is not doing cursor enable, but is doing UHF
Left Throttle button is not doing uncage but is doing VHFI might have VHF and UHF backwards, but I cant figure out how to fix it and why its just these few that are shifted?
Any thoughts? I havent touched anything in the target or keyfile.
Thanks,
-
Reload keybindings in game Setup.
Exit game.
Exit target
Start target start game loar keybindings. -
Hi pistolero
Can u build a version for warthog
Im a 2lefthanded guy.
Greetings from austria.Reload keybindings in game Setup.
Exit game.
Exit target
Start target start game
load keybindings. -
Was able to fix my issue, I didn’t realize that saving the keyfile in game messes it up. All issues solved.
-
Thanks for the profile. Work great!
-
What is the idea of putting a small deadzone in both TARGET script and BMS advance controller setting, Morphine?
-
What is the idea of putting a small deadzone in both TARGET script and BMS advance controller setting, Morphine?
I agree they are both probably not necessary and you can feel free to remove one or both of them depending on your preference.
-
I agree they are both probably not necessary and you can feel free to remove one or both of them depending on your preference.
Pardon my English as I’m not native speaker. I mean to ask you that do you find it beneficial in some way to put those deadzone on?
-
Pardon my English as I’m not native speaker. I mean to ask you that do you find it beneficial in some way to put those deadzone on?
The reason I added the deadzone to the TARGET profile was that my joystick does not always center properly due to some design or manufacturing issue. I did it before realizing that BMS also defaults to a small deadzone. I eventually removed the deadzone from one of them (I think it was BMS) so that I was only adjusting one of them.
The primary benefit of the deadzone is to deal with centering issues and if your joystick was stable enough I’d try to eliminate it (or make it as small as possible). Ultimately though having a deadzone is a personal preference for each pilot and something you should experiment with to get the feel/control you are looking for.
-
Hello Morphine!
Still using your profile but I’ve made a few changes that by now I cannot remember. Also using a customized .key file. My last post was on May this year so I’m not sure if I am using the “updated” version 2 or the “original” version 2 of your profile. Anyway, with all the changes I’ve made to my setup, I am hesitant to simply throw in anything new for fear of messing things up.
However, I am now in the stage of learning about flameouts and doing flamout landings and in-air restarts. It was hilarous when Kite and I went up for a flight to test this out, and I found out that I apparently have an F-16 with an “auto-engine restart” feature. I tried turning the engine off by flicking the Master Fuel switch to off and the engine would spool down, instruments go blank, etc…. but when I flick the switch back on, the engine starts back up, even with the throttle on full/half/idle/detent position. It doesn’t matter which position the throttle is in, it’ll restart the engine. Same issue when the Engine Feed knob turned to off and doing a negative-G maneuver… it’ll shut the engine off, but once I am in a position that would feed fuel back to the engine, it starts up. Also, lifting the throttle from Off to Idle does not kill the engine.
The only time the engine did stay off was when I landed, turned it off, and waited for the RPM to decay past 20%.
Any help appreciated!
PS - I’m also hoping to change the throttle hat switch to different views, but I’m not sure what it’s called in your .tmc file… Thanks!
I think I face this auto engine restart problem, and I use mostly stock Morphine’s profile. How do you solve it?
Edit: My mistake… It seems Engine Restart TE is design to use without Idle Cutoff patch enable.
-
I think I face this auto engine restart problem, and I use mostly stock Morphine’s profile. How do you solve it?
Edit: My mistake… It seems Engine Restart TE is design to use without Idle Cutoff patch enable.
Glad you figured it out. IIRC Ice was making the same mistake.
-
Downloaded all the attachments you have provided. When I run Target Script Editor it says “Complile error: Type required in FalconBMS-Warthog.tmc at line 1”
I followed your instructions to the 'T" placing the files where you indicated and the setup in the “Controllers” portion of setup in the game. Not sure what that error message is telling me to do. I believe I got it to run when I first set it up, but when following the directions to "Run the Target Script Editor " each time you start the sim, it now gives me that error message. I’ve opened both the DX file and the .tmc file and cannot figure out what the problem is. Any help would be appreciated. Should be obvious I’m not really TARGET savvy at this point.