For some time, I have had a nusience item or two on my system relative to movement on the ground with any aircraft in FS9 that would occasionally occur. I have mentioned them tagged on to previous posts with no replies that really gave me a solution.1. All aircraft, with or without "Torque" and "P Factor" enabled under "aircraft/reality settings" would want to drift to the left slightly when I was on the ground and the aircraft was in motion. Not unuseable, but certainly a nusience since little dinky "S" turns were a constant necessity to keep the aircraft relatively straight on the center line.2. The second problem was that I could not release my parking brake with my CH foot pedals. The assigned keyboard command worked fine for actuating or releasing the parking brake, so this was no biggy.I was not sure that I had isolated it, but due to a complete computer crash, I reinstalled everything not too long ago. With a new installation of FS9, along with everything else these problems went away.....Until....I calibrated my rudder with FSUIPC (Full purchased program). Please note that this is not a bash against FSUIPC. The majority of what I have depends upon this fine offering to fully function.Being a procrastinator, I delayed fully checking this out until this morning. I moved "FSUIPC.dll", "FSUIPC.ini", and "FSUIPC.log" from my "Modules" folder to my desktop, and cranked up FS9. Both of these problems went away. I then reinstalled a fresh "FSUIPC.dll" into the "Modules" folder. Still no problem. Taxi's straight as an arrow, and the foot pedals release the parking brake normally. Replaced the "FSUIPC.dll" with the one previously removed and both problems returned. Repeated the removal of these files and virgin installation of the "FSUIPC.dll" and everything was perfect.I speculate that this is not a fault of any kind in FSUIPC, but an offset in my foot pedal pots that for practical purposes makes no difference at all in steering, or flying the aircraft. However, when FSUIPC calibrates, it tries to correct this offset and initiates the steering problem. I have no idea why this would affect releasing the parking brake.I do not claim to have any authorative or necessarilly credible idea why this happens and it may be totally system specific to my setup, but if anybody else has these or similar problems, I would respectfully suggest that you give this method a try for a cure. It sure works for me. Remove these three FSUIPC files and replace the "FSUIPC.dll" with a fresh virgin one and see what happens. Then DO NOT recalibrate the rudder pedals useing the FSUIPC provisions. Leave them with the FS9 defaults.Hope this helps somebody else.Happy flying:RTH1585368CFIEDIT Note: BE SURE that you DO NOT delete "FSUI.dll". It has nothing to do with FSUIPC.

Hi RTH,Thanks for the info. By the by, you and I apparently hail from about the same era. I notice your cfi number and surmise it must be from the the 60's when I got mine. Right?Bill

CORRECTION!Time to tuck my tail between my legs and cry Uncle (half ways anyway).Forget what I said in my previous post relative to the taxi and turning problem. It has nothing apparently to do with FSUIPC. (I apologize Peter).The problem with steering returned again and I found the cause to be so simple I overlooked it. Seem to always overlook the obvious.Autocoordination was checked, and my yoke was not truly centered. I centered it and as would be expected, no problem. I also removed the check by auto coordination, and again no problem.Sorry if this mislead anyone.RTHBill: 100% right. I began right in the middle of the 1960's. Good to hear from you.

FYI:I use for the rudder axis calibration the non-linear filter and shape the curves so yaw sensitivity is less around the center and max at the pedal extents. This cures the taxi oversteering common on many models but provides the max rudder deflection in the air when needed. In FS I assign a small null zone to take care on the pedals not exactly returning to zero so there is a "window" range about the center point.With the latest versions you have the option of restricting each calibration snd assignment only to the current aircraft loaded. The latest interim version adds a tiller control that if you have a spare control wheel or old joystick you can have this extra control assigned as a tiller to provide a less sensitive sterring control for the ground. It just connects this extra control to the yaw/rudder axis with less sensitivity and this like the others can be assignable to the loaded aircraft only.

Have the same thing that CH pedals don't release parking brake and don't disarm autobrake on Level-D and other addons. But this only happened after calibrating the brakes in FSUIPC and I actually like that parking brake goes off only by the corresponding switch on the yoke console. Only autobrake doesn't go off, that's sad :(It seems to be that FSUIPC somehow alters the FS controls system...

FSUIPC sits between the pedals, then CH Control Manager if you use it, then FS assignments/calibration, then FSUIPC, then the aircraft model in that order.I do not use CH Control Manager. My FS9 settings have a small knull point (to allow for brakes and rudder not electrically centering each time at zero pressure) and axis reversal. FSUIPC calibration I use the rudder filter to give gentler slopes of sensitivity around the center to reduce taxi oversteering of the nosewheel and max rudder deflection at full pedal. Parking brakes go off as expected on toe brake pressure on all aircraft including the PMDG 737NG and I believe Autobrakes are set off as well on brake pressure.

Are these registered versions of FSUIPC or the generic that comes with addons?I too have this problem with left turning tendencies while on the ground.I use Saitek 52 and CH pro pedeals.

Hello Jeff:In my case at any rate relative to the original post, I use the registered version of FSUIPC as I stated.My suggestion would be to check if you have autocordinated contols checked in your realisim settings. If you do, uncheck them, be sure your foot pedals are centered, and see what happens. As I said, with autocordination checked, I found that my CH Yoke was off center a bit and that was the problem. I strongly suspect that your Joystick might have the same sympthoms. Worth a try.Good luck:RTH

Ronzie:Everything you say makes sense, but to me personally, you might be missing some options without useing the CH control manager.I would respectfully suggest that you check out the provisions from: http://www.schiratti.comand even more for help and advice from Bob Church at:[email protected](Mr. Church is one of those patient people that adds so much to FS).It does involve a learning curve (at least for a dummy like me), but IMHO is well worth it. I have one map that pretty well covers all of the bases for my personal preferences (with double button functions). I also made several others that I never use any more, but the options are plentiful.Just one man's opinion which in no way whatsoever is implied to be better than yours or anybody elses.Respectfully:RTH

I've never had auto coordination checked on. I checked the settings and they were centered perfect, so I opened the null zone a bit and that seems to help. :-)

Registered version.One thing is that you can use the calibration process to read numericly the output from the control so you can see how out of symmetry and how consistent the scaled electrical output is. This can give you an idea of how much null you might require in the FS axis sensitivity scale.One other thing of value is control spike suppression resulting from noisy pots and circuit board crosstalk. This in some cases can prevent jitter of a control.In FS2K2 I did use the CH Manager under Win 98 but mostly for mixed profiles of axis assignments by using its virtual axis swapping feature to effectively combine all devices into two. I first had X-Plane 5.x which only allowed two control devices. In moving to FS2K2 Pro I saw that it took more actual devices so that feature was not needed and CH Manager was suspect at that time for stability. As I needed the then freeware FSUIPC for other uses as it improved and had features redundant to the scaling offered in CH Manager I just decided to abandon CH Manager. FSUIP 3.x fully registered advanced heavily in offered features such as mapping and calibration per unlimited aircraft, hot-key functions beyond those assignable in FS, and so forth and while there can be a learning curve for some of the advanced features I've been very happy sticking with it.