Set up a mission in the editor so I could do a ramp start at Batumi, fly to the range at SP3 and kill some targets i'd set up. Passing SP2, slaved the Mav and TGP to SP and then tried to move the slew control and nothing moved! Gah! I'd done all that and 'no go'!

Restarted PC and it's back working, will have to check that from now on...

Well, you must have missed sumtin in your start-up procedure!


OTOH, next time see if the keyboard commands are still working.

WC

Hey, Mace,
Do a calibration in Windows for your Throttle, and Stick, too. I just brought up my second machine after a SCES racing w/e and had to recalibrate the WH Stick - had to unplug it and replug it to USB and then it worked. I don't think that is a big deal, but I do think that having the microstick calibrated is important.

WC

It's all calibrated through Windows. It happened once before and a restart sorted it out. It's not a start-up problem as it wasn't working in Windows either.

Hi,

Don't want to hijack this thread but a little confused. I assumed the TM HOTAS Warthog needed no calibration (via windows). I.e plug it in and away she goes
???

Is there a good practice when to plug/unplug the TM HOTAS Warthog?

THis slew issue does seem to crop up a bit

I have mine plugged into a powered USB hub as I have loads of USB devices and have had PCs switch off before because of power drain so I think it is when the PC starts up that the slew control doesn't 'load up'. No big problem as a restart sorts it out.

It's always best to calibrate it every now and again. The WH doesn't need any key assignments in DCS A-10C but a calibration doesn't hurt.

I always leave my HOTAS unplugged from USB when not in use, then connect it and check its cal in the windows game controllers app prior to loading a sim. I check all axes, including the hat I use for slewing. Ditto my steering wheel. It may be unnecessary, but I find it good practice, and every time I violate that procedure I seem to find SOME bizarre incident occurs. Especially the auto-calibration thing. I also tend to cycle my stick, throttle, rudder, or wheel and pedals before I start moving (much like you'll see a pilot do during a real preflight) to make sure the sim sees the calibration properly and I don't get some lousy "full up deflection from pulling the stick back just 1mm" response.

To facilitate this, I have a small USB hub/extension cable plugged into the back of the PC that extends to the front so I can easily attach the wheel or HOTAS to it. I don't use my front USB panel because the stupid thing is a bit loose and gets pushed into the case when I plug things in and half-yanked out when I disconnect.


The Jedi Master

Np, SteveUK,

This Warthog unit I was referring to had been disconnected for a week for a car race, and I'd had the stick unscrewed from the base during that time, so I was not concerned that I had to replug the stick into the powered USB hub.

When I got my Thrustmaster MFCDs, one of them would not work. I sent a service request to TM but in the meantime I ran through the Warthog calibration in Win 7 and saw that the throttle's microstick was not behaving very well - and it was not in the sim, either. After I completed the calibration the non-working MFCD came alive and I've not had any issues since.

So, when someone says something about the TM WH microstick, I chime in with a suggestion to calibrate in Windows.

WC

Never had to calibrate my hotas nor the microstick, thought I did it anyway but not noticed any difference.

It's true he does. I sometimes just mention it to wake him up