Morphine's Profile
-
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:
-
Thx for the link Morphine, the other thing i did, was to run your profile with the script editor, not the target GUI as i did before.
-
Instead of Thrustmaster Combined, the Warthog is showing up as “thrustmater virtual controller”. What gives?
-
Hi
Ive got a problem; In the procesus to use, the morphine profile for the Warthog, (for imperious reasons) i need to invert in the script, the pitch axis for the joystick (y axis.). The problem is, that I dont know how, would you be so kind to teach me how?
Thks.
S!
-
it should be in the advanced tab in the settings under flight controls just tick the invert box on the right
-
I don’t think the X & Y axis has an invert selection…