Mud's Profile
-
Hey Artur,
Yeah, I can’t quite see anything you’d be doing wrong to be honest.
Just make sure those 2 files are not set to read only then. Especially not before you have set all your axis settings.
In BMS, where you select your controller, do you see and select Thrustmaster Combined? -
@Mud:
Hey Artur,
Yeah, I can’t quite see anything you’d be doing wrong to be honest.
Just make sure those 2 files are not set to read only then. Especially not before you have set all your axis settings.
In BMS, where you select your controller, do you see and select Thrustmaster Combined?Believe me Ive tried so many options In controller selection I see Thrustmaster Combined and its selected.
Got some clue:
Running script: C:\Users\Artur\Documents\T.A.R.G.E.T Profile\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[2]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\7&34F39FBF&0&4) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\7&34F39FBF&0&1) selected
USB HID device with hardware id “VID_044F&PID_b351” cannot be found <–--------- !!
USB HID device with hardware id “VID_044F&PID_b352” cannot be found <–--------- !!
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 <–--------- !!
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse…Donemain returned 0
-
I have some of those as well. I always figured they’re a TARGET thing.
Perhaps someone who has my script running without problems can confirm this?Running script: C:\Users\Mud\Desktop\BMS 4.32 Script\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: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
3: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
4: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\6&38A36D0C&0&3) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\6&38A36D0C&0&4) selected
USB HID device “F16 MFD 1”(USB\VID_044F&PID_B351\6&182A12DA&0&6) selected
USB HID device “F16 MFD 2”(USB\VID_044F&PID_B352\5&2301DF1D&0&3) 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
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse…Donemain returned 0
-
Updated to 3.01:
Fixed:
- Master arm switch
- Comm 1 & 2 transmit
-
After closer analysis I dont think “USB HID device… ble ble ble” ale problem.
First two cannot be found 'cos I dont have MFDs that’s obviously. Second part I mean “0400” and “B10A” have nothing to do 'cos your script work at yours TARGET/BMS thing. Something else causes the issue. hmmm… brain storm. -
I’m guessing i am doing something wrong as the stick functions are not working. All else works fine.
Added your key file to the config folder.
Loaded up the target script in the editor and ran it.
Opened up BMS and ensured all the axis were mapped correctly.
Loaded your key file.
Jump into sim and no stick functions, only trim.
Throttle works fine minus the air break.I’m pretty sure I’m doing something that isn’t right since I tried morphine’s profile and all the stick and throttle functions are bound to OBS buttons.
edit: my rudder pedals were listed in bms with (0) and the warthog as (1). Fixed buy running the script without the pedals plugged in and then plugging in the pedals, warthog is now listed as (0) and pedals as (1) and all controls function fine.
Also have the “device not found” but doesnt seem to be an issue as everything is working now.
-
Yeah, there seems to be a problem with device order (ID) and the DX mappings. I’m not sure if that’s a Windows or TARGET problem.
-
I had the same issues and fixed it by:
1. Uninstalling BMS 4.33
2. Installing BMS, don’t run it yet
3. Start the script and copy the keyfile to the right place
4. Start bms, load the keyfile and you’re done -
Updated to 3.02:
- Throttle support added for twin-engine planes
-
Hello Mud, file indicates 3.01 still. I’ve greatly appreciated your work & updates mate!
-
Thanks for pointing that out, Tagster. I had forgotten to update the hyperlink.
Fixed now -
I get the following error when trying to run the script. I have both TM MFDs and joystick/Throttle are connected. The only way to prevent the error is to unplug both MFDs prior to running the script.
Running script: C:\Users\pcarr\Desktop\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: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
3: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
4: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\6&18A05601&0&5) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\6&18A05601&0&6) selected
USB HID device “F16 MFD 1”(USB\VID_044F&PID_B351\6&18A05601&0&3) selected
USB HID device “F16 MFD 2”(USB\VID_044F&PID_B352\6&18A05601&0&4) 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
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse…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!**EDIT:**After I went back into BMS setup a few commands and marked joystick.cal and axis to read only it is calling out runtime error in main ( line 476 in target.tmh )
Looks like line 476 in taret.tmh is
char ledcmd[16]={3,3,3,2,3,0,1,0,3,3,3,3,3,1,3,3};
int ledproc(alias v, int p)
{
int k, j, i = p+2 & 0xffff;
if(p & KEYON)
if(v[i+1] == LED_INTENSITY) GameOutput(v_, OUT_ID_LED_INTENSITY, v[i+2]);
else if(v[i+1] == LED_ONOFF)
{
k = v[i+2] & 0xffffff ^ 0x555555; while(k)
{
p = ledcmd[k & 0xf];
if(p < 3) GameOutput(v_, OUT_ID_LED_BACKLIGHT+j, p); –LINE 476
k = k >> 4;
j = j+1;
}
}
}__ -
Which version of Windows are you running, Deadhand?
-
I too am having this issue with the axis and trim working on the stick and the look closer…but nothing else…running windows 10 and making sure all is done as administrator. I’ve deleted the MFD section in the target editor and I’ve changed the launcher section for me drive and it all works smooth except for the joystick issue…thanks Mud, it seems like a nice profile if I can just get it to work. I’m completely new to BMS, here from Cliffs of Dover and DCS and it just seems like such a great sim…I gotta get it working…
Thanks Mud, Salute!
-
One thing I had to do myself in Windows 10 is disable advanced power saving for my USB devices. Before I did that, TARGET was unable to find the Warthog.
Check this link on how to do it: https://support.microsoft.com/en-us/kb/2900614
-
Window 10
-
I reinstalled the MFD software from the Thrustmaster site and it seems to have fixed my issue.
Thank you for the Profile and the assistance MUD<salute!></salute!>
-
Interesting. I actually have never installed drivers for my MFD’s. In both W7 & 10 I just used the MS Drivers.
Perhaps not very wise, but at least they’ve always worked fine like that -
I don’t have or use the MFD’s and I’ve deleted all the MFD code, I’ve followed all other instructions yet I still can only get the “look Closer” switch and the trim and axis to work with the joystick. Is there something in the Mud.key or target script holding it up? I’m dying to learn this sim, thanks for the help:)
-
I have no idea what the cause of that is, Kushviper.
Someone in this thread solved it by doing the following: https://www.benchmarksims.org/forum/showthread.php?8844-Mud-s-Profile&p=340772&viewfull=1#post340772