Morphine's Profile
-
Thanks Morphine, I will try the TMS up. I know the button is working. However, another question. I decided to go through each tutorial from beginning to end because I want to learn to fly this thing right. In the first tutorial, Ramp Start, I keep getting stuck on the throttle initialization. I am obviously using your profile and key file, and I have the idle detent redline setup up slightly above the bottom the the throttle movement (although I have tried it at the bottom as well). I have also enabled the idle cutoff patch in the config. But the tutorial says to move the throttle from idle to full AB and back to off, and for some reason it thinks I am not either moving it to full AB or to off, not sure which. I have the AB green line set in the dead zone. In the setup when I move the throttle over the detent to off it shows a key combo of Alt-i. I really don’t want to get stuck this early…:) Any ideas?
atrdriver
-
A couple of things….
I have the Idle Cutoff unchecked in the Configuration Options -> Settings Hardware (the Falcon BMS Configuration before you launch the Sim).
Shutting Down: I have the Red Line all the way to the bottom. The Idle Cutoff for the Throttle works when you lift the throttle levers up and over the detent on the bottom. This will shut the engine down. It does it by triggering a button when you lift the throttle up (I’ve programmed the button to send ALT-i).
Starting the Engine: After configuring the Jet for start (fuel, brakes, power, etc.), I leave the throttle at idle in the unlifted state (just pulled all the way back) and hit the JFS button (ENG OPER L on the WH). After a short pause you should hear the JFS spooling up. Wait until the SEC light goes out on the Caution panel and then move the throttle to 50%. Now hit the Idle Detent button (ENG OPER R on the WH) and wait about a second. For some reason, I then need to move the throttle forward and back about +/- 20% and eventually the RPM’s start coming up. As soon as the RPM’s cross 35-40% you can then just move the throttle back to idle and the engine will continue to spool and eventually stabilize at idle (~70%). If the RPM’s don’t start coming up after about 5 seconds, I repeat the procedure starting with the throttle to 50% and hitting the Idle Detent button (ENG OPER R).
Hope that helps and good luck.
-
Yes, that’s how it is working on mine as well, but in that first training flight for some reason it either isn’t seeing the throttle moving to full AB or to full OFF, I’m not sure which. And in that tutorial there is no way to get by that step unless it sees both full AB and full off. When I’m in the controllers setup screen I see that lifting the throttle over the idle detent sends an ALT-i. This one is driving me crazy. I will try posting in the tech support and see if anyone there has any ideas. But when I’m flying I can shut down the engine by pulling the throttle over the idle detent…
-
Hmmm… never looked at the training mission you mentioned… I’ll give it a shot and let you know what I find.
-
I finally figured it out, you just have to keep hitting Shift-K until it clears that screen. Startup worked just as you said…Thanks a ton!
-
Morphine,
I love your profile and it is by far the best one out there for FALCON BMS. However, I seriously miss having the option for LABELS and wish the CMS was configured realistically with the HOTAS. Everything else is perfect. Im active duty officer is the Army and dont have time to learn TARGET scripting or keymapping and was seriously hoping you can help me out. Any assistance Morphine would be greatly appreciated. Thanks.
-
PM Inbound.
Morphine,
I love your profile and it is by far the best one out there for FALCON BMS. However, I seriously miss having the option for LABELS and wish the CMS was configured realistically with the HOTAS. Everything else is perfect. Im active duty officer is the Army and dont have time to learn TARGET scripting or keymapping and was seriously hoping you can help me out. Any assistance Morphine would be greatly appreciated. Thanks.
-
Just dropped to say thanks for great profile. Very logical and there wasn’t lot for me to change. Some minor changes on view bindings and i switched laser and cat 1/cat 3 switch other way around, because on cockpit Cat switch is left and laser switch is on right so it makes sense to me to have them same way on throttle. Otherwise it’s perfect profile.
-
Yes, thanks for the great profile and it has prompted me to start learning TARGET!
-
Hey guys, new member here, wanted to first say this is a great sim and great community!
I’d love to be able to use this profile with my warthog, but am a TOTAL taget newb. I understand I have to put the tmc file in the script folder, but what exactly is the “key” i downloaded and where do I put it in order to be able to use the profile? I already discovered how to ensure 6DOF with my TIR5 with the vectors and FOV enabling so that’s not a problem, just need help figuring out how to correctly setup this profile. If anybody would be willing to help a complete idiot, in other words, it would be very much appreciated! :). Also, does BMS allow for the combined WARTHOG and use of CH pro pedals? How do I use both together?. I realize that’s alot of questions, but I genuinely appreciate the help guys!
Thanks again,
-Comrade
-
I hope I can help you out. First of all, make sure after following the link to the files, you download everything and I would even suggest printing out the pictures that show how to assign the controllers within BMS. The .key file is placed within your BMS config folder which should be something similar to C:\Falcon BMS 4.32\User\Config. Then, “run” the script or .tmc file that you downloaded from the TARGET script editor. Start BMS and navigate to the controllers menu and you need to load the key file. To do this, click “setup” and then “controllers.” You will see a list of key commands and under that you will see a button labeled “load.” Click it and you should see a file called “warthog_dx.” That is the key file that needs to be loaded within the sim and it has the necessary keystrokes assigned that will allow the profile to work. Then, go into the advanced tab under “controllers” and set up the axis’ based on the pictures (this is very important). Remember, you need to run the script each time before you go into the sim. If you don’t, BMS will not remember your axis assignments and you will have to re-assign them. Also, you will need to know what the different TMS and DMS buttons do within the sim. This is explained in the BMS manual. With regards to your pedals, are they “gameport” or “USB?” I’m going to assume they are USB pedals and yes, you can use those. They will be listed as a separate axis within BMS as will be the toe brakes (z axis for the rudder and x and y for the different toe brakes). Hope this helps and if I missed something, I’m sure someone else will point it out.
-
Hey, new member here….
Could somebody please tell me how to disable the TrackIR Reset and TrackIR Center buttons from the paddle switch?I use my own key press for that function and would like to remap the paddle switch/lever to the wheel brakes.
I’ve had a look through the TARGET script but I’m not sure which entry to delete/modify, I know the Paddle switch is S4 (259) and the Track IR functions are mentioned in the Warthog DX key file but I’m unsure on how to proceed.
Many thanks for the profile (saved me some work), and thanks for any replies.
Cheers.
-
This post is deleted! -
You just need to REM out the second line in the statement below in the TARGET Script:
So:
//Paddle/S4
MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX4, 750));Becomes:
//Paddle/S4
// MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX4, 750));The Paddle will now work as in Real-Life as the Autopilot disconnect alone (i.e. no TrackIR Center)
-
Thanks Morphine that has worked a treat. Just one last question ?
If I wanted to add the Switched Paddle button to wheel brakes then is it done in TARGET?
Thanks again,
-
You probably could but a better way would be to edit the .key file (Warthog_DX.key if you are using mine) with Notepad++ (or equivalent) to replace the first two lines below with the second two lines:
Paddle/S4 (…and so on…)
SimAPOverride 3 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimWheelBrakes 3 -1 -2 0 0x0 0
Now the paddle will apply your wheel brakes rather than override the autopilot.
-
Thanks! Works just how I like it now.
Great profile, Many thanks,
-
This is a great profile, thanks for it. I had some trouble tweaking it and I’m not even sure I did it right. I recently bought a used Cougar and already had a Warthog. I just wanted the Cougar for the throttle. I recently decided to upgrade the Cougar to the FSSB. It’s awesome. Anyways, the Cougar throttle sucks, the pots continually spike and the antenna elevation has no center detent. I couldn’t take it. So I attempted to use my Warthog throttle with the FSSB modded Cougar stick using this profile. Yeah, that didn’t work so well. I think I got it working now, except for the push of the CMS button for the jammer. Also, on occasion, the throttle base buttons don’t work as intended in the profile, not sure what’s up with that.
What is the “ideal” way to tweak this profile for it to work with the Cougar stick and the Warthog throttle? Thanks.
-
What you are trying to do should be possible. A couple of things you will need to consider (although I’m speaking theoretically as I’ve not tried to do what you are doing).
-
If you START with my profile as your base and use the Target Script Editor, I’m assuming you will have to remove the line that says:
Configure(&HCougar, MODE_EXCLUDED); -
I would then start with an empty Script by just rem(ing) out all of the commands in the Joystick Key Mappings section of the script.
-
Next, start the Script and then use the Device Analyzer to see how all the buttons and axes on the Cougar Joystick and Warthog Throttle are mappped to the DX buttons. Remember, there is a 32 button and 8 axes limit with Direct X so probably not all of the Throttle buttons will be mapped to DX buttons as the Thrustmaster Combined Controller is seen by Windows, and subsequently the game, as a single controller.
-
Now you will know the default DX button mappings and you can go back and program the DX buttons in the .key file. For buttons that are not mapped to DX functions, you can assign them functions in the Script. You’ll notice I did that for things like the Pinky Switch (that controls the Lighting).
-
You can also reassign the DX buttons (from the default mapping done by Target for the Thrustmaster Combined Controller) to other buttons. I did this with the EORMOTOR for example and made it Direct X button 26.
-
As you’ve noticed the CMS down on the Warthog Stick is assigned DX button 19 by Target. Since you are using the the Cougar Stick instead, my guess is that the DX 19 button was given to a button on the Warthog Throttle (thus changing many of the DX button assignments controlled by the .key flie) and that is why buttons on the Warthog Throttle appear to be working incorrectly. So as mentioned above, after you figure out the new DX button scheme, you will need to edit the .key file to relect the new order of using the WH Throttle with the Cougar Stick.
Hope that helps and good luck.
-
-
Thanks for the help. To be honest I don’t know a thing about how to edit the key files, script editing and DX shifts. I’ve looked at the key files and I see lots of numbers like 0x0001 or whatever. I haven’t figured out what all that is attributed to. The scripting as well is foreign to me. I’m not asking for an in depth explanation, I’ll read up on it all. Thanks for setting me on the right path though.
I sometimes put my Warthog stick on the FSSB. I like the feel better and the push of the CMS button. I was trying to get Thrustmaster/Guiliemot to sell me just the Warthog stick. As we all know, they don’t do that. I’m going to keep asking over the months until they say yes