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
Latest posts made by Burner59
-
RE: Mud's Profile
-
RE: Mud's Profile
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 -
RE: Mud's Profile
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 -
RE: Mud's Profile
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 -
RE: 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…
-
RE: Mud's Profile
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 -
RE: Mud's Profile
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 -
RE: Extreme amount of thrust required to move on the ground
Thanks, Gentlemen, that was indeed the problem - reversed the brakes, and all is well!
Burner59 -
Extreme amount of thrust required to move on the ground
Hi All,
After installing BMS on a brand new system, everything works fine with one exception - in order to move on the ground, an extreme amount of thrust is required to begin and continue taxiing, cracking into the afterburner. This is not right! I’ve set my controller hardware up the way it was before (Thrustmaster Warthog and Saitek Pro Rudder pedals). Does anyone know what may be causing this problem? (I had it working fine on the old PC.)
Thanks,
Jim aka Burner59