Mud's Profile
-
It seemed very odd to me to
I’ve tried morphine’s and one more (a combination of yours and morphine’s) and I get the same compile error. I’ve also tried to reinstall TARGET.
I have tried it once I’m DCS, and the script worked,but never used it (thought it would be better to map myself).
I tried to open your file as a .fcf once, and I got it to run, but it didn’t work (I can’t remember how, so I may have missclicked and opened a preset by TM).
PS: I followed a tutorial on how to start the script and what else by: Sim deck, video is called “warthog BMS profile”.
-
Could you copy and paste the text at the bottom of the TARGET Script Editor window here after you run it?
-
GUI
Script editorI don’t understand how It can’t find it
Btw, I have tried running TARGET as admin and with compatibility mode (8.1 - 7 - XP) and your file is marked safe-ish (checked a box in properties that said it was a file from another computer.) -
Weird indeed. As if TARGET doesn’t have rights there, but if it wouldn’t then it wouldn’t even be able to open the file.
For the sake of testing try putting the .tmc in another location (non users) and see what that does. -
Hey Mud,
I’m a CH Products user thinking about somehow getting the Warthog stick and throttle, and wonder if there is any similarity with CH. I noticed your Mud.key didn’t have DX assignments at the end, whereas in my key file, after the BMS Full.key entries, each button/hat has DX numbers assigned by CH Control Manager software. And then in a Notepad editor, I just assign the DX numbers to the callbacks, based on Kolbe’s advice. I wonder if I could do this with the Thrustmaster Warthog gear. If that is possible, would I still need to use your profile, which everyone agrees is really good?
-
I don’t know very much about DX assignments to be honest. My script has DX for the majority of the stick, and the airbrake on the throttle.
Apart from that, I think the best profile is possibly the one you make yourself. I released mine because it’s just what I felt worked for me. Morphine, DonLDuk and some more folks have released theirs as well. Just give them a try, and change it to our desire. Or use them as a template to make your own. Yeah, it’s a bit of work. But well worth it in the end. Of course nothing says you won’t be fine with Morphine’s, DonLDuk or mine profile without changing a thing.
-
@Mud:
Beware though: the way I have set it up is that the light comes on when you activate the autopilot, and turns off when you deactivate the AP.
If you want to get rid of that, just comment out the 3 lines regulating the lights in the AP code (Line 446).Mud
Went to Line 446 however there was nothing that I could see to do with blacklighting.
-
Look for:
ActKey(PULSE+KEYON+LED(&Throttle, LED_INTENSITY, 50));
-
Thanks alot! Also having a strange issue no one else i know seems to be having, there don’t appear to be a button to cycle the bomb release modes on the hotas.
-
Thanks alot! Also having a strange issue no one else i know seems to be having, there don’t appear to be a button to cycle the bomb release modes on the hotas.
Correct. This is done on the MFD.
-
Can’t run the tmc script for some reason, this pops up:
"Connecting virtual mouse…Error: Failed (error:0x00000057)
Aborting script (check output above for reason)…
Script stopped!Runtime Error: Script run aborted in main ( line 192 in target.tmh )"
What’s the issue? I’ve changed nothing in regards to scripts, hardware, etc. for months and today I got this right out of the blue.
-
So you were able to run it fine before?
What OS are you running? -
Windows 8.1. Yeah, it worked like a charm until today.
-
Got to be a Windows thing then unfortunately. Plugging in stuff in different USB ports can upset it.
-
Only thing I can think of then would be another of those damned involuntary updates I got yesterday, I haven’t even changed the USB ports I’m using for ages. Thanks Mud!
And screw you Microsoft!
-
Your most frequent customer is back, already!
Updated to Windows 10, scripts work now. The issue I have now is that the following simply aren’t detected with your script: Cursor enable, pickle button, all DMS, TMS and CMS keys, NWS and pinky buttons on joystick.
-
I am having a problem where it seems the script is not selecting the right controller as my stick… so for example once I execute the script my throttle controls my rudder, and so on.
Here is the script execution log:
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\5&20A9C10C&0&1) selected
Error: (internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_0402”
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 found
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse…Donemain returned 0
Any assistance would be appreciated.
Thank you.
EDIT: Well that’s strange. This morning I tried using the script again and everything worked fine. No errors in the log. I just remapped the axes in BMS to the combined device (strangely, the vid I found that told me about this mapping said to map my axis BEFORE running the script), and now I’m golden. Tested all the controls and it works (include the long/short pulls). Yay :).
-
Mud, I got myself into trouble taking the advise of deleting and reinstalling 4.33…now I have the dreaded
Thanks M8, I guess I’m stuck flying DCS, CLoD, RoF, BoS…lol and none of those seem to be a true Sim like Falcon BMS…
Cheers and Salute
KV~When I saw this, I got worried about my Windows 10 registry. Here’s why. I have both BMS 4.32 and BMS 4.33 installed in different directories and both work OK using Mud’s v3.03. So what’s the problem? When I look at Windows “Programs and Features”, I only see Falcon BMS 4.32. There is no Falcon BMS 4.33. I’m afraid that if I ever have to uninstall, things could get screwed up. If anybody’s got both versions installed, what do you see?
-
@jc1:
I have both BMS 4.32 and BMS 4.33 installed in different directories and both work OK using Mud’s v3.03. So what’s the problem? When I look at Windows “Programs and Features”, I only see Falcon BMS 4.32. There is no Falcon BMS 4.33. I’m afraid that if I ever have to uninstall, things could get screwed up. If anybody’s got both versions installed, what do you see?
Same as you and this is correct. To uninstall 4.33, run the Setup.exe in your Falcon BMS 4.33 Setup folder.
I’ve had to do it and had no problems.
-
Same as you and this is correct. To uninstall 4.33, run the Setup.exe in your Falcon BMS 4.33 Setup folder.
I’ve had to do it and had no problems.
Thanks Steve, that’s good to know. When I uninstalled 4.32, I had to go to Windows “Programs and Features”, expecting the same for 4.33. I’ve never had to uninstall 4.33 and I hope I never will.