Autopilot Settings

[AllanL]

While fiddling with the instruments in a few aircraft I've noticed that in some the heading settings only adjust in increments of 10 degrees rather than single degrees. The altitude settings can also be in increments greater than the standard 100 feet.

Is this coded into the model rather than any setting in the aircraft.cfg file? I know the DC-2 has a 'rookie' co-pilot coded into the model which holds headings but floats about +/-100 feet on altitude hold. Probably been schmoking shome good dutch shtuff, no doubt.

[Garry Russell]

Hi Allan

Is this FS.X or 9??

[DaveB]

I remember this cropping up before.. a long time ago and longer than I can remember what the answer was I'm guessing that the gauges will only do what they're programmed to do rather than any setting in the aircraft.cfg. For headings.. blocks of 10deg sounds rather off but for your DC2 to hold alt +/- 100ft is probably bang on. The old Sperry AP.. while innovative in it's day was never particularly accurate at holding alt.. from what I've read. Anyone who's had the Pilots Boeing Clipper will be used to this

ATB

DaveB

[AllanL]

Forgot to mention that it was in FS9. The problem occurs with individual aircraft models - the autopilot instrumentation is default microsoft which gives single degree heading adjustments in the cessnas/learjet etc. - but then go all course (ooh matron) in the "offending" aircraft.

[DaveB]

Ahh... I see what you mean

In that case, copy the [Autopilot] section from the Cessna or whatever it is into the model you're using the gauges in to see if that helps.

ATB

DaveB

[nigelb]

I think this can be cured with FSUIPC - here is a quote from the User Guide:

"Fix control acceleration is provided, in FS2002/4 only, to try to fix the occasional stuck control acceleration—i.e. the
problem with some panels where the increments/decrements to values like heading, course, and so on, get stuck at 10 (for
instance—sometimes, for timing reasons, you get rather more unpredictability). These ―accelerations‖ are actually
legitimate when a key or mouse is held down long enough, but it seems some things can make them ‗stick‘. What happens
is that inside FS there's a timing check: closely arriving controls trigger the acceleration. The problem appears to be that
FS does not care whether these controls are all the same or all different. The assumption seems to be that, if they are
arriving that close then they MUST be the same—the user couldn't move the mouse to another spot, or select another key
on the keyboard, so quickly. However, some gauges or other driver programs can be sending controls very fast indeed,
hence the problem. Whether this explains all the cases reported I don‘t know, but it seems likely. "

I have the registered version of FSUIPC and I am not sure this can be changed in the free version. It is on the miscellaneous tab, near the bottom left in a box that is labelled "FS2002/4 only."

Nigel²

[AllanL]

Thanks - I'll give that a go when I can lever No 1 son off youtwitfacetoob. I had to nick this netbook off the HouseDragon to get this far.