BMS 4.33 Profile.
-
I’m not familiar with that profile, but I wonder two things:
- Have you gone to Setup–> Controllers–> Advanced and set up the various axes; assigning rudders to yaw, throttle to throttle, etc.?
- Have your checked the file x:\Falcon BMS 4.33 U1\User\Config\DeviceSorting.txt to be sure your devices are in the ‘proper’ order for this profile?
-
Thank you for the reply. I think that the device sorting is the issue. I don’t have that file but rather a “default devices”. I am a real newbie to the HOTAS stuff and BMS is a bit trickier than DCS, but the reward much greater.
If you have the time could you explain the device sorting?
-
In layman’s terms ('cause that’s all I know) ….
First you should have that file afaik. I thought (pretty sure) it’s in the default install.
Each device takes up a ‘slot’. Depending on how the devices are connected, Windows and/or BMS may assign those slots differently … one time the Stick is in ‘slot 1’ and the next time it’s in ‘slot 2’.
The issue is that the keyfiles assume static device location. The key file assumes the ‘buttons’ on the Stick (say) are set up for the Stick to be in (say) ‘slot 2’ … if Windows puts the stick in a different slot it buggers up the device order and the Stick buttons don’t do what they’re supposed to do.
The file I reference tells BMS what ‘order’ the devices should be recognized by BMS; from a BMS perspective, it keeps the devices and their ‘slots’ static.
-
First you should have that file afaik. I thought (pretty sure) it’s in the default install.
Avid, are you running 4.33 or 4.33u1? Not sure 4.33 had the devicesorting file. In your question you mention 4.33, but not u1….
Verstuurd vanaf mijn C6903 met Tapatalk
-
Hi All,
Im having the same issues and it appears that the target software that runs the morphine script does not have the extra axis in the script to account for the t flight pedals. The pedals get combined with the warthog and throttle when the script is run. Its a pain as all that would need to happen is for the t flight pedals to not be included in the axis when the script is executed. It seems the Target software does this because it thinks this is what you need but in fact to simply find away of not having the pedals pulled over into the warthog combination would fix the problem.
Thing is i have no knowledge of the script editing to even add the extra axis for the pedals, failing to stop them being included in the target software either.
This is a real show stopper for me as i bought these pedals specifically to allow me to run BMS without having to use my wheel pedals which simply is not ideal.
Need help on this as with the OP
-
Ok a work around can be to unplug the t pedals and then run the script you use and plug the pedals in afterwards.
Its not ideal but it works for the time being.
-
Sorry guys for the late reply, hectic work week!!
RuskyV you have the solution, that has fixed it and while a pain it means the game works!! Thank you so much!! If I find a more convenient fix I will let you know. Now I just need some advice on editing the key file to make the trim hat work the views.
-
Hi All,
Im having the same issues and it appears that the target software that runs the morphine script does not have the extra axis in the script to account for the t flight pedals. The pedals get combined with the warthog and throttle when the script is run. Its a pain as all that would need to happen is for the t flight pedals to not be included in the axis when the script is executed. It seems the Target software does this because it thinks this is what you need but in fact to simply find away of not having the pedals pulled over into the warthog combination would fix the problem.
Thing is i have no knowledge of the script editing to even add the extra axis for the pedals, failing to stop them being included in the target software either.
This is a real show stopper for me as i bought these pedals specifically to allow me to run BMS without having to use my wheel pedals which simply is not ideal.
Need help on this as with the OP
Going to take a stab and guess that you are still using a TARGET 1ish version as I didn’t see anything specifically in the manual about a T.1600 and TFRP whereas TARGET version 3 does talk about that combination. Suggest you read the TARGET users manual for version 3.0 pages 12-14 covering “Configure Axes Mapping”.
I looked at SimHQ and someone showed an include line so guessing that creating an exclusion line in the TARGET script should also do the trick.
At the very top of your TARGET script should be an area that looks something like this. It won’t be the same because we own different hardware so DO NOT directly copy this into your file as that will screw things up.
include "target.tmh" int main() { Configure(&HCougar, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); if(Init(&EventHandle)) return 1; SetKBRate(50, 50); SetKBLayout(KB_ENG); SetShiftButton(&Joystick, S4);
Now if the code from SimHQ was correct if you added in
Configure(&TFRPRudder, MODE_EXCLUDED);
in the same location as you see my exclusions in your file that should stop TARGET from including the rudder pedals into the combine. Otherwise follow the suggestions from the TARGET users manual for version 3.
-
That is awesome mate thanks so much for taking the time to sharing this! ive added it to the script and it works a treat. I guess this will also solve the issue for AvidHatwearer
Again thank you!
-
Does anyone have a copy of the latest ver of the profile please Morphs page says not up to date get from others.
So are there any OTHERS out there with the latest ver pleasesorry not ment for here
-
I’m a little late to the party but did you find the latest version of the profile? I just got my Warthog working with 4.33 U2 using the files from here via reddit.
@ Agave_Blue:
DeviceSorting.txt
THANK YOU for this tip, it fixed my issue. I had the combined controller created by TARGET (I think that’s how it works) sorted last which was causing issues with assigments (DMS was showing assigned to OSB keys in BMS. After moving “Thrustmaster Virtual Game Controller (root)” to the top of DeviceSorting.txt, Morphine’s profile is working as intended with my Warthog in 4.33 U2. Thanks!
-
I’m a little late to the party but did you find the latest version of the profile? I just got my Warthog working with 4.33 U2 using the files from here via reddit.
THANK YOU for this tip, it fixed my issue. I had the combined controller created by TARGET (I think that’s how it works) sorted last which was causing issues with assigments (DMS was showing assigned to OSB keys in BMS. After moving “Thrustmaster Virtual Game Controller (root)” to the top of DeviceSorting.txt, Morphine’s profile is working as intended with my Warthog in 4.33 U2. Thanks!
Hey I created that profile. It had some issue, so I created a new version. I also made a version of the script to account for the new version of the thrustmaster pedals. Tpedals was added to the script title to differante it from the original. It can be downloaded from the link below.
https://www.dropbox.com/sh/4l2j2sbbkkmwoaa/AAAMks8YYDvUsOQ6vr7bi5bia?dl=0