dimebug

pedals alone will not work, but you can choose to use only rudders axes coming from the G940 complete set and make them work with the warthog connected...

DirectX doesn't support enough axes to support the complete cougar, by default, if you check in the Cougar Control Panel, you will see that the Microstick axes are 9 and 10, so hidden to DirectX. Late last night I've noticed that if you don't have a rudder plugged in the Cougar only offer 5 axis whatever you do. If you have a 3 axis rudder plugged in, if you swap the Toe Brakes ones with the Microstisk ones, you will access the MSX and MSY axes. Be also aware that the physical name cannot match their expected names as you can change their order of mapping and DirectX or T.A.R.G.E.T cannot detect it.

you can do that with target without problems (gui or script) but yet all the keystroke aren't defined in DCS A10C, so, it's just better to wait the finished product to start to works on a serious configuration.

Warthog Throttle alone = 32 buttons HOTAS Cougar Throttle + Joystick = 32 buttons what else....

Yes for the virtual rotation, it's interesting if there's no transition of force between X and Y axes. So good for Warthog and T-16000M, but not adapted to Cougar.

Panzertard, the benefits are huge if you really want to fine tune you controller setup. You can use internal memory, do math, changes axis curves in flight, create you own chaff and flare programs under FC2, make it loop or play it just one time. You can use logic to have realistic control of the Autopilot under FC2 (make it equal to the one of DCS A-10C)... For those who wants to use the joystickcentred and turned 15° counter clockwise but keeping the axes straight in line with the plane, it's also possible... just some examples of applications.

The source of install problem as now be identified, it's created by the windwos keyboard local settings... to avoid it or to give a try Go to regional settings and set the language to English-US. (For Win7, in control panel->region and language, set the location to United States and the keyboard default input language to English-US, in the Keyboard and languages tab->Change Keyboard... ). Then make sure that when you start the program, in the language bar EN is selected. Mower, TARGET does nothing to the Cougar stuff, doesn't replace or touch any cougar drivers or whatever, it just works throught Direct X. It doesn't use any tool tools from the Cougar. And TARGET and Foxy can live together on the same system without issue. If you are already a good foxy user and not a big fan of complex configuration, you don't own the MFDs, target as a limited interest for you and don't change of programming language and software will keep your life simple. You have the choice, that's the most important.

Well, the Hog is not yet avaliable in France...

it should...

the Warthog stick as only switchs, no axes

it's not yet implemented and it wasn't for the Cougar stuff. Detect an exe launch means that you must have a kind of spy loaded in memory at windows startup. This kind of stuff use to slow down your computer and takes some memory. It's not the way Target Works. If people ask for it, it could be added, or a TARGET external small launcher.

Yet, Target isn't able to do this

Dimebug> Can you elaborate on this a little further? You alluded to the Y saturation parameter. Presumably this setting is in DCS: A-10C? In the 'Options' menu? I couldn't see anything that related to the microstick axis under 'controllers', but I'll have another look. go in the DCS Option Menu, select controls tab, select axis command categorie. In the collumn Throttle Hotas Warthog, select by simple click axe X then click on the button Axis Tune. Here you have access to the Y saturation parameter, set it to 11. Once done do the same for Y axis

if you want to launch the game with an associated configuration/script, you can do it from the Fly now menu, on the main page of Target. all the other ways only launch the Configuration/script alone, and then you have to start the Flightsim software.

in the Control Panels of A-10Cn set the Y saturation parameter to 11 or 10, and deadzone on 20 Ch users had the same issues, the camera really moves too fast. It's the Same in BS, except that the TMC provided with Target include a Sensitivity adjusment depending the level of zoom.

you can report the errors here : http://target-bugtracker.thrustmaster.com/ maybe i can help you, but i need to know the error message first...

Tarmac Aces use to make high quality stuff, made of strong resin. http://www.tarmac-aces.com/html/en/hangar.php I've tried the rudder and the KG13, that's good stuff.

this is right, this is why the scale axis parameter solve this issue.

I confirm, the Simped is a great choice

i've got one, interfaced with leo usb card, if you are interested, pm me... i'm in France