Mud's Profile
-
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
-
Glad to hear you got it sorted
-
Only because you gave me the right script That now leaves the AWACS declare spare, is there any documentation I can read so I can try for myself or is it a programmers language, I dont want to keep bugging you Mud.
Best Regards
Aim
-
Itâs actually not that hard. Just find the button you want to map a key to, and then look up the USB code in the TARGET_SCRIPT_EDITOR_basics.pdf (page 55) file located in C:\Program Files (x86)\Thrustmaster\TARGET\Resources\ and put that code at the desired button action in the script.
If you have trouble with it then just let me know which key you want bound to what. Just donât expect me to redo the entire script
Br,
Mud
-
I will give that a go Mud tyâŚâŚ And no I wouldnt expect you to redo all that work
I bought some Thrustmaster MFDs today, installed the driver for them, plugged them in and they both lit up⌠I had to re start the PC, I ran the TMC script and only one MFD lit up, I popped into BMS and the lit one doesnt change anything⌠I looked at the script that I ran and saw these lines
//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);I am guessing? I need to change something?
Is it take away the two forward slashes on the top two lines?
Again sorry for being a pain in the bumâŚ
I will check out that document you mentioned too and see if I can work it out for myself, if I can I shall report back on this thread.
Many thanks Mud
Aim
185th (cadet) -
I take it back about the MFDâs not working on your script⌠I reinstalled the driver for the MFDâs, ran your amended script, the one where button 29 is ALT+V , went into the pit and the MFDâs work fine, all the OSB buttons and toggle buttons work great but nothing on the MFDâs are illuminated, no LEDâs OSBâs not lit⌠Wonder whyâŚ
-
HI Mud, I have had a look through that document and copied the TMC file to desk top so I could try and edit it in wordpadâŚ. I wanted the Mic up switch to map to Numlock for Teamspeak.
This is the change I made
//Mic Switch
MapKey(&Throttle, MSU, DX83); // Teamspeak
MapKey(&Throttle, MSR, DX21); //Com 1 Transmit
MapKey(&Throttle, MSL, DX20); //Com 2 Transmit
MapKey(&Throttle, MSD, PULSE+L_ALT+USB[0x19]);DX 83 on the document was Numlock so hopefully I got that bit rightâŚ.