December 25, 201411 yr Hello, I got yesterday the Saitek Pro Flight Cessna yoke system. I installed the latest Saitek driver and smart technology program but the yoke is not recognised in FSX. I am running windows 7 32 bit. Anyone out there has or had the same problem ? When I select properties I get the message that there is an issue with the driver. and also "code 37" I removed an reinstalled the latest driver but no avail. greetings, Dimitri
December 25, 201411 yr Hi Dimitri, Might seem like a silly question - did you restart your computer? Also, I usually never install Saitek drivers... they're awful. I recommend removing it, and using SPAD - - http://fstools.weebly.com Good luck! H e l p k e e p A V S I M f l y i n g
December 25, 201411 yr Hi Dimitri, I got this from the support section of the Saitek site and it worked for me : "To recalibrate in Windows, first remove the USB plug for your controller from the PC. Press and hold the Windows Key on your keyboard and then press the letter R. This will open the Run box. Type regedit and then click ok. The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name. +HKEY_LOCAL_MACHINE+System+CurrentControlSet+Control+Media Properties +Private Properties+Direct Input. Delete any folder inside the Direct Input Folder that begins with VID_06A3. Once deleted, close the editor, then plug the USB back into the original port. Move all the axes of the controller through their full range of movement four times. Now go to the Control Panel > Game Controllers > Properties to check the axes in the test screen." When it looks all a bit scaring to you, trust the advice but make a copy of the Original Register for security. And don't forget to let your PC show hidden files, otherwise you won't see the Register". Cheers, Ben from the Netherlands Ben Rikken, The Netherlands
December 25, 201411 yr Author Hi, I fixed the problem : Saitek drivers are rubbish ! I uninstalled them, removed the yoke in the device manager, plugged it back in and it works now with the generic windows driver. Many thanks for the advice ! Kind regards, Dimitri
Create an account or sign in to comment