Mud's Profile
-
thanks for the reply jc1.
after putting those 4 lines I still get these:USB HID device with hardware id “VID_044F&PID_B10A” 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 foundwhat are those devices?
VID_044F&PID_B679 is Thrusmaster Rudder Pedals. Remove the line with Configure (&TFRPRudder, MODE_EXCLUDED);
I thought VID_044F&PID_B10A was T16000, so I don’t know why you still get the line with “cannot be found”
I don’t know what VID_044F&PID_B687 is.The VID portion of the code identifies the device manufacturer and PID is the specific code for a product of the device manufacturer. 044F is the code for Thrustmaster. And the PID is the code for the various Thrustmaster devices. It’s hard to get an answer if you communicate to Thrustmaster, but good luck if you try. It doesn’t mess up anything if those “cannot be found” lines appear in the TARGET script output.
-
Hi jc1,
Thanks a lot for the explanation.
because it doesn’t mess up anything,
I won’t bother contacting TM since its customer support is the worst of all. -
Hi to all!
I using Hotas warthog and rudder, but BMS doesn’t recognize the rudder.
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{B679044F-0000-0000-0000-504944564944} “T-Rudder” -
Haven’t used his profile but I guess its because Script combines T-Rudder pedal without assigning any axis.
Configure(&TWCSThrottle,MODE_EXCLUDED); Configure(&TFRPRudder,MODE_EXCLUDED);
Add these line to .tmc file.
-
Hi, I’m fairly new to using TARGET so please bear with me:
After commenting out all of the MFD portions of the tmc I compiled the script and ran it.
After loading falcon I switched the joystick to the virtual one and imported the keyboard file.Here is where things mess up for me:
Some of the keys function correctly, such as the china hat and boat switches, but others do not such as the slew control, master mode, or speed breaks.
Any ideas what is up here? -
Thanks!
-
Hi to all!!
The rudder is working now, but some bottoms from the stick are not working, like DMS or tms switch; also I can’t active NWS, I can’t active it. -
I’m not sure what I’m doing wrong, but I load file in correct place. I setup my axis and then exit and make my axis assignments file read only. I then load the script as instructed. Run BMS and test. All axis works, but I’m missing lots of button assignments like MSL step switch, all buttons on stick, and half of switches on throttle. The switches on throttle panel work as advertised.
I go to the controller page and test and there are no assigned functions for these buttons and switches, however I can’t assign the correct functions because they are not present in the list.
Sent from my iPad using Tapatalk
-
Deleted
-
Hi to all!!
The rudder is working now, but some bottoms from the stick are not working, like DMS or tms switch; also I can’t active NWS, I can’t active it.I checked the devicesorting.txt file as recommended by several members. I fixed mine by checking that file and moving the combined warthog line to the top line in that file. Try that and see if that fixes yours as well.
-
Hi
thanks for this amazing profile
Thanks
-
Hi Mud,
i´m rejoining the BMS community since years, last times I flew AF and now I found your profile but it´s not working properly for me.
Most of the functions do not work for me, e.g. the air brake, or the mic switch (both on the throttle), or the pinky button on the stick.To be honest, I use TARGET for the first time, as I do not use it Prepad3 SIM, which I also fly.
What I did:
copied AND loaded the BMS keyfile (keyboard)
opened TARGET under “fly now” -> add:
“title: BMS
path: launcher.exe from the BMS direrctory
working directory = the bms main directory
associate configuration: your target script BMS4.33-Mud”
Then I hit “fly now” and your script is being loaded.Then I start BMS etc….
I don´t know what I can do, because I´m not really familiar with the software.
Can you please help me?
Thank you very much!
EDIT:
Just opened the game controller settings for the stick to check the pinky button. When I press the pinky button on the stick the red 3 flashes. Does this mean, that it is DX 3 ?
In your script this is set to DX 5.
And does it mean I have to change all the DX numbers according to my numbers in the game controller settings for the stick and throttle?This is just speculation from me!!
-
Hey Gustav,
You shouldn’t have to change anything.
Though I think it’s best to load the script in the TARGET Script Editor and run it in there (ie: the play button).
Once it’s loaded then start BMS.See if that resolves anything.
Br,
Mud
-
Good morning Mud,
thanks for your hint! I´ve just tested the script and loaded it via Target Script error, it says compile succesful, but still the same problems, airbrake not working, etc.
(However the canopy switch works for example, as it did before).I do not have the MFDs at the moment, but I didn´t erase the lines in the script, could this be the case?
What else could be wrong?
-
Hey Gustav,
I’m pretty sure the MFD code is not the problem, but I’d delete those lines or comment them out with // in either case.
You can test the Event Tester in the TARGET script editor. The paddle switch should show the ‘L’ key then.
If that is showing up correctly, then it would appear you didn’t load the key file properly in BMS.Br,
Mud
-
Ok, I´ve tested the paddle switch and it shows “L” indeed.
The airbrake, for example, isn´t recognised, as well as the pinkie button.I copied the key file “BMS 4.33 Mud.key” into the falcon dir./user/config dir. and loaded it in BMS.
Still not working…EDIT:
I opened BMS and checked the key file, pushing the paddle switch shows “L - looking closer”, pushing the pinkie button shows “no funtion assigned”… -
It’s normal afaik that some don’t show up, as they’re DX functions. But they will function in the cockpit.
Did you try there, or just at the key stroke settings?
-
I tried in the cockpit, no funtion.
-
That’s mighty strange.
Just tested on my end again and everything is working as it should.
Your controller in BMS is set to Thrustmaster Virtual Game Controller (root) - or something similar?
And in DeviceSorting.txt (BMS User\Config), that one is on top of the list? -
Without the TARGET script the BMS menu describes the warthog as"Joystick-Hotas Warthog" and “Throttle-Hotas Warthog”,
with the script enabaled it says “Thrustmaster combined”.the devicesorting.txt:
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{076506A3-0000-0000-0000-504944564944} “Pro Flight Cessna Rudder Pedals”
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”