Mud's Profile
-
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
-
Hmmm, not quite sure why it wouldn’t work. Unless num lock is seen as a special key.
I’ll hook up my hotas this weekend and try it out myself.Mud
-
Try 0x53, that’s also num lock.
-
ah, cool thank you, Numlock was suggested as the hot key for Team speak as it serves no function on BMS, I will amend the tmc file I have been playing with, rename it and drop it into /user/config, then load it up on TARGET to see what happens, if it doesn’t work I will revert back to the file that does work with the Mic switch down ALT+V you kindly done for me Mud and keep trying til I crack it, I need to be self sufficient on this as I have no doubt further down the line, more personal changes will be needed and I need to do those myself, not keep relying on you, I am sure you are busy enough.
I do thank you for your replies and help I do think its a great profile….
AIM
-
I have tried again and changed the hotkey for team speak to ALT+V, thats Mic switch down… When I am in teamspeak and I click the Mic hatswitch down the transmit light flashes but then goes out, it doesn’t seem to toggle… Any ideas?
Just another quick question, I have only had the Warthogs three weeks and still trying to memorise all the presses etc, I keep hitting the chaff/flare by mistake with my thumb moves down lol
I am training at the moment and having a real problem slewing the cursor to the targets, could you explain the Slew control please, on the diagram it says
Short –-- Radar cursor reset
Long---- Radar cursor enable
Am I right in thinking that to be able to slew I have to press the button in for a long time, that then activates the slew function? If I hold it in for a short time it will reset to the middle of the FCR? If so I think I may be pressing it in by mistake as I am slewing around, I am not doing well with Mavericks due of this…
Regards
Aim
-
Rudder pedal question… I just got my HOTAS about a week ago and started using this (muds) profile. Everything was, and still kind of is working great, but I just got my rudder pedals today, and, if I have muds script running, my rudder pedals dont show as a selectable control axis. If I stop muds profile and restart BMS, they show up and I can assign them. Can somebody tell my why and maybe how to work around it?
-
You most likely comment out line 15 from my script:
So from
Configure(&TFRPRudder, MODE_EXCLUDED);
To
//Configure(&TFRPRudder, MODE_EXCLUDED); ```Sorry for the late reply btw. Busy, hectical life at the moment. Mud
-
Alright, so it appears that it indeed is working in the jet now with my current DeviceSorting (still shows nothing in settings). So hopefully case is closed, thanks
Hey
I have the same problemCan you please tell me exatly how you solved the problem?
Either way, I’ll exxplain my problem with the hopes that somebody will help me.
I’m using Mud’s profile with Warthog hotas. Also I got the TrackIR5 and saitek pro rudder pedals.
All axis are working in the BMS, all buttons on throttle are working and pedals axis.
I have set up the Mud’s profile following it’s instructions.But, there is a problem with my joystick. Joystick axis are all fine and working. But only one button is working, and that is the Zoom in/out. Everything else I “press” on the joystick has no effect in the BMS.
Do you know how to fix this? PleaseI’m on Update 4
EDIT: and the trim is working on joystick.
-
Cheers Mud! I figured it all out eventually (having some experience with TARGET Script Editor helped) and got my T-Rudder working as well. Now to learn how to fly…
-
Can someone please direct me to a solution? I have installed the Mud keyfile to the correct folder and .tmc profile. When I run the profile through TARGET I get no errors. When I go into setup for controllers, I load the Mud keyfile. After that, half of the buttons work. The ones that don’t are the DX buttons. I can assign some but there are some assignments that don’t show up after loading the Mud keyfile like everything for the stick. I am completely confused. Any help will be greatly appreciated.
-
Hey
I have the same problemCan you please tell me exatly how you solved the problem?
Either way, I’ll exxplain my problem with the hopes that somebody will help me.
I’m using Mud’s profile with Warthog hotas. Also I got the TrackIR5 and saitek pro rudder pedals.
All axis are working in the BMS, all buttons on throttle are working and pedals axis.
I have set up the Mud’s profile following it’s instructions.But, there is a problem with my joystick. Joystick axis are all fine and working. But only one button is working, and that is the Zoom in/out. Everything else I “press” on the joystick has no effect in the BMS.
Do you know how to fix this? PleaseI’m on Update 4
EDIT: and the trim is working on joystick.
Can someone please direct me to a solution? I have installed the Mud keyfile to the correct folder and .tmc profile. When I run the profile through TARGET I get no errors. When I go into setup for controllers, I load the Mud keyfile. After that, half of the buttons work. The ones that don’t are the DX buttons. I can assign some but there are some assignments that don’t show up after loading the Mud keyfile like everything for the stick. I am completely confused. Any help will be greatly appreciated.
Looks like we are in the same boat.
-
You should not test the buttons in the BMS config, as the DX ones will not fire there. They should work fine once you’re in the pit.
This has been covered quite a few times in this thread already.
If it is that “problem”, I’m not blaming you for asking. 58 pages to go through is a bit much
I’ll add a FAQ to post 1 some time in the near future.Mud