Mud's Profile
-
Hiya guys, I have the Warthogs and use Mud’s profile (great work btw) I want to get some rudder pedals, the set I have my eye on are the THRUSTMASTER TFRP Flight Rudder , are these compatible with the Warthogs AND BMS 4.33
Thanks in anticipation
Aim
-
I have also emailed Thrustmaster support and will report back my findings……
-
Well I got a standard “They will work with the Warthogs but we cant comment on BMS” reply from Thrustmasters tech support.
I am hopeless with scripts and haven’t touched Mud’s profile, does anyone know how I can bind the TFRP T.Flight Rudder pedals to Muds profile? I calibrated the rudders using Thrustmasters program, plugged them in but they wouldn’t steer or brake on the taxi way. Any help would be really appreciated.
Aim
185th Cadet -
Well I got a standard “They will work with the Warthogs but we cant comment on BMS” reply from Thrustmasters tech support.
I am hopeless with scripts and haven’t touched Mud’s profile, does anyone know how I can bind the TFRP T.Flight Rudder pedals to Muds profile? I calibrated the rudders using Thrustmasters program, plugged them in but they wouldn’t steer or brake on the taxi way. Any help would be really appreciated.
Aim
185th CadetI use the Warthog and TFRP pedals also with BMS. I’m using DX assignments mostly and my own little Target profile for where DX won’t work. The TFRP pedals I have setup in windows and in BMS self of course, they are not included in the profile. Works fine for me, this way.
-
Really appreciate the reply Terminator, I’m a real newbie on BMS, used to fly F4 back in 2002 for three years then moved on, I’m also a bit of a newbie about DX assignments etc…. Am I right in thinking if I setup the rudders in windows and BMS (not sure how to do that) then they shhould work with Mud’s profile, I do use the TARGET software to run his profile? Apologies for not really understanding your advice.
Regards
AIM
185th Cadet -
Hey OldAim,
Indeed you should just set up your rudders in Windows and BMS. You may have to edit out this line in the beginning of my script: Configure(&TFRPRudder, MODE_EXCLUDED); by adding // in front of it.
My script itself you should run with the Target Script Editor, not the Target GUI.
Best regards,
Mud
-
Ah ha the man himself Got to say I love your profile Mud, thank you for all the hours you must have put in. I have run the rudder driver for windows and attached a piccy of whats showing in my windows devices, did I get that bit right?
In the BMS config launcher window, do I enable virtual rudder (pic attached) I’m a real novice and haven’t dared to fiddle with your profile until I feel competent enough, how do I edit the script? Do I use notepad or wordpad to find that line and just put two forward slashes in front then save the file?
Best regards
Old and Ancient AIM
185th cadet -
I just got brave and went to edit mode in the TARGET software, looks to me like the two forward slashes are already in front of that command line.
-
Oh and I did enable virtual rudder in the BMS configuration, tried it out quickly on a TE on taxi way but the rudders are not steering or braking As you can probably tell I havent a clue …. lol
-
Yeah, in the BMS launcher you need to leave that virtual rudder to default - so off I guess.
Check page 1, post 9 how I set up my former Saitek combat pedals in the BMS settings: https://www.benchmarksims.org/forum/showthread.php?8844-Mud-s-Profile&p=155588&viewfull=1#post155588
-
Ah I was configing it in the wrong place on BMS, thanks very much for the link Mud and all your help, trying to taxi n brake using the keyboard is a mare lol
-
I went into the right BMS config as per your pic (I printed the pic out as a reference), set it all up and checked it all, working lovely…… Came out of BMS, ran your profile via Target, back into BMS and it didn’t work, with TARGET running there are only two options, keyboard and mouse, Any ideas what I have done wrong?
-
I would assume because Target adds to rudders to a virtual device. Not sure as I’ve never used those.
See what happens when you remove the // before Configure(&TFRPRudder, MODE_EXCLUDED);
Edit: This post could also be of relevance to you: https://www.benchmarksims.org/forum/showthread.php?8844-Mud-s-Profile&p=448492&viewfull=1#post448492
-
Thanks Mud, I shall give that a go, test it out and check that thread out… I shall report my findings back on this thread if thats ok with you……
-
That worked a treat Mud, you are indeed “The Man” Great fix, so so thankful to you…… Just removing the two forward slashes was the fix.
Best Regards
Aim
-
Sorry to be a pain Mud, on the hat switch that clicks up for AWACS declare forward for Uniform and back for Victor, I noticed the down click is showing as N/A on the diagram you made, I would like to use VAC as a comms device to keep off the keyboard as much as possible, how do I set that down hat switch as a hot key that will activate VAC? When I am in BMS controller set up I notice that hat switch comes up with button 21 when pushed forward and button 20 when pulled back, the N/A down position is button 29 on the BMS controller page, so I guess I am asking how to assign button 29 to (right) ALT+V, that is the hot key on the VAC BMS profile I was given.
Regards
Aim
-
For ALT+V you’d have to add the following to the //Mic Switch Section
MapKey(&Throttle, MSD, PULSE+L_ALT+USB[0x19]);
-
Thanks again Mud, I’ll admit to not being that great at editing profiles…. I have had a go and added the line, is it in the right place? I hit the return key after adding the line to separate the next section…
Here is a screen shot of what I done… Sorry to keep bugging you… I did try google etc and I am not sure any pilots in the 185th have warthogs with your profile so I am kinda on my own…
Thanks again for taking the time to reply and supply the right code
-
I obviously didn’t do it right as when I loaded the profile with the changes the auto pilot toggle wouldn’t turn the lights on and off on the throttle… So I am guessing it wasn’t right… See I said I was useless at this lol
I have removed the line and saved the TMC file, ran TARGET again and the sticks are back to normal. Next time I will choose “save as” after an edit so I don’t balls it up again…
-
I had another crack at it and placed that code you supplied over the top of the last unused one with the two slashes and it has appeared to work, I used “saved as” and called it Mud button down 29.tmc and ran the script, when I started BMS the controller page reports button 29 as ALT+V
Thanks ever so much
Aim