Mud's Profile
-
Ok thanks , I will try that for the throttle lights.
As for the auto pilot , I figured it out, I just had to set a key to the " MISC-pitch switch cycle (also combat pilot) " in the controllers settings.Thanks for the help.
-
Hi Mud,
Thanks for your profile.
After fixing DeviceSorting.txt by putting thrustmaster combined on top,
it seems to work.However, I notice all buttons that have dx assignments when I push it in the game, I get only button 1, 2, 3 etc.
Is this correct?all other buttons with no dx assignments:
- on throttle: autopilot, radar ±, tilt up down, dogfight/missile override, waypoint ±
- on joystick: look closer
seem to work well.
So I have to reprogram within the game all dx assignment buttons:
- all buttons on the joystick except “look closer”
- on throttle: speed brake and mic switch
?
Is this correct?
Sorry if this a noob question.
Please advise.
-
Hey tirta,
It is indeed normal that a number of buttons have DX assignments. You shouldn’t have to do anything yourself.
Just load my key file in BMS and all buttons should work as shown in the diagram that comes with my script.Try it out in the cockpit and I’m pretty sure you’ll find everything working as it should.
Br,
Mud
-
Thanks Mud.
It is indeed working in the cockpit.So the assignment for dx button is inside the key file.
Why not assign it straight like autopilot, radar + - ,etc ?Is it better to assiign it like this?
-
Yeah, they’re in the key file as far as I remember. Also in the default key file.
They offer advantages, but are not unlimited in number. -
So I did a complete new install of BMS tonight and new TARGET software and drivers. I’m using your latest profile with the right key file in the config but when I go in to set up the stick none of the buttons show up. It says the button number and says it’s unassigned.
Any ideas?
Thanks!
-
Hey Wicked,
Is your DeviceSorting.txt set properly?
Br,
Mud
-
Yes it is now. However now when I load the profile it will only work with the Full Key.key file. Mud.key barely loads any call backs to the stick and throttle but the MFD’s work fine… lol.
-
I’m good to go. I ended up using Morphine’s and all is well with my BMS WORLD!
-
Hey guys, coming from DCS (A-10C) and am an abosute newbie. In the A-10C the the DMS key on the joystick can zoom in/out the TGP.
Is that function not avaiabe on the F16 (using MUD’s profie)?
Edit: TH Target Script disabed my Lower case “L”
Edit 2: Nevermind. Its my Slider -
Hi Mud,
I notice I get lots of “cannot be found” message:
Running script: F:\thrustmaster\BMS 4.33 - Mud.tmc
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: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
2: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\8&1CA09029&0&4) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\8&1CA09029&0&2) 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
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 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
I have erased all TM Cougar MFDs code since I do not have them.
so which usb devices can not be found?
can you explain? -
Hi Mud,
I notice I get lots of “cannot be found” message:
Running script: F:\thrustmaster\BMS 4.33 - Mud.tmc
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: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
2: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\8&1CA09029&0&4) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\8&1CA09029&0&2) 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
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 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
I have erased all TM Cougar MFDs code since I do not have them.
so which usb devices can not be found?
can you explain?I had this on mine too but it doesnt affect the operation of the HOTAS. Simply open the devicesorting file and ensure that virtual controller (if “Thrustmaster Combined” is not available) is at the top.
Go into the controller setup screen in F4 and ensure that virtual controller is also selected.
Everything else should work as intended.
-
yes, it seems everything works.
however, I still would like to know what causes these “cannot be found” messages.
-
yes, it seems everything works.
however, I still would like to know what causes these “cannot be found” messages.
Try putting this in your TARGET code, after “int main()
{”Configure(&HCougar, MODE_EXCLUDED);
Configure(&T16000, MODE_EXCLUDED);
Configure(&LMFD, MODE_EXCLUDED);
Configure(&RMFD, MODE_EXCLUDED); -
@jc1:
Try putting this in your TARGET code, after “int main()
{”Configure(&HCougar, MODE_EXCLUDED);
Configure(&T16000, MODE_EXCLUDED);
Configure(&LMFD, MODE_EXCLUDED);
Configure(&RMFD, MODE_EXCLUDED);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?
-
I’ve had stuff like that show up from the very start, and everything was working the way I wanted it to.
So I never bothered wasting time into tracking them down.Don’t try to fix that which isn’t broken
-
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.