zcaa0g

I wouldn't get a throttle that isn't being made any more. Replacing certain parts won't be easily achievable unless its standard items like Hall sensors and things along those lines. I'm not a fan of the new throttle in terms of looks or capability, but to each their own I guess.

Yeah, the small form factor Virpil base is only around 5" x 5", so about half the dimensions on the standard Warthog base.

I also appreciate the type of material used so it's scratch proof. I don't like scratches so sue me. :smilewink:

Are you the very same LASooner that posts on DirtBurglars? Regardless, Boomer Sooner! :)

I have both a Warthog and the CH Fighterstick and that glass filled nylon polymer will far out last that cheap Chinese metal used in the Warthog. Anyone that criticizes the durability of CH's "plastic" is ignorant, plain and simple. And that's how I really feel. :-) While I prefer the Warthog due to ergonomics, there's something to be said for the CH Fighterstick USB which is still flawless after about 15 years of use (same for Pro Throttle). I also got 2 of the throttle quadrants and the CH Eclipse yoke when they were released and they are still going strong as well. Anyway, I am getting off topic, so I will bail out now.

I just wanted to ensure it was a known issue and nothing specific to my configuration. Thanks to all for the confirmation. I was actually able to get them all to show up within Target with IDs 1, 2, 3 and 4 assigned by manipulating the contents in the following path: C:\Program Files (x86)\Thrustmaster\TARGET\DevCfg However, while you can assign key commands, the button doesn't show up for the LED control and when you try to process a script, it will bomb. So it looks like the issue is hard-coded in Target. Oh well. I know DCS will recognize them as separate controllers and this is a DCS forum, but I also use these for several other titles as well, so that is why I was curious. I also have two CH MFPs, so I can work around these issues from a flexibility standpoint.

Greetings, I wanted to check and see if anyone is currently utilizing more than 2 Thrustmaster Cougar MFDs. I currently have 4 connected, but there is a problem where while the Windows gaming control panel applet sees all 4 MFDs and I have them assigned as ID1, ID2, ID3 and ID4 respectively and they all function fine there, when I go into Thrustmaster Target, it only shows 2 of them. And the only way I can have all 4 show up in Thrustmaster Target is to assign two of them to ID1 and two of them to ID2, but then when you go to program them, they would have duplicate assigned keys, which defeats the purpose of having more than two of them. So the basic problem here is if the MFDs are assigned to anything other than ID1 or ID2, while they will always show up in the Windows gaming control panel applet, they will refuse to show up in Thrustmaster Target. Has anyone seen this or is this a known problem? It seems everything is fine at a hardware level.