Mud's Profile
-
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….
-
Yaay got them both lit up, stoopid settings in windows control panel……
-
Spoke too soon lol… When I ran the TARGET script, the one you helped to configure button 29 to ALT+V both MFD’s have no illumination again, I went into windows devices again and there was no facility to turn the brightness up, when I went into controller settings for the MFD’s on the Warthogs and Rudder was there, no sogn of the MFD settings…
Also did try running the amended script I tried…
//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]);TARGET came up with an error message, so I must have screwed up.
Aim
-
Hi again Mud, I noticed (should have looked first) that this issue came up before and you as always you had a fix
"Ah yes!
They should actually not be turned off, but I forgot to adjust the value in my last version upload.
Anyway, easy to set yourself. There’s two ways:
- Edit the script:
Look for (line 342)
Code:
//*************************
//*** TM Cougar MFD’s ***
//*************************ActKey(PULSE+KEYON+LED(&LMFD, LED_INTENSITY, 0)); //set left MFD backlight power to desired number (0-255)
ActKey(PULSE+KEYON+LED(&RMFD, LED_INTENSITY, 0)); //set right MFD backlight power to desired number (0-255)
And change the 0 to any value between 0 and 255. 255 being the brightest setting."I made the suggested changes and am now looking at bright LED’s on my MFD’s….
SO I just need to get the right syntax for assigning mic switch up to numlock…
My attempt failed
//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]);is 83 the right code for Numlock or did I get something else wrong?
Regards
Aim
-
That would have to be USB[0x83] for NUM LOCK, as it’s not a DX binding.
So DX83 becomes USB[0x83] in your case.
-
I am sure I will get my head round it soon… Thanks for the correction Mud I will pop that line in and see how I get on.
Once again many thanks for your time.
Aim
-
I have made the alterations… Are they correct now?
//Mic Switch
MapKey(&Throttle, MSU, USB[0x83]); // Teamspeak
MapKey(&Throttle, MSR, DX21); //Com 1 Transmit
MapKey(&Throttle, MSL, DX20); //Com 2 Transmit
MapKey(&Throttle, MSD, PULSE+L_ALT+USB[0x19]);Regards
Aim
-
I tried it and it didn’t
I have reloaded the previous file for now…
Aim