I’d gladly pay the extra £30 to get a brand-spanking-new Warthog 🙂

@-Ice:

Yeah, I realized if I wanted an _and an [O] layer, I’d have to map one to _and one to [O]. If I mapped one to _[O] and mapped another one to _, the _won’t show up. 🙂

Yeah because as soon as you mapped one to both I and O you told TARGET that the shift state did not matter you wanted that one command to be used at all times. At that point creating a I only command didn’t make sense and I’m guessing TARGET ignored it for that reason. :)_____

thanks for showing this option for the WH detent. Didn’t know about it.

K the output of the script is looking fine so I’m guessing the problem lies somewhere else now…

@freemind:

If I go to the Game Controllers properties/Test the x and y axis don’t move.

Ok so that implies that it’s an issue with windows not recognizing the axes correctly though I’m currently clueless as for what the issue can be…

@freemind:

Do I have to do anything in the HOTAS Cougar Control Panel?

Perhaps, the fact that I don’t have a Cougar makes things a little more difficult… What options do you have in that control panel?
What I could also do is try to remotely login to your computer (with Teamviewer preferably since that’s what I have) so I can dig a little deeper…

One question though, do you have the throttle of the cougar too? If so, is it hooked up? Not sure if that’s a problem but if you got the cougar’s throttle, it’s definitely worth trying to see what happens if it’s hooked up…

Thanx to all for the reply…
Ive solved…
the mistake I made was that I felt the controls in the setup instead of entering the 3D world ahhahahaha in the 3D world works all.
there was no problem in the .key
In the setup you do not see the secondary buttons when using the shift … you see only the primary buttons
but in 3D world work perfet

🆒

Have a nice day and thanx again

TxMtb, thanks for the support ill look into it.

@TxMtb:

Manually edit your devicesorting.txt to put Thrustmaster Combined as the first line, then the rudders.
Once it’s set there you should be good. IF it changes again for some reason, edit it back and set it to read only.

Yess… work… the Combined TH stay in 1° position device also if i unplug or replug the rudders… ive try also to restart the PC.

Thanx so much guys 😄

Red nail polish for the trigger seems like it would meet your criteria of easy and inexpensive. Not sure how well it would adhere though so use at your own risk lol

I find it easier to hook up in a turn because of the slight back pressure on the stick, seems easier for me.

Thanks for all the advice! I found the solution in another thread about issues with the Target Script. I just need to run the program as an administrator.

Thanks again guys.

Blu3wolf,

I may do that, but I do like all the extra toggles and switches on the Warthog throttle. I’m using Rybo’s profile, and its great. He helped me to get the pedals to work, and wow, what a hotas. What an upgrade from the X52, which I really liked.

Thanks for all the advice guys, I’m having a blast.

Hi,

Sorry, I thought the uploader will display download page in English depends on the browser language but seems it does not.
I changed download link to my google drive.

I don’t own them but Cougar MFDS should work. For Thrustmaster pedals, enable specific line in the TARGET script as described, then they should work. It also works with TrackIR. I tested with FreeTrack.

I did not include any function that does not exist in RL F-16 so you have to assign zoom callbacks to some of the remain DX buttons.
If you want to assign zoom axis to throttle slider, you have to edit DeviceDefaults.txt

This profile does not do anything special or weird. Default BMS setup is assigned for HOTAS COUGAR so instead of uploading a key file I changed DX buttons order to match stock setup.
You only have to run the profile before starting BMS, and after you finished BMS you can stop the TARGET script.

Sweet shots.

A fairly good summary of certain pages from the manual included for free in your install folder.

@Stevie:

We could all food them with our Cougar/Warthog hacks…pictures and descriptions? Maybe they’d take notice.

I’m in.

@violetaceman:

Instead of using the Event Tester, try using using the Event Analyzer.
You have to click in the circle on the upper left and select the “Thrustmaster Combined” device once it’s open.
This will allow you to see all the DX buttons, and the virtual keyboard and virtual mouse also.

Ok, had some conflicting OBS entries. Commented them out.

TARGET’s control over deadzone is much finer than BMS’s so I would tend to use TARGET’s if I could (and not both). The minimum deadzone in BMS I think is 5% which is quite a lot. Ideally the beginning of input (> 0) would happen exactly at the edge of center slop.

Despite TARGET’s wording I don’t think that the hardware deadzone is “hardware” but simply built into the script that’s running. I would have to test it. In any case if you’re running the joystick device as part of the TARGET virtual device then you have a lot of control over deadzone. So ideally set up deadzone in TARGET and set BMS to none.

This is actually a dual cockpit enhancement, IMO.

There is also a cursor slew speed parameter option in the Config utility (or the text file it’s editing) Avionics>Cursor Speed.

TARGET determines what is the output from the logical device. A completely “blank” Target script (or GUI profile) does exhibit fall through behavior such that buttons still produce output in a default way even though no explicit binding has been made. Considering that both Warthog devices is more than the logical limit of 32 buttons and 8 axes not every input will get an output (joystick’s 19 buttons get priority, the remaining throttle LTB #20 then one through speedbrake get 21-32). By excluding the joystick from the TARGET profile the full functionality should be mapped.

If you’ve already set up BMS to use the Warthog devices without TARGET then running TARGET will be like plugging in a totally different device. There’s no reason why you can’t use the UI to setup a TARGET joystick just like a non-programmable one.