Just bought a Warthog and Saitek Combat Pedals...A big mistake....

[Ebs]

...Is that I didn't get them sooner! Haha! ;)

 

Seriously though, this thing is awesome. I had an X52 (non pro) before and a MSFFB2 before that...But the Warthog? Wow.

 

I'm not knocking the X52. It served me well and I had it set up exactly how I wanted it, but after two days with the Warthog I doubt I could ever go back to the 52.

 

One thing's for sure, the Warthog takes some getting used to. The first flight felt like I was arm-wrestling Schwarzenegger and nothing was where it was supposed to be! (like on the X52 I mean!) and I felt myself overcorrecting everywhere. I didn't expect it to be so sensitive. It almost feels like it's force sensing, honestly.

 

The Saitek programming software is pretty deep, but I didn't expect the level of programming available via target. Of course, everything's plug and play with the 'hog but being a developer in my day job, I took a look at some Target stuff and it blew me away. One of the reasons for getting the Warthog was so I wouldn't have to do so much tweaking...But seeing the possibilities with Target threw all that out the window :)

 

As for the pedals...can't complain. I had a set of CH Products pedals years ago but I couldn't really get over the fact that they were so close together. the Saitek's feel so much better in that regard. Quick deadzone setting and invert for the toe breaks in DCS and all is set.

 

In short, I can't be happier.

[snafup]

[dburne]

Congrats!

Great combo, I got the same early last year and love them!

[FreeFall]

There is this well known issue:

http://forums.eagle.ru/showthread.php?p=1650285#post1650285

 

Haven't tested it with v1.2.3 though.

[Python]

I just upgraded to the hog from the x52 pro, the difference really is night and day! I'm really happy with it. Only problem is I don't have rudder pedals yet but I'm on the case. As you say though, it is taking some getting used to but it is well worth it.

[bn880]

DCS A10-C Trustmaster Warthog TARGET Pass-Through

 

A "developer" who just got the warthog with TARGET eh? You might enjoy this then; I wrote an A10 pass-through TARGET script which basically maps your A10 controls identically to the plug and play operation you get with DCS.

 

The reason for the pass-through is to allow you to switch profiles without restarting DCS, for example from Ka50 and Su25t. Also you can then use the same push to talk key for teamspeak in all the profiles.

 

It has a few bonus features:

 

 

• Pressing Mic In toggles/cycles TGP scroll speed between 3 different rates. Quick search, Adjust, and Fine.
  
• Pressing Mic Up presses 'j' for teamspeak, but you can remap that in the script.
  
• Pressing the Stick paddle will write "RIFLE" to friendly chat, but you may need to adjust the Chat key to match your's. Mine is R-ALT+M
  
• All lights are turned off, you probably don't want them on.
  
• Most keys are mapped using DX assignments identical to the plug and play functionality (so you don't see them in the script), but once you go above 32 buttons the extra ones require key bindings.
  

 

 

You do however need to map your axis, and a few keys in DCS as they are completely unassigned by default, the mappings required are all commented in the script with // **MAP**

A10C_passthrough.zip

Edited March 2, 2013 by bn880
little title

[Ebs]

Very nice bn880!

 

I've been working on my own 'combined' profile of late. I've got it so the stick outputs all 32 DX buttons before resorting to keyboard commands (I'm suspicious of too many keyboard commands getting sent to DCS:World, I'm sure it's possible to overload the engine somehow) All the buttons on the stick are mapped to DX buttons and most of the 'hand on' buttons on the throttle too. I wanted it to act like a regular joystick as much as possible for mapping to the other modules.

 

There's also a couple of tricks in there too. all the LEDS are fully programmed (throttles on idle..all leds off. flaps down, 1 LED on..speedbrake LED etc.)

 

and I have a couple of 'switched' commands using the stick paddle. paddle + mastermode switch toggles A2A refuelling curve. holding down paddle reduces the slew sensitivity..stuff like that. A10 and KA50 are mapped. Moving onto FC3 next :) I might release it when I'm done....if anyone's interested!

[Seil]

Congrats Ebs! Welcome to the party!

 

I haven't applied my program yet, I have one in the works as well (almost done). Plan to keep everything stock save for PTT and running my backlighting and LED control from export data ;)

 

-Seil

[Ebs]

Plan to keep everything stock save for PTT and running my backlighting and LED control from export data ;)

 

Now that's just showing off! ;) Totally cool idea btw.

 

I never thought the WH would impress me so much. It's the gift that keeps on giving! :joystick:

[Seil]

Thankya 8)

 

I'll drop the source if you want, I'm just trying to finish designing the light state logic for alarms and such right now..... dunno, maybe I otta make a full out thread for this profile :music_whistling: but, I'm setting cms push as a two state (long /short) where short is normal in-game with just a standard dx binding and the long is PTT ;) ...... c'mon you know you like that!

 

Used to be only a push for me on the G940 as PTT... best of both worlds :D

 

Mic SW UP / Push are also un-used in the real bird (at least according to the spec we have) so those are also setup as aux PTT commands

 

Paddle is shift... although there's only TiR center bound as shift + master mode on the stick for easy access (I'm smoking like a chimney out the window to the side)

 

...and some overrides for backlight intensities that are using the shift + MFD rockers

 

