Reviews and Problems with Saitek Pro Flight Yoke System
Showing 1-10 of 280
big null zone problem
1 August 2015
Summary: After reading several of the conflicting reviews, thought I would give this a try after using a joystick exclusively since buying fsx. Having owned a couple real aircraft and flown a variety of others I realize that a yoke costing a hundred dollars or so is not going to feel like the real thing, but...
Summary: The quality level wasn't as good as I hoped. The yoke wobbled quite a bit and movement wasn't recognized equally when turning left to right (it took more distance to recognize movement to the left than it did to the right after being calibrated).
Summary: Just got this to replace an older Ch that I picked up cheap to get everything up and going. WOW what a difference!!! I did what many feedbacks said and went straight to Saitek's downloads page and downloaded the latest and greatest drivers instead of installing the discs......
Summary: Worth the investment. I use it to brushen up before a flight or checkride. Helped me get back in the swing of things without having to dish out on plane rental. Flight instructors can tell when you practice!!!!
I've had the Saitek Pro Flight Yoke + Pedals and the CH Flight Sim Yoke + Pedals + Quadrant. This is what you need to know.
Christopher Eastridge, Amazon
9 October 2014
Summary: Alright people, listen up. This is the review you want. If you are like a normal person and can't afford the $600-$1000 yoke from PFC without getting divorced then you are undoubtedly comparing this yoke (or the CH Eclipse, same thing really) to the Saitek Pro Flight Yoke.
Summary: I have never flown with a yoke and rudder pedals. Ever since I got my first flight simulator, I've always used a Top Gun Afterburner joystick and throttle combo, with a rocker button for the rudder. So obviously, I'm new to the yoke.
Summary: I purchased the item in August 2013. The USB connection of the yoke would suddenly be disconnected, without any signs or warnings, 15-30 minutes into use in FSX. I suspected it was a computer and/or FSX issue, so I ignored the problem. The issue persisted for several months.