Mud's Profile
-
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 -
Try setting all USB devices to EnhancedPowerManagementEnabled = 0 in your registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\
That’s basically what I had to do at some point and it sorted my problems.
-
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.