honestly, it was just as simple as not setting the axes properly. you are the man. I can’t believe I overlooked this.

I thought you had to select the throttle and then assign the axes there but you have to have to joystick selected and go to advanced and select the throttle axes for the throttle.

thanks!

I can’t get the TARGET script program to show the Device Analyzer for the Thrustmaster Throttle when I’m running a script. What needs to be to done to get the Device Analyzer working?

Edit:
Got it. After I downloaded the latest firmware.

TARGET Script is really a mighty tool,

enjoy the programming phase :)!

Shadow, what about those pictures the inside of your Warthog? and what type of grease are you going to use? Did thrustmaster suggest any type?

WeakLink

Listen to Icarus. he helped me get mine set up. thanks Icarus

googled “empty warthog sheet”

second link was bingo
sended you a pm about AP

Look for:

//*************************** //*** Launch Falcon BMS *** //*************************** //Launch Falcon BMS 4.33 system("spawn -w \"D:\\Falcon BMS 4.33\" \"D:\\Falcon BMS 4.33\\Launcher.exe\"");

And change it to:

//*************************** //*** Launch Falcon BMS *** //*************************** //Launch Falcon BMS 4.33 // system("spawn -w \"D:\\Falcon BMS 4.33\" \"D:\\Falcon BMS 4.33\\Launcher.exe\"");

Or you can delete that part alltogether, or set the path to where you have your BMS installed.

Mud

@Sarge55:

Morpine’s does use TARGET. It’s a great profile, been using it for years.

True, I meant the GUI editor. I learnt to avoid keybindings through the TARGET GUI in order to avoid duplicate or overlapping binds. The more dx assignments, the better.

I’ve had that problem, the joystick and throttle would go to sleep, Thrustmaster wrote back and said" the warthog needs to be plugged in to a powered USB hub or better yet direct to the computer. It seems to work best plugged into the computer and I run my rudders of the power HUB no problems since. Hope that helps.

Frederf answered my question -they will work.

I had the problem with Win 8.1 so carried out the steps by editing the registry for both devices, they flash but only when I’m not logged into Win 10. I just have a problem where my machine wont boot with the TM Warthog plugged in, i have to take out and re-insert the device after log on

I used all my PC slots for a while and had issues with one device dropping out randomly. I bought a powered USB hub ($20) and the problem disappeared. The MFDs, Warthog joystick and throttle, CH rudders, TrackIR, and Lilliput monitor have zero issues now.

ViewZoom does not work…Set on a slider…use trackIr5
TrackIr vector Z Axis mode - Z Axis control…

EDIT : resolved

I believe the 1.5 second delay is only active when using the ‘shifted’ china hat function, ‘emergency jettison’.;@AlunHowells:

The values in the target script require the hat to be held for 1.5 seconds and the flight stick axis to be within certain limits.

alter the key file to simple send a
MapKey(&Throttle, CHB, PULSE+L_CTL+‘j’);
MapKey(&Throttle, CHF, PULSE+L_CTL+‘e’);

Alun

I’m also using Morphine’s profile, and these are the lines from the .tmc file;

MapKeyIO(&Throttle, CHF, TEMPO(0, L_CTL+‘j’, 1500), AXIS(DX_THROTTLE_AXIS, -500, 20));
MapKey(&Throttle, CHB, AXIS(DX_THROTTLE_AXIS, 500, 20));

FIXED!!

The problem was Commodo Free Internet Firewall!! I was getting fed up with its constant pop up requests to allow this or block that so I uninstalled it and changed to Zone Alarm. I had still been testing the TARGET scripts as recently as the day before (possibly even the same day) and they wouldn’t run, same error message or the script would time out. However it occurred to me this morning that I should try it again now I have ZA instead of Commodo Firewall and BOOM!! It worked!!

I had to re-arrange the order of the controller ID’s using the JoyID’s application so that they matched the order in which TARGET was detecting them when running the script but once that was done the script ran perfectly and created the Thrustmaster Combined virtual device (it has never done that before). I opened the Device Analyser (also never been able to open that before either) and all axes and buttons etc are working fine! Thrustmaster Combined is also now showing in Devices and Printers (but it shows as HID-compliant Game Controller).

So, I am pretty convinced it was Commodo Firewall? The interesting thing to note is that I had disabled the firewall on numerous occasions when trying to get the scripts to run and had also added EVERY TARGET executable file to the Commodo Allowed Programs list but it was obviously still blocking outwards comms between TARGET and my controllers? I have not changed or altered anything else on my system that could have affected this problem as far as I know.

Hope this helps anyone who experiences this problem now or in the future?

I can now start using my Warthog HOTAS to its full potential!!

Sorted!!

PS: VERY happy with Zone Alarm so far too!! Very unobtrusive Firewall.

keep it simple…

download morphines profile, and install it like this:

1)install target and open FalconBMS-Warthog.tmc with it. press play in the target software to run the joystick. your joystick should be named now THRUSTMASTER COMBINED in windows control panel / usb controller device.
2)copy the Warthog_DX.key to your FalconBMS folder (Falcon BMS 4.32\User\Config)
3)run falcon 4 bms, load the Warthog_DX key by going to SETUP, CONTROLLER, then click LOAD button and select the Warhog_DX.key
4) inside falcon 4 bms setup, select the joystick controller as “thrustmaster combined”. then map the joysticks in the advanced tab inside the controller configuration in BMS. this mapping is described in the JPGEG Pictures that morphine includes (View Control, Flight Control, Avionics Control)
5) set Afterburner by clicking the AB button. Leave the Thorttle in the position before activation of afterburner, then click the button. Repeat for Idle deten but with right click of the AB button.
6) enjoy!

after you learn and stabilize, you will want to edit things to your likings.

cheers!

I figured this one out. I had the wrong hat mapped. That’s why it didn’t work. Operator error as usual!

I run linear with small deadzone. It’s pretty fine that way. If I was putting the stick under the TARGET script then I could use the programming language to make exact deadzone limits. People complain about the stiff spring but I like it. The real SSC takes like 40 lbs. of force to command 9G. I suppose you could put in saturation levels to make it more twitchy and “telepathic” but I have a hard enough time being smooth and doing AAR at linear. Curves are precision in one area at the expense of the other and saturation are missing out on valuable range.

I really wish I could customize my deadzones precisely. BMS “small” is a bit too much but it’s unacceptable to fly where handsoff does not equal a consistent output. Flying with output slop is madness.

@Shadow:

Just finished a flight , Ill see whos up for more , wait one

PS: Most are going to bed, maybe another time. Our Team-speak is easy to find and you welcome.

Thanks for the help Kolbe

Yep amazing info Kolbe but you just forgot to give us the link to download 4.33 🙂

Get your self a copy of “Notepad ++” and use that to view your .key file.

Be carefull not change anything yet. NP++ has an Undo function but.

Cheers