March 27, 201214 yr Hi All,I've been troubleshooting a yoke "X axis" problem since I purchased the complete Saitek Cessnasystem about 2 weeks ago.Long story short, everything works but the left-turn axis of the yoke. The yoke works correctlywhen I'm testing it with the Saitek test panel, i.e., it smoothly increases in value from 0 to 16383 as Iturned the yoke towards its maximum left limit.But, when I try to fly it or calibrate it in FSX or with the registered FSUIPC, the left turn axis goesimmediately from zero to the max of 16383 after turning the yoke towards the left by only 1-2" fromcenter.You can imagine the effect it has on flying - the roll slams hard over to the left when I'mturning the yoke at a normal amount to do a standard-rate turn.I've loaded and tried Saitek's FSX profile, uninstalling and reloading all of the applicable drivers(twice), and I've rebuilt my FSX config. None of it has helped. I downloaded SPAD, but I read that it'sprimary purpose was with the switching units, not the Cessna yoke.I know the hardware is good - the left-turn axis works fine when I'm using the yoke Saitek system testpanel. The problem appears to be rooted in the software interface between FSX and the yoke.When I attempted the FSUIPC (registered) calibration, the readings did the same as in FSX - theywent from 0 to 16383 with very little turn of the yoke. I didn't think FSUIPC would be able to correctfor that, so I didn't go any further. I'm going to re-attempt the FSUIPC calibration again shortly.FSX is the only sim I have, so I can't try the yoke interface on another sim or game.Any information would be greatly appreciated.Thanks!Mark
March 27, 201214 yr Try doing a system restore from a time before you were having the problem. This will repair your standard XMl file in your appdata/roaming/ Microsoft/FSX/controls folder. it has worked for me when I have had a simular issue. Now I keep a copy of it just in case it gets corupted again. If you ck your controller outside of FSX in the control panel and it works there then there is nothing wrong with it. FSX is the culpret.Josh CPU: Intel i9-11900K @5.2 / RAM: 64GB DDR4 3200 / GPU: 4080 16GB /
March 27, 201214 yr Nah, spare that to yourself.Check this out:http://www.saitekfor...ead.php?p=89502I had the same problem...System restore is actually not a bad idea, but it will revert possibly more than just what you need.
March 27, 201214 yr Nah, spare that to yourself.Check this out:http://www.saitekfor...ead.php?p=89502I had the same problem...System restore is actually not a bad idea, but it will revert possibly more than just what you need. Hi Word Not Allowed Thanks for the link I will try that next time this happens to me. I have posted many times about this problem but never got a answer. The system Restore has always worked and I do create restore points about every week so I don't have to re install updates and things like that. Do you by chance know what causes this. I have a yoke, two throttle quadrants a TPM and trim wheel. Also If I do as the link says does that whipeout my controller settins. And if I replace the standard XML file will that restore my setting assignments .Josh CPU: Intel i9-11900K @5.2 / RAM: 64GB DDR4 3200 / GPU: 4080 16GB /
March 27, 201214 yr Yes, it will most surely fubar your assignments, so back up your standard.xml, but: I use only key assignments in fsx, controllers disabled.So I can hardly tell you what happens with joystick assignments, only that those that weren't assigned got default assignments.My problems arose in FSUIPC. After delete, the controller numbers in FSUIPC were changed, thus effectively rendering all my Saitek assignments wrong.Only solution to that, beside new assigning (=major pain) was to note numbers of assignments prior to deleting/connecting them again, and then connect them one by one, and in between starting FSX. It's a process but it works.
March 28, 201214 yr Author Thank you all. A combination of your suggestions and a corrective action (hard slap to right side of head) took care of the "operator error" issue (a.k.a. a short between the headsets). It seems that I failed to go through the complete travel of center - right - center - left during the calibration procedure. Yea, I want to kick my own butt if I had the flexibility to do it...Regardless, I learned a tremendous amount about this area from both of your inputs. Thanks very much! All of what you wrote has been entered into a Word document I keep. I use the "Find" function to look up items as I experience problems in the future. It keeps me from asking the same question twice...Thanks again, Gents.Mark Nault
Create an account or sign in to comment