Autopilot sensitivities

[ronzie]

In 2.975 I wonder if I missed any selection that would affect autopilot sensitivities.

Anyway, there have been a few discussions elsewhere regarding poor over or under control of autopilot under approach situations. This might be something you wish to think about.

Also, this might require a suggestion I made some time ago that perhaps those settings which are specific for each aircraft's performance be stored either in that aircraft's folder or in a section of aircraft.cfg.

[Pete Dowson]

In 2.975 I wonder if I missed any selection that would affect autopilot sensitivities.

No. I wouldn't know how to influence any of that -- most over- or under-sensitive behaviour comes about through the aircraft design parameters (in the AIR file and CFG file).

Anyway, there have been a few discussions elsewhere regarding poor over or under control of autopilot under approach situations. This might be something you wish to think about.

Designing aircraft correctly, or writing proper autopilots, are not in my area of knowledge nor really something that I would think belongs in FSUIPC. However, all the facilities for writing your own autopilot through FSUIPC's interface to FS are available. Programs like Project Magenta provide external autopilots which work very well for specific classes of aircraft, provided they are set up with the correct parameters.

Also, this might require a suggestion I made some time ago that perhaps those settings which are specific for each aircraft's performance be stored either in that aircraft's folder or in a section of aircraft.cfg.

Isn't that where they are, already - in the AIR file or, increasingly, in the AIRCRAFT.CFG file? Or am I misunderstanding your suggestion?

If you aren't a programmer or an aircraft designer but want to see a good autopilot designed for a particular aircraft, I think you might need to spread your request to a wider audience. There may be some readers here who can do this sort of thing, but it really isn't likely to be the best place.

Regards,

Pete

[ronzie]

I was referring to each aircraft.cfg have an area for FSUIPC parameters used for that specific aircraft. An example might be throttle mapping and control sensitivities where the user might want different characteristics for each model design.

[Pete Dowson]

I was referring to each aircraft.cfg have an area for FSUIPC parameters used for that specific aircraft. An example might be throttle mapping and control sensitivities where the user might want different characteristics for each model design.

I can implement automatic selection of some parameters based on something like the aircraft name, but I think it would still be better to keep them central, in the FSUIPC.INI, possibly with sections named after the aircraft. Folks do chop and change aircraft and exchange them, so parameters relating to one person's control kit could get imposed on another's, which could cause problems.

Another consideration is that, although, in FS2002, I can actually derive the correct AIRCRAFT.CFG file path, this currently isn't the case for FS2004 and may not always be feasible in any case.

All this will have to wait until I'm in a position to start thinking about new facilities in any case, and would probably go hand in hand with proper axis selection and assignment facilities (instead of relying on the FS CFG file as at present). We'll see. Maybe you'll want to remind me in a few months?

Regards,

Pete

[ronzie]

Thanks for your reply. Take the time to sniff the roses and keep your sanity.