CaptJackG

yes

Serial #: 0179 Location: South Carolina, US

Here is a nice TIR setup video from Ralfi

If you plan on flying...get some rudder pedals. I use the mfg pedals. They are excellent and have a really good feel, very close to what you'll encounter in a real plane.

Get the TrackIR first then start a swear jar. In no time you'll have enough for the whole Warthog HOTAS.

I had a very similar problem with WH on X99. Pretty much solve with a MB BIOS update and a PCIe USB 2.0 card for WH.

Thanks for the information ronht, I'm considering purchasing 1 of these.

I'm sorry to hear about your warthog problem, being a warthog owner I can sympathize. But I am impressed with the help and tips and it does make you feel good to know that if you have a problem there are so many willing to pass along their knowledge and expertise.

There is no left hand conversion in aviation. You fly in the left seat your left hand operates the flight controls and the right hand operates the throttles. You fly in the right seat......well, you get the picture. Ergo no left hand conversion.

Your wife will divorce you because of all the sweet nothings you whisper to your pedals.

Absolutely they are worth the wait. I've had mine about 8 months and they are wonderful. I also note that his competitors' newest offering uses a cam like Milan's. Which people are buying and then modifying by adding a dampener. Milan''s need no modification at all.

My friend and I have just noticed the same bug. Some times one or the other of us will have them appear but usually not.

Fons, delete the pitch and roll axis from your Throttle - HOTAS command. All will be well.

In DCS A-10C it functions as a slew control

I'm still fairly new owner myself but I'll share what I've learned. 1. Do not need to use TARGET in DCS A-10C. DCS assigns all the functions as per the actual HOTAS and switches. 2. Yes 3. I've not had any issues but again I'm still fairly new owner. From what I've read it looks like regreasing will fix the problem. 4. The friction lock functions as a slider that you can program for any use, I use mine for zoom view control.

