Mud's Profile
-
I am very new to this forum, so forgive me if this is the wrong place to post. your profile worked perfectly for me, except, that in spite of following the instructions to the letter, my control setup within the game doesn’t save. So I have to set the pedals, Joystick and throttle, every time I play?
Another question, can I enter more inputs in the list and then save those?Yeah, Same here… Just getting back into all of this myself. I set my preferences in setup and then save. I’ve changed both files to read-only and yet every time I start I have to reconfigure the rudder and throttle assignments.
Curious. Maybe it’s a new-guy thing.
Hmmmm… Just tried it again and it worked… must be a new-guy thing.
-
I’ve given up! cannot get the controls to work correctly. Yesterday after spending half an hour resetting it all up again, nothing worked correctly. My plane constantly wanted to climb at a steep angle and no amount of trim would correct it. Pity because the game looks amazing and I miss Falcon 4.
Will stick to Dcs I have five aircraft to fly there, though I have never mastered flying the Black shark! -
I’ve given up! cannot get the controls to work correctly. Yesterday after spending half an hour resetting it all up again, nothing worked correctly. My plane constantly wanted to climb at a steep angle and no amount of trim would correct it. Pity because the game looks amazing and I miss Falcon 4.
Will stick to Dcs I have five aircraft to fly there, though I have never mastered flying the Black shark!If at first you don’t succeed - give up!?
Short of hardware failure - which if it works in DCS eliminates the possibility - there is no reason you should give up. Perseverance and community help will solve your issues.
-
As instructed the script file was put into Target Gui and the key file into Bms, User file,config. then to axismapping and clicking on read only. Same with Joystick.cal, click read only.Then gone to setup, controllers, loaded your profile and then set all my axis preferences and TrackIR.
After closing down and restarting the game, it’s the axis mapping that have all to be reset.
Shouldn’t happen.If you have marked the files as read-only BEFORE doing the required changes inside BMS Setup pages, you will never save them! There is no reason at all to mark the two files read-only anyway - change them back and try again please.
-
There is in fact a reason for setting them to read-only, Malc.
The TARGET scripts set the stick and throttle to a “Trustmaster combined” device. So let’s say you’ve set up everything properly and then launch BMS without first enabling the script, and thus “Thrustmaster combined”, BMS will see different devices for the Warthog and revert back to defaults in the settings. So you have to redo the whole thing.
As Malc said though, don’t give up yet Mike. It took me many hours, but you get rewarded whenever you learn something new. BMS is a great sim.
-
@Mud:
There is in fact a reason for setting them to read-only, Malc.
The TARGET scripts set the stick and throttle to a “Trustmaster combined” device. So let’s say you’ve set up everything properly and then launch BMS without first enabling the script, and thus “Thrustmaster combined”, BMS will see different devices for the Warthog and revert back to defaults in the settings. So you have to redo the whole thing.
As Malc said though, don’t give up yet Mike. It took me many hours, but you get rewarded whenever you learn something new. BMS is a great sim.
No, I disagree. The two files in question, axismapping.dat and joystick.cal, need to be written to after he visits the Setup page within BMS. If they are marked as read-only he will be able to assign axes and calibrate joystick/throttle/rudder until the cows come how but THEY WILL NEVER BE SAVED and will require resetting every time starts BMS again. These two files are specific to BMS and are totally independent of anything done outside BMS. If they are not read-only, they will save his assignments and calibrations.
-
@Mud:
Ah, you’ll have to make those files read-only after having configured your settings in BMS. Else, BMS cannot save them.
See above.
-
-
Hey Mud, I am a total nugget when it comes to BMS and trying to get the Warthog running was tedious up to so far…
I loaded up your profile with the Target Script Editor and put the keyfile in the user/config directory and loaded it up. Now with the ingame controller settings the Throttle axis does not respond. All the other axis are a-ok and I can map them all - only the (right) Throttle axis won’t budge. Now when I open the joystick analyzer from within the Script Editor the axis responds normally - any idea what is going wrong?
Cheers
Kirin
-
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.