Morphine's Profile
-
It sounds like what you are describing is a common problem with doing a Taxi Start in MP and happens to everyone regardless of the HOTAS they are using. Sometimes planes even run into each other which can cause them to explode and really ruin the fun. What we typically do is make sure you’ve cycled the throttle when it’s loading but more importantly be pumping the hell out of the brakes so that your plane stops as soon as possible after you load in. Of course, none of this is a problem if you do a Ramp Start
-
Didn’t use the software, but you were definitely on the right track, all up and running now. Thanks a bunch mate!
What was your fix? I have the same problem. Windows 8.1. The mapping works fine in TARGET but in BMS the key mapping is all off - random MFD assignments and such for buttons. Some of the buttons, however, are correct, like the trim hat. Others are not, like the trigger on the stick. Axes are all fine, DX IDs are in the proper order.
-
good morfin
Thanks for enjoying your profile, now a question as active the DataLink A / A, A / G What I seek and not find it on the Warthog Profile -
But the Aircraft also starts rolling if i don’t move the throttle at all. With a light payload it even starts rolling when i hold the wheelbrakes while loading.
Has anyone else encountered this, and if yes, come up with a solution?
Ok I limited my quote to the relevant portion.
Morph I think he hasn’t set up the throttle correctly for the AB/idle cutoffs to see a problem like this. That isn’t an issue with the profile D_Fens but with user setup of controls. You should have a red line close to the bottom of your throttle axis bar and a green line closer to the top, about 2/3rds up or so. If your green line is at the bottom close to the red line you set up BMS incorrectly for the throttle.
Now if it is set correctly then I’d go with Morphine’s advice in that you might be putting the wheel brakes on too soon and the sim isn’t seeing that when you enter pit.
-
AB and Idle Cut Offs are set properly. And the only problems appearing are the ones mentioned above.
So when would be the right time to hit the brakes? -
I start pumping the brakes while I’m in the loading screen and don’t stop until I’m in the cockpit on the ramp.
-
The only time I ever see the fast taxi on pit entry anymore is when I forget to cycle the throttle from idle to mil to idle during the load screen to pit. As long as I do that I will only be moving a bit when I enter 3D and can quickly stomp on the brakes and be all good.
-
Morfine hello, there some switch your profile to send DL AA and DL AG?
-
The only time I ever see the fast taxi on pit entry anymore is when I forget to cycle the throttle from idle to mil to idle during the load screen to pit. As long as I do that I will only be moving a bit when I enter 3D and can quickly stomp on the brakes and be all good.
Hm, strange. In my case this exact behavior causes my aircraft to cross half the airbase in full AB:lol:
-
I am using this profile but for some reason when setting the x and y axis for pitch and roll the rudder toe brakes are activating it and not the stick movement.
The rudder toe brakes are controlling the brakes plus the pitch and roll. -
Right, so… I KNOW this is going to be likely a stupid question… I apologize for this in advance if it is - but I’ve been looking everywhere for the reason why I’m running into this…
So after I run the script; assign the flight control axis; and load the key file… nearly all of my buttons are coming up as MFD OSB assignments - except for a few buttons - like the trim hat on the stick or master arm on the throttle…
Any ideas?
For USB devices I’ve got Track IR, G13, and the warthog HOTAS but thats about it. I know theirs got to be a good answer for this, but I’m terrible with TARGET and I’m new to BMS.
I know its a long way from FreeFalcon and AF - but I’m pretty sure I don’t want to assign my CMS switch to LMFD OSB 15-18… right?
If so, I’d better get my nose back into dash-1 because I am WAY off from where I need to be on these avionics
Thanks in advance btw for all the help from Morphine and the rest of you
EDIT:
Fixed it - Some USB device was picked up as device #1 - so the TM was coming in as buttons 34 and up or something; hence all the OSB buttons… Got it fixed by unplugging EVERYTHING. Including the G13/Wireless Headset/Track IR/Mouse and KB -
Talk about being deflated…… elated
Spent most of the day getting the TARGET profile to work in 4.32.
After a few controller unplugs/reconnect etc it is up and running as it should be, happy days.but as of 18.01 and the release of 4.33 the possibility of doing it all again looms… Morphine (please tell me it will be ok)
-
Hi Splash ive been using this profile under 4.33 and have had no issues so far. Load er up!
-
Same here
-
Working great so far for the most part, just having my CMS switch running OSBs. Can’t figure out why.
-
Working great so far for the most part, just having my CMS switch running OSBs. Can’t figure out why.
I’m having the same problem too. In the past, that was a symptom of having my rudder pedals listed before my stick and throttle by joystick ID. For some reason with 4.33, even though my rudder pedals are the last device in my device manager, in-game they are listed first. I’m trying all my black magic tricks to try to fix it, but no dice so far.
Edit: If anyone has a surefire way of reassigning joystick IDs so that BMS will recognize them in the proper order I’m all ears. I’ve tried using “Joystick ID Swapper” and even though it shows that I successfully swapped joystick ID’s, BMS still sees them backwards.
-
I went through the keyfile line by line (1301 lines) and cross referenced with the new file. It has been completely updated and all the new functions have been added to the file.
It works exactly like it always has; and works with all the new aircraft. I’ve been testing it for hours now. I’ve found zero bugs or mistakes.
I used Morphine’s original keyfile without any personal modifications. No other files have been changed so just start the target script like usual and load up this keyfile and you are good to go.It took a long time to do so I wanted to share it and hopefully save you guys some trouble.
Here is the file: https://www.dropbox.com/s/eb8393zfy1ll9bg/Warthog_DX-4_33_2.key?dl=0
Cheers
-
This post is deleted! -
Doesnt work for me either. Tried all .key files but with the same result. Could be joystick ID issue.
-
It works when i connect my MFDs.