I am a new warthog owner and I've done a lot of research on TM problems. I recently had to replace my desktop due to a lightning strike in the home. My new machine has an ASUS X99. At the same time I went from CH to Warthog Hotas. I could not get the new computer to boot with TM plugged in, or for that matter anything more that a mouse. After a couple of calls to IBuyPower (where purchased) tech support I updated the Bios on the MB and most of my problems went away. I also had to run a program to find unrecognized devices to update their drivers to fix some problems in Device Manager. The long and short is now everything is working mostly fine...a few little boot glitches every once in a while. I found this post from a few years ago and have saved it for future use just in case. Warthog on Asus x99 Hello. I have been having real problems with my Warthog, and indeed my MFDs after a major computer update. I now seem to have solved them, with the help of Thrustmaster Technical Department. I want to outline what worked for me so any other poor bugger having the same problems has a head start in solving them. The Problem. I upgraded to an Asus x99 Deluxe motherboard and SLI 980s ect. I also went from Win 7 to Win 8.1 64 bit. As you may know, the new motherboard had predominantly USB 3 slots, and as you probably won't know, Win 8.1 introduced a new way of managing power to these USB ports. Both facts are relevant, as it turned out. The Symptoms. The computer suddenly became unstable when it booted up with the USB peripherals attached. In particular, Win would not recognise my Warthog joystick: it was listed as a 'Bootloader', and to make matters worse, when I tried to update the firmware, it would not load, and consistently failed at step 2 with the error message of 0x0000000c. I ended up with both my joystick and throttle without any firmware at all, and always being listed as Bootloader when I attached the cables into the USB slots. So..unstable computer that hung randomly on loading, and Warthog throttle and joystick not working. What I Tried. I first unloaded everything to do with the Warthog, re downloaded all the latest drivers and tried to reload drivers. No good; did not work. Then I followed the Thrustmaster advice on their website to 'wake up' Bootloader joysticks. I followed the instructions to the letter; this did NOT work, no matter how many times I followed it. Next, I tried setting up the Warthog on a seperate, older machine, with only USB 2 ports. No good. Did not work either; the firmware update kept failing at step 2 with error 0x0000000c. I was in despair. What Finally Worked For Me. I sent an email, in my despair, to TM support. In the meantime, I trawled the web. There was ONE post on the SimHQ website, just one, about a guy complaining about Win nit booting properly with a Warthog attached. The solution was to go into the BIOS to disable something called xHCI mode in the USB configuration settings. The guy disabled the xHCI mode and it sorted the problem. Upon doing research, I discovered that Intel xHCI controlled the USB ports: xHCI equalled having the USB ports active. Turn it off, and the ports reverted to USB 2. So the problem had something to do with peripherals, especially the Warthog HOTAS, being plugged into this Intel controlled xHCI USB 3 ports. Something was not gelling. So what I tried was to turn off in my BIOS the xHCI mode, then reloaded the Warthog drivers, following the prompts, and IT ALL WORKED! Especially, the firmware updated with no problems. My HOTAS was with firmware again, and recognised by the computer again, and working. I then turned the xHCI back to enabled again, and the settings stayed, and the HOTAS was still ok. I might point out here that I had it plugged into USB 3 ports; putting it into the USB 2 ports did not help when it was playing up. The second thing I did related to the way Win 8.1 managed the power settings of the USB ports. There was a work around in the TM message to me that dealt with apparent problems that this new power management arrangemnet of the USB ports that Win 8.1 used. Microsoft has acknowledged that the way Win 8.1 manages the ports has caused lots of compatibility y problems with USB devices. Apparently, the new power arrangement turns power off to the device when Windows thinks it is sleeping or not active. This causes problems, loading, disconnecting and reloading devices to the computer seemingly randomly. It was particularly evident when I attached the TM MFDs. They flicked on and off constantly, flashing lights and causing the computer to bleep constantly, and generally have a heart attack. What I did was to go into device manager, and located the HID device of game controller, click on it, go to device details and find the device path in the registry. I copied the HID/PID unique numerical line, opened Regedit, found the appropriate line under Current, System, Enum, USB, and then TURNED OFF a thing called EnhancedPowerManagement by setting the string entry to 0. This stopped Windows from managing the power of devices attached through the problematic USB ports. Microsoft has a detailed set of instructions on their site to specifically allow people to use this workaround to deal with problematic USB devices. It absolutely worked; the computer became more stable and the MFDs stopped disconnecting, and now behave themselves. I have yet to get to the bottom of the Intel xHCI thingy, but there is a problem I think with the way it relates on newer motherboards and legacy USB devices, which is what all of us have. Conclusion. What did I learn? The way Win 8.1 mangers power to the USB ports, especially USB 3 ports, is problematic and causes problems with devices, such as Warthog joysticks and throttles and MFDs. (Btw, it also caused issues with my Saitek combat flight pedals.) the way to fix it was to turn off in Registry by Regedit this enhanced power management. I also switched the BIOS setting of USB configuration of Intel xHCI to Enabled from AutoSmart...after I had disabled it to fix the Warthog (which did the trick). Any instability, and I will play around with the xHCI setting in the BIOS. Hope this is/will be helpful to users in the future. Happy to expand on anything I wrote here.

30950 USA

I had the CH pedals for several years. They work great. The only issues I ever had was an occasional recalibration...usually after doing ROF for a while. I have sinse upgraded to MFG Crosswind pedals (and I do mean upgraded). There is no comparison between the two pedals. The precision, feel, looks, and support that Milan provides makes them top notch pedals.

I'm a long time Thrustmaster user that ran into problems a few years ago with the Cougar. I finally gave up and changed to CH gear. I'm now back in the fold with the Warthog. Any recommendations on templates that can be used to label switch/button commands. And....is the Target software programming close to the old Foxy software as I was pretty familiar with Foxy. Thanks

I'm a new warthog owner and I've seen past threads about warthog having a problem with usb 3.0. Is that still the case and does it help to go into the bios and change the usb from xhci to ehci. I have a new computer with the ASUS X99 MB and it has 10 usb 3.0 ports. Thanks for any advice.