Mud's Profile
-
Hey Kirin,
That’s correct. Only the left throttle is looked at. Since I have both my throttles physically linked together for BMS, it’s not a problem for me. If you prefer using only the right one for some reason, I can look into that. I’m pretty sure it’s possible.
Regards,
Mud
-
Thanks for the quick reply. I’ll try linked then… I was hoping to use the left Throttle axis for something else…
-
Well, you can do it if you wish to.
Just uncomment (remove the // in front of) both lines I marked and the right throttle should be active too.
Around line 160:
//Throttle Axis Setups
MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
SetSCurve(&Throttle, THR_LEFT, 0, 0, 0, 0, 0);
//MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); //Not used in the game at the momemt for dual engine planes
//SetSCurve(&Throttle, THR_RIGHT, 0, 0, 0, 0, 0);
MapKey(&Throttle, IDLELOFF, CHAIN(D(1000), PULSE+L_ALT+USB[0x0C])); //Idle Detent ** USB i **
MapKey(&Throttle, IDLELON, PULSE+L_ALT+USB[0x0C]); //Idle Detent ** USB i **Best regards,
Mud
-
Wow, you get things done fast, man! Thanks.
Now I have to dig into the manual after fooling around with Instant Action!
Cheers
Kirin
-
I believe I am being a massive noob here but you all seem very helpful so I will post my issue.
I’m using the TMS Warthog and Saitek Combat Rudder Pedals (Also TrackIR5).
I loaded your script into Target GUI (v1.0.11.304) without any warnings or errors, in Falcon 4.0 BMS (v4.32) I loaded the 4.32 Mud keyfile and it seems as though none of my controllers keys are assigned? I tested it out in instant action and only a few commands such as autopilot and dogfight mode worked (which I believe are actually coded commands in the script). My joystick, throttle and rudders axis’ are all working 100% in BMS and the hardware works like a dream in DCS A10C/F15C/MIG21B, so I’m not entirely sure what’s going wrong here.
I also tested Morphines profile and came across pretty much the same issue.
Like I say, I’m probably being an idiot as always but could someone point me in the right direction? Been trying for almost 4 days now lol.
-
I’m abroad at the moment so I can’t check but I see you load the script in target gui.
Try running it in the target script editor instead.
Best regards,
Mud
-
Damn I was just coming back to the thread to post some additional information and you’ve already responded, thanks.
I have tried both gui and script and get the same issue.
I removed the MFD code, in case that was messing with the bindings.
It seems to be focused on the joystick as the throttle gives off plenty of commands when running the event tester, whereas the joystick gives none except for the paddle switch (which in game responded correctly as Look Closer, all the others in game have no function assigned).
Similarly when testing Morphines profile all of the joystick inputs were assigned to MFD buttons, rather than their actual counterparts, seems almost as if there is something mislabeling my keys.
-
I made the assumption that the controller is meant to be the TMS Warthog root and NOT the keyboard correct? (In BMS)
-
Beware, the event tester will not show dx nor USB key codes I believe . So you really have to test it in the jet.
-
I have first, I did those tests afterwards to make sure all the hardware was responding correctly.
Most of the functions on the diagram are not working as they should. I tried re-downloading the script and keyfile in-case of corruption but with no success.
-
Hmm, I’m not sure then. Might have to wait till I’m back home on Monday and perhaps I can talk you through it over TeamSpeak or so.
-
Sure thing. Thanks for your time and enjoy whatever country you’re in.
-
Hi Mud,
I am very late to this show, so I hope you see this post. I recently installed BMS and subsequent to that I installed Warthog Hotas (which I have working perfectly in DCS). I would like to give your setup a go as I am unable to get to assign throttle, rudder pitch and roll etc. I guess that I am doing something wrong. Just a quick question please; Would you please explain what you mean by the following?
4.Automatic Launch of Falcon BMS Edit or delete the code at *** Launch Falcon BMS *** as you please. But if you do not change it, you will most likely get an error.
5.TM Cougar MFDs If you do not have the Cougar MFDs, you should also delete or comment out the *** TM Cougar MFDs *** code.
Where and how does one take these steps?
I am very new to anything other than very basic Windows 7.1 manipulation.
Thanks very much for the effort you put into this profile. It is very much appreciated by this Newbie.
Kerfuffle (aka Steve) -
Hey Kerfuffle,
If you have trouble with your throttle and axis make sure you have set the proper device in Setup => Controllers and then the droplist just under your profile name. Default it’s set to keyboard I believe.
4. A line in my script launches BMS automatically once the script is loaded. But since your installation of BMS is probably not at the same location on your disks as mine is, it will not find the .exe. So you either comment out that line (so it does not get executed) or you edit it to the correct path.
Commenting out something is done by adding // to the beginning of the line.
//***************************
//*** Launch Falcon BMS ***
//***************************//Launch Falcon BMS 4.32
system(“spawn -w “D:\Falcon BMS 4.32” “D:\Falcon BMS 4.32\Launcher.exe””);5. Just delete or comment out these lines if you don’t have the Trustmaster MFD’s
//*************************
//*** TM Cougar MFD’s ***
//*************************ActKey(PULSE+KEYON+LED(&LMFD, LED_INTENSITY, 2)); //set left MFD backlight power to middle
ActKey(PULSE+KEYON+LED(&RMFD, LED_INTENSITY, 2)); //set right MFD backlight power to middle// Left MFD
MapKey(&LMFD, OSB01, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x1E],LOCK)); // ** USB 1 **
MapKey(&LMFD, OSB02, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x1F],LOCK)); // ** USB 2 **
MapKey(&LMFD, OSB03, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x20],LOCK)); // ** USB 3 **
MapKey(&LMFD, OSB04, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x21],LOCK)); // ** USB 4 **
MapKey(&LMFD, OSB05, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x22],LOCK)); // ** USB 5 **
MapKey(&LMFD, OSB06, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x23],LOCK)); // ** USB 6 **
MapKey(&LMFD, OSB07, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x24],LOCK)); // ** USB 7 **
MapKey(&LMFD, OSB08, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x25],LOCK)); // ** USB 8 **
MapKey(&LMFD, OSB09, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x26],LOCK)); // ** USB 9 **
MapKey(&LMFD, OSB10, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x27],LOCK)); // ** USB 0 **
MapKey(&LMFD, OSB11, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP1,LOCK));
MapKey(&LMFD, OSB12, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP2,LOCK));
MapKey(&LMFD, OSB13, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP3,LOCK));
MapKey(&LMFD, OSB14, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP4,LOCK));
MapKey(&LMFD, OSB15, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP5,LOCK));
MapKey(&LMFD, OSB16, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP6,LOCK));
MapKey(&LMFD, OSB17, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP7,LOCK));
MapKey(&LMFD, OSB18, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP8,LOCK));
MapKey(&LMFD, OSB19, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP9,LOCK));
MapKey(&LMFD, OSB20, CHAIN(LOCK+PULSE+L_CTL+L_ALT+KP0,LOCK));
// GAIN = HUD Brightness
MapKey(&LMFD, GAINU, CHAIN(LOCK+PULSE+L_ALT+USB[0x1B],LOCK)); // ** USB x **
MapKey(&LMFD, GAIND, CHAIN(LOCK+PULSE+L_ALT+USB[0x1D],LOCK)); // ** USB z **
// BRIT = Left MFD Brightness
MapKey(&LMFD, BRTU, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x0A],LOCK)); // ** USB g **
MapKey(&LMFD, BRTD, CHAIN(LOCK+PULSE+L_CTL+L_ALT+USB[0x09],LOCK)); // ** USB f **
// SYM = AA / AG
MapKey(&LMFD, SYMU, CHAIN(LOCK+PULSE+L_SHIFT+KP1,LOCK));
MapKey(&LMFD, SYMD, CHAIN(LOCK+PULSE+L_CTL+KP1,LOCK));
// CON = Altimeter adjust
MapKey(&LMFD, CONU, REXEC(3,90,“ActKey(PULSE+KEYON+L_SHIFT+L_CTL+USB[0x14]);”)); // ** USB q **
MapKey(&LMFD, COND, REXEC(4,90,“ActKey(PULSE+KEYON+L_SHIFT+L_CTL+USB[0x1A]);”)); // ** USB w **// Right MFD
MapKey(&RMFD, OSB01, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x1E],LOCK)); // ** USB 1 **
MapKey(&RMFD, OSB02, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x1F],LOCK)); // ** USB 2 **
MapKey(&RMFD, OSB03, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x20],LOCK)); // ** USB 3 **
MapKey(&RMFD, OSB04, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x21],LOCK)); // ** USB 4 **
MapKey(&RMFD, OSB05, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x22],LOCK)); // ** USB 5 **
MapKey(&RMFD, OSB06, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x23],LOCK)); // ** USB 6 **
MapKey(&RMFD, OSB07, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x24],LOCK)); // ** USB 7 **
MapKey(&RMFD, OSB08, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x25],LOCK)); // ** USB 8 **
MapKey(&RMFD, OSB09, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x26],LOCK)); // ** USB 9 **
MapKey(&RMFD, OSB10, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x27],LOCK)); // ** USB 0 **
MapKey(&RMFD, OSB11, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP1,LOCK));
MapKey(&RMFD, OSB12, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP2,LOCK));
MapKey(&RMFD, OSB13, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP3,LOCK));
MapKey(&RMFD, OSB14, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP4,LOCK));
MapKey(&RMFD, OSB15, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP5,LOCK));
MapKey(&RMFD, OSB16, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP6,LOCK));
MapKey(&RMFD, OSB17, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP7,LOCK));
MapKey(&RMFD, OSB18, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP8,LOCK));
MapKey(&RMFD, OSB19, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP9,LOCK));
MapKey(&RMFD, OSB20, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+KP0,LOCK));
// GAIN = HUD Brightness
MapKey(&RMFD, GAINU, CHAIN(LOCK+PULSE+L_ALT+USB[0x1B],LOCK)); // ** USB x **
MapKey(&RMFD, GAIND, CHAIN(LOCK+PULSE+L_ALT+USB[0x1D],LOCK)); // ** USB z **
// BRIT = Right MFD Brightness
MapKey(&RMFD, BRTU, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x0A],LOCK)); // ** USB g **
MapKey(&RMFD, BRTD, CHAIN(LOCK+PULSE+L_SHIFT+L_ALT+USB[0x09],LOCK)); // ** USB f **
// SYM = AA / AG
MapKey(&RMFD, SYMU, CHAIN(LOCK+PULSE+L_SHIFT+KP1,LOCK));
MapKey(&RMFD, SYMD, CHAIN(LOCK+PULSE+L_CTL+KP1,LOCK));
// CON = Altimeter adjust
MapKey(&RMFD, CONU, REXEC(7,90,“ActKey(PULSE+KEYON+L_SHIFT+L_CTL+USB[0x14]);”)); // ** USB q **
MapKey(&RMFD, COND, REXEC(8,90,“ActKey(PULSE+KEYON+L_SHIFT+L_CTL+USB[0x1A]);”)); // ** USB w ** -
Hi Mud,
Thanks for the quick response. I see in the setup screen where I need to select which controller I want to assign however, once I assign the throttle and the go to assign to rudders for example and the go back to check the throttle, the throttle no longer responds in the setup screen.
What is the path one takes to comment out a line? See, I really am a beginner.
I really like Falcon as I used to mess around with 4.0 years ago. I am looking forward to enjoying it once again. So much has changed! -
So you start by opening my script file (the .tmc one) in the TARGET Script Editor, right?
Once in there, you’ll see some lines of text are green. That means they’re comments. They don’t get executed. They all start with //
If you if prefix a normal code line with //, it will become green and therefor inactive so to speak.Then you press the play button on top of the TARGET Script Editor and then do your settings in BMS.
-
Hi Mud,
First of all thanks a lot for the profile! It’s been most helpful.
However I’ve encountered the same problem mrmr mentioned in the previous page. None of the DX buttons are working for me. The script gives me this error, i don’t know if it’s related.
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 foundI disabled all lines related to the MFDs (i don’t have those), so that’s not the cause.
Everything else worked like a charm, so i ended up disabling all DX keys in your script, modifying your .key file to re-enable the DX HOTAS buttons (TMS, DMS, CMS, trigger, pickle… just copied those from the original BMS.key) and binding them in the sim. Now everything works, hope this is helpful to anyone else having the same problem.
-
Hi Mud
Please new target settings in BMS 4.33 -
Haha yeah! Give me … hmm … a few days or so and I’ll get everything sorted. I won’t be taking no 3-4 weeks btw
-
At the moment I’ve not been able to find anything I should change in the script or keyfile, as none of the new callbacks seems to be linked to the HOTAS. I’m still a bit overwhelmed with the amount new info though.
Anyway, if any of you know something which should be added or changed, feel free to inform me.