Morphine's Profile
-
But on real f-16 the speed brake extension depend from pressure on switch, right? Or it is an on/off switch like on some business civilian jet?
There is not a pressure sensing mechanism in the switch but the extension part of the switch is spring-loaded. When moved to the deploy position, the speedbrake will begin extending (and its fairly quick). You can stop it before it reaches full extension by moving the switch back to center and leave it extended in it’s current state. Use the outside view and observe the speedbrake extending as you move the switch and quickly return to center. You should be able to stop it before reaching full extension. Below is the text from page 133 of the BMS Dash-1 describing the speedbrake operation.
1.13.4. Speed brake System
The speed brake system consists of two pairs of clamshell surfaces located on each side of the engine nozzle and inboard of the horizontal tail and is powered by hydraulic system A. The speed brakes open to 60 degrees with the gear not down and locked. With the gear down and locked speed brake opening is limited to 43 degrees to prevent the lower surfaces from striking the runway during landing. This limit can be overridden by holding the SPD BRK switch in the open (aft) position. When the NLG strut compresses on landing the speed brakes can be fully opened and remain fully open without holding the SPD BRK switch.The Speed brake switch
The SPD BRK switch, located on the throttle, is a thumb activated three position slide switch. The open (aft) position is spring loaded to off (centre) and allows the speed brakes to be incrementally opened. The closed (forward) position locks in place, allowing a single motion to close the speed brakes.The speed brake position indicator
A three position indicator is located left of the LG control panel.
Positions are:
• CLOSED
• 9 dots symbol: The speed brakes are not closed (thus open but it is not possible to say how open they are)
• Diagonal lines: Electrical power is removed from the indicator. -
This post is deleted! -
once i realized through trial and error (not having seen post 271 ) that the script needed to be run each time, i got the profile working and its awesome. maybe add that instruction to the OP for first time users? i kept trying to do things like adding the TMC file as a configuration, or dropping into the drag/drop windows, etc.
and IRT the speedbrakes, viper drivers report never using partial boards really. either full open or full closed. i love the way the speedbrake switch works on this hotas
and again, much thanks for the awesome profile sir! at some point i want to dive into the LED thing, and also i want to assign batt/main power to the APU switch, and maybe move some stuff around. We’ll see
-
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.
Well it has been at least eight months since I’ve played BMS because after I upgraded to Windows 8.1 I didn’t feel like going through setting up all my controls again. However, everything worked pretty much perfectly this time. This new code with the LED’s though is messing up things. If I utilize this code it causes my stick and throttle to become unresponsive once I hit the deadzone. If I don’t go into the deadzone with the throttle then everything continues to work. I copied and pasted the code exactly from here. Is the last long line supposed to be broken up into separate lines or something? Thanks for the help.
-
This post is deleted! -
I stopped using the LEDs and started using the mechanical detent once I was able to anchor my throttle. I’ll see if I can test it later this week.
-
I actually figured it out. I went into the TARGET GUI and enabled the LED’s on the throttle via the checkboxes and then your script worked correctly. With that said, I don’t use the LED’s now. I use a hybrid of your script. I bought the TUSBA for the Cougar throttle so I can use it without the Cougar stick and I use the switches on the Warthog throttle with the FSSB R3 for the Warthog stick plus the MFD’s and your G-13 profile. Then, next week I have the Obutto cockpit coming so that will shuffle it all up. Without your script though, I would be SOL.
Re-ordering controllers in Windows is a huge pain still and there is no fix.
-
I also have Obutto and FSSB3. Works really well to have the FSSB3 anchored to the A-10 Obutto kit. I ditched the MFDs and G-13 and went 100% touchscreen with Helios.
-
I also have Obutto and FSSB3. Works really well to have the FSSB3 anchored to the A-10 Obutto kit. I ditched the MFDs and G-13 and went 100% touchscreen with Helios.
Can you do me a favor and PM me a pic of your Obutto setup? I need ideas so I’m prepared next Tuesday when it arrives.
-
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.Cheif1942, If your still around can you help me and let me know how you resolved the above issue. I’m new to BMS and just recently purchased the Thrustmaster Warhog Throttle and Stick. So far I have this Error everytime i try to run Morphines Profile. If anyone else wants to chime in and help a guy out it would be greatly appreciated.
-
@ Morphine
Just started using your script about a week ago and lovin it. I may tweak it a little bit to accommodate my own tastes. But overall it installed and works perfect.
Thanks alot !!! -
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 0I would caution using your shift button for any trimming and instead keep trimming unshifted and use the shift functions for your views (or whatever else you want). In BMS, your trimming can get “pinned” when you use the shift button unless you first press the shift button and then the trim.
If you hit the two simultaneously (or if your timing is off), your trim direction will stick and cause your trim to repeat until it is maxed out in the direction originally pushed. While you can quickly reset the trim if needed, I found this too distracting and problematic. By keeping my trimmer unshifted, I never experience this problem, although it would be nicer to have the trim functions shifted since they aren’t used all the time.
If anyone has a workaround for the trim sticking when shift-pressed, please share!
-
Hey Morphine,
Thank you very much for your Warthog’s profile. I have just a problem with the autopilot, I can’t activate (with throttle or in the game) the AP - ALT HOLD
See you
-
I don’t know if this profile is outdated and I’m just late to the party but I can’t get most of the shift functions to work. Flaps for example - from what I understand pinkie+flaps up or down on the throttle should work the flaps? And pinkie+tms don’t seem to work either.
-
I don’t know if this profile is outdated and I’m just late to the party but I can’t get most of the shift functions to work. Flaps for example - from what I understand pinkie+flaps up or down on the throttle should work the flaps? And pinkie+tms don’t seem to work either.
It is VERY rare indeed to need to manually control the flap positioning. The FLCS handles that for you.
-
I don’t know if this profile is outdated and I’m just late to the party but I can’t get most of the shift functions to work. Flaps for example - from what I understand pinkie+flaps up or down on the throttle should work the flaps? And pinkie+tms don’t seem to work either.
The “Flaps” switch on the throttle does not have any shifted functions programmed to it.
The shifted TNS functions are not realistic so I wouldn’t worry about them not working either.
-
Hey Morphine, thx for sharing this good profile! When using it with stick and throttle only everything is pretty fine. But if I use it with my MFDs, the keybindings get mixed up; as an example, when pressing CMS or DMS or TMS i get to the MFD-Buttons.
Is there a way to get this working or is it just not written to work with MFDs? pls help me out on this one. thx -
I use Morhine’s profile with thrustmaster MFDs, all works fine. Perhaps recheck your setup. Sounds like you make have a duplicate setting somehow.
-
I got it now! I had the MFDs on a USB-Hub, which caused the problem, now I have them in different USB-Ports so everything is fine! Wonderful, thx for telling me that it works, helped me out. A good thing became just great ;). jipee, now, after everything is working as it should I can begin my struggle with the Viper
-
I got it now! I had the MFDs on a USB-Hub, which caused the problem, now I have them in different USB-Ports so everything is fine! Wonderful, thx for telling me that it works, helped me out. A good thing became just great ;). jipee, now, after everything is working as it should I can begin my struggle with the Viper
Glad you got it working Gekko. The problem you were having was the Window’s ordering, or numbering, of your Direct X devices. By plugging your MFDs into different USB ports you were fortunately able to get them to be renumbered with Thrustmaster Combined as your first device and the MFDs as subsequent devices. You can read more about this common issue here: