Morphine's Profile
-
I changed devicesoting.txt …thx TxMtb…and everything works…
Glad it worked. Have fun flying!
-
Hi,
I try with the Morphine’s profile modified file for 4.33 called FalconBMS-Warthog - LEDAB_2 and .key called Warthog_DX-4_33_2 with the changes in devicesorting.txt that you posted before ant it works.
Thanks a lot.
-
I use Morphine’s profile and it works fine. Check your “devicesorting.txt” file to ensure the numbering is correct. It should look something like this:
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{00F2068E-0000-0000-0000-504944564944} "CH PRO PEDALS USB "I just need to add to or modify the keyfile to add the 4 new callbacks for the F-18.
Sniped…
Mine looks like this… What do you do?
{0402044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{0404044F-0000-0000-0000-504944564944} “Saitek Pro Flight Combat Rudder Pedals”
{076406A3-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{FFFF044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”The game still sees Thrustmaster Combined as device 1 no matter the order
EDIT: Okay looks like I got the device situation figured out… Deleted the device text file and it generated a new one. So all the DX things are sorted. It does look like the newer 4.33 key file needs some fixing. It does not play well with 4.33 U1 very well.
-
I have taken away your third and fourth innings (only I have left the combined and pedals) and works perfectly. Obviously I have no MDF.
{0402044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{0404044F-0000-0000-0000-504944564944} “Saitek Pro Flight Combat Rudder Pedals”Fresco
-
For beginners, you may specify the steps to be done to change the profile and make it functional?
-
Okay I’m at a complete loss here… I’ve been able to sort out the DX stuff in terms of my Warthog and Saitek Rudders (Axis). The mapping within the game is completely different even using the newer Key File. For example when I press my Weapons release it comes up as button 32 Left MFD OBS. Missile Step is something completely different. In searching through this thread I did see a profile which removed the MFD mappings but it has to do with how DX has mapped my HOTAS. I never had this issue with 4.33 and this profile worked perfectly. I hope someone can help me sort it. I’ve actually uninstalled BMS and reinstalled. Lastly here is the default settings for the devices. It doesn’t matter what order I put it in. My throttle and stick combined are still defaulted to 1.
{076406A3-0000-0000-0000-504944564944} “Saitek Pro Flight Combat Rudder Pedals”
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”Windows 10
Warthog
Saitek Combat RuddersSolved. I change the order in the text file. Uninstalled my devices because Windows Reordered them. They reinstall and your good to go.
-
This post is deleted! -
Capt, I would try deleting the devicesorting.txt file.
Run the target script, then start BMS again and go into setup. Check what shows up.
Exit and check the order in the new devicesorting.txt.
It should have ThrustMaster Combined as the first entry.Edit: Just saw what you edited. If you move Thrustmaster Combined to the first line of the file you should be sorted out.
The way your file is, it’s seeing the Joystick/Throttle as device 2, hence the button shift. -
Okay I figured it out… Stinken Windows 10 reordered my devices. In other words if your Warthog Combined is not first in the list after keyboard it gets the second set of 32 buttons which are not aligned with the Key File. In the main part of this forum there is a thread that walks you through how to fix it. Basically you disable the devices in order and then you do a quick hardware change and it will resintall them in the correct order. I went back into BMS and now my Warthog Combined is the first device. Problem solved. Windows is very annoying sometimes.
-
Capt, bad part about that is, more than likely when you reboot the PC, the order is going to be wrong again. I’ve fought this in Windows 10 to no end.
That’s why our awesome dev’s created the devicesorting.txt file.
If you set the order correctly in the file. It doesn’t matter what order Windows put’s the devices in. BMS will see it as #1. -
Capt, bad part about that is, more than likely when you reboot the PC, the order is going to be wrong again. I’ve fought this in Windows 10 to no end.
That’s why our awesome dev’s created the devicesorting.txt file.
If you set the order correctly in the file. It doesn’t matter what order Windows put’s the devices in. BMS will see it as #1.I did make those changes to the devicesorting.txt file and it only corrected the AXIS not the actual Key mapping to the sticks. This is the first time I’ve ever had a DX mapping issue with Win 10 but I do see others are having the problem. At least I know how to fix it now. What a pain
-
Is anyone having any issues getting the throttles to work on the F-18 in a Cold Start in the TE? Loaded up another TE and the throttle does work but not when you cold start the plane.
-
I found the same issue initially. As I was faffing around trying to figure out my mistake I noticed the throttle jump forward over the detent on it’s own and was operational (animated) again. It was odd…
I hope this is what you were noticing? If not disregard.
-
Perhaps its some sort of callback that is not part of Morphine’s profile. Up until this point I can’t get the throttles to move in a cold start.
-
I am missing something important, where is the devicesorting.txt located please? Can’t find it anywhere
-
Can’t find it anywhere
Probably because you didn’t even bother to search
1. maybe the search function of the PDF reader will help, BMS manual, page 50
2. are you aware that Windows explorer is also able to perform searches?
3. Most of these users files are always in the same folder -
Thanks a lot Olivier. I’m sorry to have given the sensation that I did not search, which I indeed did. It was as simply as that I am moving to update1 and was trying to work the Morphine bugs BEFORE running the new 4.33 with U1, so the devicesorting.txt was not created yet, that’s why it did not appear in the folder and therefore I could not find it by any tried means. Your tip on the Bms Manual was valuable, have not thought of looking there.
By editing the order in the devicesorting.txt and manually putting the thrustmaster combined on top the problem was gone. Thanks for the inputs you all!By the way I want to congratulate you Red Dog on the manuals, I have the 4.32 printed and now will go with the 4.33u1 ones on lulu. Excelent work, and long live the VF-1.
-
I use Morphine’s profile and it works fine. Check your “devicesorting.txt” file to ensure the numbering is correct. It should look something like this:
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{00F2068E-0000-0000-0000-504944564944} "CH PRO PEDALS USB "I just need to add to or modify the keyfile to add the 4 new callbacks for the F-18.
Sniped…
Wait. So as long as thrustmaster combined is the first I can use this file to finally use my cougar mfds properly. Having them sit behind my second monitor when they work perfectly for DCS has been driving me nuts. I can’t wait to try this
-
Wait. So as long as thrustmaster combined is the first I can use this file to finally use my cougar mfds properly. Having them sit behind my second monitor when they work perfectly for DCS has been driving me nuts. I can’t wait to try this
Yup. I haven’t had to chase my device order since the “Devicesorting.txt” was introduced. As far as I’m concerned this was the greatest change in the entire update.
-
Now is there an easy way to switch left and right mfds? I have them set up to Velcro to a spare monitor and it works great in DCS but BMS is switching up the left and right and I don’t want to have to remove the padding and put Velcro in its place.
EDIT Well I just switched the order on Devicesorting.txt and didn’t even bother changing the MFD# and it worked. This has turned into a great day hehe.