Mud's Profile
-
I did that now, still no go - bombs out with the same errors listed above……weird, man…I don’t know why it’s trying to find those three HW devices that are not on my system anywhere…
-
That’s pretty weird.
Are you using the newest version of TARGET, or the older one? -
I had something similar happen to me when I was running on win 10. In my case, after this problem, if I went to check the hardware in windows, the throttle had a yellow exclamation mark next to it. I solved the problem by downloading the latest drivers at the TM website. The standard windows driver for the throttle was causing the problem in my case.
Verstuurd vanaf mijn F5121 met Tapatalk
-
Hi Mud - I’m using the latest version of the Target software, newly downloaded from their site last week….I think I still have the installer for the previous version. Which version are you using?
Hi Terminator - All of my hardware devices are working normally in Win10, no problems.
…that’s why I can’t figure this one out…it doesn’t make sense…
JB -
I swore by the old version up until I started having problems myself, and downloaded the newest one to ensure W10 compatibility.
-
I use a modified Morphines profile but just downloaded this one and have the same error as Burner59.
Is there a reason that the 5 devices with // below are not “excluded” from the profile?
//Configure(&LMFD, MODE_EXCLUDED); //Configure(&RMFD, MODE_EXCLUDED); Configure(&HCougar, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); //Configure(&TWCSThrottle, MODE_EXCLUDED); //Configure(&TFRPRudder, MODE_EXCLUDED); //Configure(&T16000L, MODE_EXCLUDED);
Running script: D:\Users\David\Downloads\BMS 4.33 Script - Mud v3.06\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: "F16 MFD 2" - "USB\VID_044F&PID_B352&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: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\5&36488FA&0&7) selected USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\5&36488FA&0&8) selected USB HID device "F16 MFD 1"(USB\VID_044F&PID_B351\5&36488FA&0&6) selected USB HID device "F16 MFD 2"(USB\VID_044F&PID_B352\5&36488FA&0&5) 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)...Done main returned 0 Error:One of the selected USB devices (2) has been unplugged. Aborting script! Aborting script (check output above for reason)... Script stopped!
If you run it with them excluded it seems to work properly.
Configure(&LMFD, MODE_EXCLUDED); Configure(&RMFD, MODE_EXCLUDED); Configure(&HCougar, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); Configure(&TWCSThrottle, MODE_EXCLUDED); Configure(&TFRPRudder, MODE_EXCLUDED); Configure(&T16000L, MODE_EXCLUDED);
Running script: D:\Users\David\Downloads\BMS 4.33 Script - Mud v3.06\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\5&36488FA&0&7) selected USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\5&36488FA&0&8) 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)...Done main returned 0
-
Hi TxMbt - I tried your suggestion, and it worked - the script ran ok. But I had to go back and exclude both MFDs again to make those work (since I have a pair of them):
//Configure(&LMFD, MODE_EXCLUDED);
//Configure(&RMFD, MODE_EXCLUDED);
Configure(&HCougar, MODE_EXCLUDED);
Configure(&T16000, MODE_EXCLUDED);
Configure(&TWCSThrottle, MODE_EXCLUDED);
Configure(&TFRPRudder, MODE_EXCLUDED);
Configure(&T16000L, MODE_EXCLUDED);
THANK YOU!!! It makes sense now, because I don’t have those pieces of hardware on my system that were causing the script to crash, so they should be excluded….I missed that bit of logic before.
One thing still remains unsolved - it doesn’t spawn the launcher with this code:
//Launch Falcon BMS 4.33
system(“spawn -w “D:\Falcon BMS 4.33” “D:\Falcon BMS 4.33\Launcher.exe””);Everything is pointing to the correct path, as I have it installed in D:\Falcon BMS 4.33\Launcher.exe
I have to fire up the launcher manually, but that’s not a show stopper…the main problem is solved!
Any ideas on getting the launcher to execute automatically?
Thanks again!!!
JB -
Hey Jim,
The line should be:
system("spawn -w \"D:\\Falcon BMS 4.33\" \"D:\\Falcon BMS 4.33\\Launcher.exe\"");
Best regards,
Mud
-
Hi Mud - I copied your line above to replace what I had…still does not launch…?? I’ve looked at the section in the TSE manual on page 36, and your code syntax is indeed correct, so this is another mystery…only possibility I can think of is that my D drive is named Data (D:), but that shouldn’t matter as the code just references the drive letter…
JB -
Not that it’s a big thing, because I actually turned off the auto-launch in my own script cause sometimes I just run the script and stop it to turn off the lights of my throttle.
But anything, the two things I can think of that could cause it are:
- the line is commented out by // and therefor not being executed.
- Your path is not D:\Falcon BMS 4.33
Mud
-
I agree, it’s not a big deal at all, I just run the launcher separately, too. To your two points - it is not commented out, and my path is D:\Falcon BMS 4.33, so it’s just bizarre
Thanks for your script once again, Mud
Jim -
Hey guys,
Havent played F4 om about 4 months. Got on tonight and the profile is acting up.
For example, on the master arm switch, it only activates when the (Flow R) switch is clicked up and not down.
Which means I have to cycle it 3 times before getting it to the position I want.
Any ideas?TIA
-
I’m not sure if I quite understand the problem, but the way the switch is set up is:
Up = Master Arm ON
Down = Master Arm OFFIt’s not set up as a toggle switch.
-
Hi Mud,
Sorry I’m probably not explaining it well.
Only when I flick the switch up, does the master arm cycle.
So if the master arm is on, and I want to switch it to off, I have to toggle the switch down and back up(goes to sim)
Then down and back up again for it to go to off.Does that explain it a bit better?
-
Yup, I get it now
Can you check in the TARGET Script Editor Event Tester if the switch passes a command on both up and down?
If it does there, my guess is that something is wrong with the key file then in BMS.Br,
Mud
-
Yep, passed a command both up and down.
Replaced the Key file and all is back to normal!Thanks Mud!
-
This was a massive help in getting started with the Warthog HOTAS, thanks for sharing Mud
Had a few issues with the MFD’s which initially caused a USB disconnect error when running any of the TM profile scripts. Turned out to be caused by the latest Win 10 64 bit patch activating some USB power management settings behind the scenes. Once I disabled them all was well. Just waiting for the Thrustmaster flight pedals to arrive and then my setup is complete (for now, at least…).
I bought F4 when it first came out and can’t believe how far it’s moved on thanks to the dedication and hard work that the BMS Team have invested in it. Well done guys and thanks very much.
-
Post removed ––answer found—
-
Sorry for the late reply. I was on holiday.
While I’m happy you found the solution. It may have been a good idea to leave your problem and solution right here in your post, as others may also encounter it as well.
If you still have it in the back of your head, it may help others to edit your post againBest regards,
Mud
-
Hello MUD
I have a litle problem here that i hope you can help me with.
First im running with Win /.
Gear.
Thrustmaster Warthoc, 2 MFD, Bu0836X from leo bodnar:
I have installed Falcon 4 and BMS, on my E: drive.
Im running lates T.A.R.G.E.T dowloaded from thrustmaster.
I paste the Mud.Key in this folder E:\falcon bms\Falcon BMS 4.33 U1\User\Config
and the Mud.tmc in this folder C:\Program Files (x86)\Thrustmaster\TARGET\scripts
I Run the Target script and get this info.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: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
3: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
4: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\7&9D9F79B&0&4) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\8&33A019CC&0&2) selected
USB HID device “F16 MFD 1”(USB\VID_044F&PID_B351\7&9D9F79B&0&2) selected
USB HID device “F16 MFD 2”(USB\VID_044F&PID_B352\8&33A019CC&0&5) 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)…DoneIn my Devicesorting.text the list is like this
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster combined”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{076306A3-0000-0000-0000-504944564944} “Saitek Pro Flight Rudder Pedals”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 2”
{10011DD2-0000-0000-0000-504944564944} “BU0836X Interface”Then i launch Falcon BMS and open the controler.
Keyboard
Thrustmaster Virtual Game Controller ( root)
Saitek Pro Flight Rudder PedalsIn BMS i load MUD and apply, and set controller in advanced.
Some of the botton in the throttle dont work and no key from Mud is showing up atall???Im really confused and hope you can help