Morphine's Profile
-
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…
-
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’m having the same issue. The ‘a’ key is not registering even though it registers, for example, just fine for the RDR ALT switch.
Btw great work Morphine!
-
A quick follow-up -
I was able to resolve the AP - ALT HOLD issue by starting Falcon BMS without the Warthog script being active, exiting, enabling the script, then re-entering Falcon; of course, the ‘Advanced’ tab of the control settings had to be reset, but after that the autopilot switch has been working great.
-
My Mic switch UP transmits on UHF and is also MMB. Pressing MMB causes my BMS to center and zoom out the view completely. What should I do to remove this since I don’t need TS3 keys to be there and I’d rather have it as Mouse Button 4, for example.
-
Hi Morphine…
I’ve been flying with your profile for a couple of weeks and It’s amazing.
I only want to say thank you so much for share your work.
-
Thanks for the profile Morphine and Happy Holidays! The one change I’m trying to make is on the Throttle coolie. Rather than have a snap zoom with button 22 / HUD only on 24 - I’m changing 22/24 to be incremental FOV increase/decrease. I’ve made the change in the keyfile and that is working fine.
How do I - if possible - set it up so that if I hold down the coolie it will ‘repeat’ - similar to how trim functions?? Right now I have to keep bumping the hat over and over.
-
hello a couple questions, where do i put the files : dx key, and also the.tmc file? also how do i load The .tmc file to run with the TARGET Script Editor ??
-
Put the .key file in your FalconBMS 4.32/User/Config folder. Load the key file in Setup. The .TMC file can be placed anywhere you wish, you just have to navigate to it when you launch TARGET.
-
Thanks for the profile Morphine and Happy Holidays! The one change I’m trying to make is on the Throttle coolie. Rather than have a snap zoom with button 22 / HUD only on 24 - I’m changing 22/24 to be incremental FOV increase/decrease. I’ve made the change in the keyfile and that is working fine.
How do I - if possible - set it up so that if I hold down the coolie it will ‘repeat’ - similar to how trim functions?? Right now I have to keep bumping the hat over and over.
Here’s what I did:
//Coolie Switch
MapKey(&Throttle, CSU, REXEC(1, 40, “ActKey(PULSE+KEYON+L_SHIFT+L_CTL+L_ALT+USB[0x56]);”));
MapKey(&Throttle, CSD, REXEC(1, 40, “ActKey(PULSE+KEYON+L_SHIFT+L_CTL+L_ALT+USB[0x57]);”));I also changed g_fFOVIncrement to 2 in Falcon BMS.cfg to achieve a finer control.
-
Here’s what I did:
//Coolie Switch
MapKey(&Throttle, CSU, REXEC(1, 40, “ActKey(PULSE+KEYON+L_SHIFT+L_CTL+L_ALT+USB[0x56]);”));
MapKey(&Throttle, CSD, REXEC(1, 40, “ActKey(PULSE+KEYON+L_SHIFT+L_CTL+L_ALT+USB[0x57]);”));I also changed g_fFOVIncrement to 2 in Falcon BMS.cfg to achieve a finer control.
Thanks Wheezy! So it seems this has to be done on the Target side for this to work vs. in the keyfile side. Didn’t know about the FOV Increment either - good stuff! Happy to report I implemented this and it works perfect.
-
@Morphine - Been using your profile for a couple of months now and I can say that it works great! The only qualm I have is the shift and zero trackIR mappings need to be swapped (as it can be quite hard to hold in the pinky button while operating other controls with the same hand whereas the paddle is so much easier to hold in) but I can see you already have a linked tip on how to do that, brilliant!
Thanks for creating and sharing it as well as making the print outs (currently stuck to my wall beside the PC )
- Hyp3rion
-
Whenever I put the line of code for the LED’s in, the virtual controller freezes and does not move any axis. Only the non-led profile works and I haven’t found a way to make the LEDs work. ANy ideas?
-
I sometimes made a bit complex Warthog programming, using the LEDs as indicators for a number of things. Those scripts ended up causing problems with the Warthog programming and drivers. I discussed it with Thrustmaster Support, and they dug it out all the way. They provided me with some new internal files to their TARGET unit.
They did not provide any exact information, but when overriding the older TARGET file in their own directories, it fixed these LED and freezing problems. Even when looking inside the file, it is not self explanatory even by programmer eyes.The fixed file obviously was overriding something in their own setup, but I think they did not re-version their TARGET software because of this. It may or may not be fixed in their distribution, and you can always try to reload the TARGET software, and see if it is newer, even without newer version number.
OR you could try inserting the file I received. You can find it in my profile, here: https://www.benchmarksims.org/forum/showthread.php?5857-Is-there-a-TM-Warthog-profile-that-mimics-F16-hotas-setup&p=71632&viewfull=1#post71632 Remember to backup the old one.
I never had any problems after I replaced the old one, and since then my profile has been working perfect.Of course my profile may be a borderline case, along with the author. But hey, if it fixes something internal, it might fix it for you too!
Greetings to a fellow Finn!
-
Whenever I put the line of code for the LED’s in, the virtual controller freezes and does not move any axis. Only the non-led profile works and I haven’t found a way to make the LEDs work. ANy ideas?
As TKorho says, there seems to be some bugs in the LED handling as I’ve also had problems and removed the LED code (I also decided to use the physical AB detent so I didn’t need the LEDs). You could try using the newer tmh file that he provided to see if that fixes the problem as well.
@TKorho, thanks for providing the new tmh file.
-
As TKorho says, there seems to be some bugs in the LED handling as I’ve also had problems and removed the LED code (I also decided to use the physical AB detent so I didn’t need the LEDs). You could try using the newer tmh file that he provided to see if that fixes the problem as well.
Yeah the only LED coding I have is for the Maser Arm and Master Lighting Switch for FENCE purposes but I always physically verify the positions of the switches anywho so it is redundant. However I have never had a problem with those two LEDs. The only peculiarity I have found is it doesn’t check the switch positions when you spin up your profile and (for me at least) I would have to cycle those two toggles to get the throttle/TARGET to get it’s act together. Other than that all normal. However I’m also not running Morph’s profile other than the engine start/stop coding.