Mud's Profile
-
Yes, I selected it. I can try profile in 3D world, that’s something what I didn’t check because I supposed that if profile isn’t working properly in setup will not work in 3D as well. Is very strange that this profile is working well https://sites.google.com/a/hodderweb.com/warthog/falcon-bms/home but because I have MFDs Cougars and your profile is tested for Falcon BMS 4.33 so, I would like to use it.
-
Okay, I have an issue. I’m flying BMS 4.33 U1
I have been flying Mud’s profile forever. I love it.
I have the Warthog suite and used to, until recently, use logitech g-940 pedals.I have replaced the pedals with the Thrustmaster T-rudder.
I see that the T-rudder is showing up in T.A.R.G.E.T. no problem.
I load my Mud configuration same as always in T.A.R.G.E.T., Then fire up BMS.
I go to settings to set up my flight controls and make sure the right axis is assigned as it should. No T-rudder is found.
If I leave BMS, unload the MUD T.A.R.G.E.T. profile, restart BMS and go to settings, the T-rudder controller is seen big as life but I need the T.A.R.G.E.T. mud profile running to get mud running.
If I load the MUD profile in TARGET and the MUD key file in BMS I naturally can’t used my rudders because under MUD they are not “seen” by BMS. Mud works fine.
What am I doing wrong here?
Is MUD not designed to work with TM pedals for some reason?Is this a controller sorting issue?
My devicesorting.txt:
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{B679044F-0000-0000-0000-504944564944} “T-Rudder”When engaging the TARGET mud profile it returns this:
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Physical USB HID devices managed by script!
Currently plugged USB HID devices[5]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
3: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
4: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
5: “T-Rudder” - “USB\VID_044F&PID_B679&REV_0110”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\6&3512E6DA&0&3) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\6&3512E6DA&0&4) selected
USB HID device “F16 MFD 1”(USB\VID_044F&PID_B351\6&3512E6DA&0&1) selected
USB HID device “F16 MFD 2”(USB\VID_044F&PID_B352\6&3512E6DA&0&2) selected
USB HID device with hardware id “VID_044F&PID_0400” cannot be found
USB HID device with hardware id “VID_044F&PID_B10A” cannot be found
USB HID device with hardware id “VID_044F&PID_B10B” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device “T-Rudder”(USB\VID_044F&PID_B679\5&2AB8F5ED&0&1) selected
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
-
SOLVED!
If anyone has the problem here is what you do.
1.Detach your TM pedals from the system. Physically pull the socket out of the USB.
2. Connect all your OTHER TM devices EXCEPT your pedals.
3. Load TARGET.
4. Load the TARGET Mud profile.
5. DO NOT load BMS yet.
6. Connect your pedals.
7. Load BMS.Your pedals will now magically appear in the axis set up menu.
Your Mud controls will 100% work in the cockpit.
Your pedals will work like a charm.
-
SOLVED!
If anyone has the problem here is what you do.
1.Detach your TM pedals from the system. Physically pull the socket out of the USB.
2. Connect all your OTHER TM devices EXCEPT your pedals.
3. Load TARGET.
4. Load the TARGET Mud profile.
5. DO NOT load BMS yet.
6. Connect your pedals.
7. Load BMS.Your pedals will now magically appear in the axis set up menu.
Your Mud controls will 100% work in the cockpit.
Your pedals will work like a charm.
You can edit the script to exclude the pedals from the script, which you are essentially doing by connecting them after running the script.
See post #417 and edit the script to exclude the pedals, it’s the Configure(&TFRPRudder, MODE_EXCLUDED); line that needs added for the pedals.The devicesorting should have Thrustmaster Combined as the top line
If you have the MFD’s, the next line is F16 MFD 1 and the third F16 MFD 2
Then the rudders, everything else can be below those lines{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{B679044F-0000-0000-0000-504944564944} “T-Rudder”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog” -
I just upgraded to the Warthog HOTAS from the T1600 HOTAS. After running this profile in the Target script editor and loading the key file, everything works as expected for the Warthog throttle, but the flight stick didn’t have any input working which didn’t seem like a big deal at first as I could manually add it. But when going to Stick controller keys (section 5.11), only three are available, the same ones that only Zenith could see:
No Key Assigned - REM: Trim-Reset (change @ CKPIT)
No Key Assigned - STICK: PINKY/SWITCH (DX SHIFT)
Alt a - STICK: PADDLE SWITCHAnd here is the updated rearranged DeviceSorting.txt file, still not having any luck
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Virtual Game Controller (root)”
{C0F2068E-0000-0000-0000-504944564944} “CH Pro Pedals USB”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{B10A044F-0000-0000-0000-504944564944} “T.16000M”
{B687044F-0000-0000-0000-504944564944} “TWCS Throttle” -
I just upgraded to the Warthog HOTAS from the T1600 HOTAS. After running this profile in the Target script editor and loading the key file, everything works as expected for the Warthog throttle, but the flight stick didn’t have any input working which didn’t seem like a big deal at first as I could manually add it. But when going to Stick controller keys (section 5.11), only three are available, the same ones that only Zenith could see:
No Key Assigned - REM: Trim-Reset (change @ CKPIT)
No Key Assigned - STICK: PINKY/SWITCH (DX SHIFT)
Alt a - STICK: PADDLE SWITCHAnd here is the updated rearranged DeviceSorting.txt file, still not having any luck
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Virtual Game Controller (root)”
{C0F2068E-0000-0000-0000-504944564944} “CH Pro Pedals USB”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{B10A044F-0000-0000-0000-504944564944} “T.16000M”
{B687044F-0000-0000-0000-504944564944} “TWCS Throttle”Please make sure you test in the 3D world with my key file, and not just in the setup of BMS.
-
Haveing trouble downloading profile, it just says that the file is unrecognized?? any ideas? Thanks
-
Haveing trouble downloading profile, it just says that the file is unrecognized?? any ideas? Thanks
The script doesn’t run on Target GUI, it needs to be started from the script editor. Are you using the correct program?
Verstuurd vanaf mijn F5121 met Tapatalk
-
Haveing trouble downloading profile, it just says that the file is unrecognized?? any ideas? Thanks
The files are packed in a Rar archive. You’ll need a program like WinRAR or 7zip to extract them.
-
Hi Mud,
First of all thank you for your profile! i have been using it for the past 4 (Falcon BMS 4.33) months and it’s been working great! I would like to do some modification to it and i need your help:
- I would like to switch the pinky button and the master mode back to their original settings
- I would also like to insert the IDM A-A transmit on the MIC switch up (should be SimCommsSwitchLeft) and IDM A-G FCR transmit on the MIC switch down (should be SimCommsSwitchRight)
Any ideas on how to do that? Will i have to modify the .tmc file and the .key file to get it to work?
Thanks in advance for your help!
-
Hi Mud,
First of all thank you for your profile! i have been using it for the past 4 (Falcon BMS 4.33) months and it’s been working great! I would like to do some modification to it and i need your help:
- I would like to switch the pinky button and the master mode back to their original settings
- I would also like to insert the IDM A-A transmit on the MIC switch up (should be SimCommsSwitchLeft) and IDM A-G FCR transmit on the MIC switch down (should be SimCommsSwitchRight)
Any ideas on how to do that? Will i have to modify the .tmc file and the .key file to get it to work?
Thanks in advance for your help!
Hey,
For you first question you can just change this code:
//************************** //*** TM Warthog Stick *** //************************** //Master mode Button: Cycle FOV MapKey(&Joystick, S1, PULSE+DX3); //Pickle Button MapKey(&Joystick, S2, DX2); //Pinky Button: Missile Step / NWS / AA Disconnect MapKey(&Joystick, S3, DX5);
To:
//************************** //*** TM Warthog Stick *** //************************** //Master mode Button: Cycle FOV MapKey(&Joystick, S3, DX5); //Pickle Button MapKey(&Joystick, S2, DX2); //Pinky Button: Missile Step / NWS / AA Disconnect MapKey(&Joystick, S1, PULSE+DX3);
As for your second question:
Unfortunately I don’t have the time to do that for you now, but you could just change the code for those buttons to give the keyboard command for the SimCommsSwitchLeft and SimCommsSwitchRight.Best regards,
Mud
-
@Mud:
Hey,
For you first question you can just change this code:
//************************** //*** TM Warthog Stick *** //************************** //Master mode Button: Cycle FOV MapKey(&Joystick, S1, PULSE+DX3); //Pickle Button MapKey(&Joystick, S2, DX2); //Pinky Button: Missile Step / NWS / AA Disconnect MapKey(&Joystick, S3, DX5);
To:
//************************** //*** TM Warthog Stick *** //************************** //Master mode Button: Cycle FOV MapKey(&Joystick, S3, DX5); //Pickle Button MapKey(&Joystick, S2, DX2); //Pinky Button: Missile Step / NWS / AA Disconnect MapKey(&Joystick, S1, PULSE+DX3);
As for your second question:
Unfortunately I don’t have the time to do that for you know, but you could just change the code for those buttons to give the keyboard command for the SimCommsSwitchLeft and SimCommsSwitchRight.Best regards,
Mud
Thank you so much for the quick response! I will substitute the script right away! if you should find the time in the future i will be watching this thread
Thanks
-
Hi, Thanks for the profile Mud, I am learning BMS and am using it. I’m trying to modify it for a rookie to bms like me.
I have set Autopilot on/off to the Engage/disengage button, Landing gear to gear horn button and (I think) redone flaps.One thing I’m struggling with is this:
I have set the paddle switch (S4?) to the shift (I/O?) key, and I wanted to make:
Trim hat to Trim hat when unshifted and look around the cockpit (padlock?) when shifted
DMS hat to DMS hat when unshifted and Track IR Zoom in, Zoom out, Pause and reset when shiftedCan anyone help?
PS, I’ve skipped Tutorial one (yes, I know) and start Tutorial 2 on the Runway. I can set comms to speak to tower. When I move the throttle over idle detente and to A/b….the engines go on…and then out and everything shuts down. Any idea what is going on?
-
Hello Mud.
After running Target Script Editor - shows the error:
Running script: C:\Users\castor\Desktop\BMS 4.33 Script - Mud v3.06\BMS 4.33 - Mud.tmc
Compile Error: File not found: target.tmh in BMS 4.33 - Mud.tmc at line 1
widows 10 64bit.
Target _v3016(615v2) and Target_v1.0 -
Hello Mud.
After running Target Script Editor - shows the error:
Running script: C:\Users\castor\Desktop\BMS 4.33 Script - Mud v3.06\BMS 4.33 - Mud.tmc
Compile Error: File not found: target.tmh in BMS 4.33 - Mud.tmc at line 1
widows 10 64bit.
Target _v3016(615v2) and Target_v1.0My first guess would be to try and reinstall Target really. Seems to be a problem there somehow.
-
Hello Mud.
After running Target Script Editor - shows the error:
Running script: C:\Users\castor\Desktop\BMS 4.33 Script - Mud v3.06\BMS 4.33 - Mud.tmc
Compile Error: File not found: target.tmh in BMS 4.33 - Mud.tmc at line 1
widows 10 64bit.
Target _v3016(615v2) and Target_v1.0Put the script in the Target script directory.
Usually at C:\Program Files (x86)\Thrustmaster\TARGET\scripts if you installed it normally.
That’s where target.tmh is located. -
Put the script in the Target script directory.
Usually at C:\Program Files (x86)\Thrustmaster\TARGET\scripts if you installed it normally.
That’s where target.tmh is located.You’re big - problem solved thx
-
Hi Mud,
I transferred BMS 4.33 to a Win10 Home system because my Win7 Pro puked. I’ve installed the latest Target software from their site, and downloaded your latest .tmc file. When I attempt to run the script through the script editor, it stops:
Running script: C:\Program Files (x86)\Thrustmaster\TARGET\scripts\BMS 4.33 - Mud.tmc
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[4]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
3: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
4: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\6&2F5EE2A6&0&4) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\6&2F5EE2A6&0&2) selected
USB HID device “F16 MFD 1”(USB\VID_044F&PID_B351\7&B30CBC7&0&1) selected
USB HID device “F16 MFD 2”(USB\VID_044F&PID_B352\7&B30CBC7&0&2) selected
USB HID device with hardware id “VID_044F&PID_B10B” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B679” cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
Error:One of the selected USB devices (2) has been unplugged. Aborting script!
Aborting script (check output above for reason)…
Script stopped!
I have no idea what hardware it thinks has been unplugged, because all of my USB devices are plugged in and functioning properly…this is a head scratcher…any ideas to solve this problem? Everything was working fine on the Win7 rig…could it be Win10’s notorious USB problem?..I have the latest build of Win10…still doesn’t make sense because all devices are recognized by the OS and functioning normally otherwise.
Thanks for any ideas you or anyone else may come up with…
Burner59 -
I’ve had this happen also because of the Windows power management powering down the devices.
Might be worth giving this a shot:
https://support.microsoft.com/en-us/help/2900614/some-usb-devices-do-not-recharge-in-windows-8.1Br,
Mud
-
Hi Mud,
No go - the entries:
USB HID device with hardware id “VID_044F&PID_B10B” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B679” cannot be foundcould not be found anywhere in the Windows Registry, and they seem to be what is preventing the script from executing completely. I also checked every hardware ID and device instance path, and those entries do not exist on my system.
Another weird thing - my Saitek rudder pedals are “seen” by BMS, but do not show any movement in the controller setup screen, with them as the selected hardware.
Any ideas?
Thanks,
JB