Also, shift + ???? unknown button, thinking about using left throttle button will trigger an internal hotas startup calibration mode - basically using the 5 LEDs to designate any controls that are not returned to starting position for quickly resetting the hotas for a new flight (saves a lot of time when you're drunk)

 

any other ideas are welcome, I'm trying to keep the base controls STOCK and have minimal management controls on the shift states - HUGE improvement over having to SHIFT + EVERYTHING to a couple limited D-Pads on lesser sticks. :p (referring to a couple from a particular brand in specific)..... (also have TiR so trim is accessed without a shift like the real bird)... planning to test TM trim vs sim trim, any comments?

 

LED feedback via export conditions are represented via on/off as well as blinking states w/ variable patterns and rates.... I'm really not getting too carried away here, I currently have the 4 light boxes under the extinguisher handles (gun ready, nosewheel, marker beacon, canopy lock) as on/off with the four MFD LEDs... and then blinking patterns for GCAS, Engine failures, master caution... ????

 

Trying to capture the "head's up" spirit with those LED's (not having dedicated replicas of everything in the pit)

 

I have on the fly intensity adjustment capabilities for the backlights (I like to have some light on my real controls without them on in the simulator's cockpit) although I thought it'd be cool to have it synchronized.

 

And on/off MFD and Throttle back lights when power is supplied to your systems :D

 

Hopefully I'll get some time this week to wrap this and that other project up ;) Anyways.... sleep is needed.

Edited March 6, 2013 by Seil

[Walking Dude]

...Is that I didn't get them sooner! Haha! ;)

 

Seriously though, this thing is awesome. I had an X52 (non pro) before and a MSFFB2 before that...But the Warthog? Wow.

 

I'm not knocking the X52. It served me well and I had it set up exactly how I wanted it, but after two days with the Warthog I doubt I could ever go back to the 52.

 

One thing's for sure, the Warthog takes some getting used to. The first flight felt like I was arm-wrestling Schwarzenegger and nothing was where it was supposed to be! (like on the X52 I mean!) and I felt myself overcorrecting everywhere. I didn't expect it to be so sensitive. It almost feels like it's force sensing, honestly.

 

The Saitek programming software is pretty deep, but I didn't expect the level of programming available via target. Of course, everything's plug and play with the 'hog but being a developer in my day job, I took a look at some Target stuff and it blew me away. One of the reasons for getting the Warthog was so I wouldn't have to do so much tweaking...But seeing the possibilities with Target threw all that out the window :)

 

As for the pedals...can't complain. I had a set of CH Products pedals years ago but I couldn't really get over the fact that they were so close together. the Saitek's feel so much better in that regard. Quick deadzone setting and invert for the toe breaks in DCS and all is set.

 

In short, I can't be happier.

 

How is it plug and play. I have the TH and the Saitek combat rudder pedals, and try to fly the Su-25t, and none of my stuff works. What am I doing wrong?

 

A "developer" who just got the warthog with TARGET eh? You might enjoy this then; I wrote an A10 pass-through TARGET script which basically maps your A10 controls identically to the plug and play operation you get with DCS.

 

The reason for the pass-through is to allow you to switch profiles without restarting DCS, for example from Ka50 and Su25t. Also you can then use the same push to talk key for teamspeak in all the profiles.

 

It has a few bonus features:

 

 

• Pressing Mic In toggles/cycles TGP scroll speed between 3 different rates. Quick search, Adjust, and Fine.
  
• Pressing Mic Up presses 'j' for teamspeak, but you can remap that in the script.
  
• Pressing the Stick paddle will write "RIFLE" to friendly chat, but you may need to adjust the Chat key to match your's. Mine is R-ALT+M
  
• All lights are turned off, you probably don't want them on.
  
• Most keys are mapped using DX assignments identical to the plug and play functionality (so you don't see them in the script), but once you go above 32 buttons the extra ones require key bindings.
  

 

You do however need to map your axis, and a few keys in DCS as they are completely unassigned by default, the mappings required are all commented in the script with // **MAP**

 

How do I put this script into DCS world? Or even in Falcon 4.0? Sorry for the newb questions, but I really cant find any setup instructions anywhere.

[FreeFall]

How is it plug and play. I have the TH and the Saitek combat rudder pedals, and try to fly the Su-25t, and none of my stuff works. What am I doing wrong?

Thrustmaster HOTAS Warthog is Plug and Play with DCS A-10C. You don't have to install Target Software.

 

BUT, AFAIK, with SU-25T you have to manually assign the all buttons you want.

[zahry]

Best combo ever :-D

[bn880]

Very nice bn880!

 

I've been working on my own 'combined' profile of late. I've got it so the stick outputs all 32 DX buttons before resorting to keyboard commands (I'm suspicious of too many keyboard commands getting sent to DCS:World, I'm sure it's possible to overload the engine somehow) All the buttons on the stick are mapped to DX buttons and most of the 'hand on' buttons on the throttle too. I wanted it to act like a regular joystick as much as possible for mapping to the other modules.

Cool, yeah BTW that's exactly what happens in the profile I uploaded as well. By default all the stuff is assigned a DX ID, so when you don't see a button in the script, it's automatically acting like DX. :)

 

I guess we were trying to solve the same problem and that's the result

[Walking Dude]

What IS Dx?

[bn880]

Dx is just an acronym for DirectX (referring to Microsoft's Direct Input library)