Mud's Profile
-
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.
-
BMS doesn’t recognize any of the stick functions for me, it says the button number and then function not assigned
-
BMS doesn’t recognize any of the stick functions for me, it says the button number and then function not assigned
I think this is normal. I have this as well, but in the pit they do work as they’re supposed to. I think it has something to do with these being DX-buttons.
-
@Mud:
I think this is normal. I have this as well, but in the pit they do work as they’re supposed to. I think it has something to do with these being DX-buttons.
I tested it but when i’m in the pit my buttons still don’t function. My speedbrake, mic hat, TMS, DMS, NWS, CMS etc. don’t do anything
-
And you did load my keyfile and ran the script in the TARGET script editor?
-
Yes, I’ve loaded both, it seems only the DX keys are affected
-
That’s odd. Seems that more people have reported this problem yet I do not experience it myself …
-
All working fine here! However, with the addition of new callbacks for manual flaps, hook, wing fold and nozzles it would be useful to have these added to the script, or at the very least in commented out alternatives. Flaps and nozzles in particular! I’d offer to add them myself but I’m still figuring out how to interpret USB and DX codes.
Possible solution could be to switch the Warthog Flaps toggle back to manual flaps (optionally) and maybe add nozzle increments to something like Shift+China Hat. I guess Gear would have to back to the L/G Silence button and lose alt gear button altogether?
-
Quick question. Does the script also fiddle around with the axis settings as in their sensitivity? Or is it just the mapping of the buttons?
Greetingd and thanks for your great profile,
Mobius
-
The axis settings are in the beginning of the script, and they’re basically default. So no messing around with the sensitivity really.
-
@Mud:
That’s odd. Seems that more people have reported this problem yet I do not experience it myself …
I have fixed it by completely uninstalling 4.33 and then reïnstalling it
-
I’m currently modifying the script and BMS 4.33 keyfile. I’m going to modify to original key file as little as possible.
You can expect me to upload the new version today still. -
New version has been uploaded. I did bite off a bit more than I could chew today though. The autopilot code has not been done yet, nor have I been able to test the new script properly.
I’ll upload a full and tested version later this week.Feel free to report any problems you may encounter so far.
-
This post is deleted! -
Having the same issues as Qmaster, even with the updated files.