I'd rather have that dead-zone requirement than have the buggy, old-hat control manager running. The only issue CHPro Throttle has is the difficulty in precision centre for the mini-joystick axes - so that is more sensitive to dead-zone setting. I am both an electronics engineer and have been flight simming since forever so I know what I am talking about. I have no issues with the controllers at all. I just calibrate using the Windows game controller calibration. Luckily I'm out exploring so my old throttle will work for now.Īnyway, I'm curious about what in-game deadzone setting you need for the mini stick? If you need high settings, is it causing you any problems?ītw, the y-axis down only needs a tiny deadzone, and I can always get the mini stick to return to zero with smaller deadzones if I give it a quick flick down, but I don't think I want try that on a high-g planet. I'd even consider switching out the mini stick, but I don't want to void the warranty. I'm trying to decide whether to return both sticks and wait a few months and try one again, or buy one from another source at a higher cost, or if I should just live with the 'better' one and only return one. The new throttles have date codes of 122017. This is after calibrating each stick in the CH control manager software. I rechecked my original and it still only requires 10 clicks. I guess it's slightly better, but it still seems way out of line. This one requires 48 clicks on the y-axis and 23 on the x-axis. I thought that was crazy, so I ordered a replacement. Long story short, I had to get another and it required 63 clicks on the y-axis and 16 on the x-axis. Not great in theory, but worked fine and I didn't really notice it. I bought one about 3 years ago and had to program 10 clicks (10% I think) deadzone in-game for the mini stick x and y axes.

Ch flight yoke problems