Am 09.03.2012 20:57, schrieb Renk Thorsten: >> Ok I haven't entirely given up on the idea of removing the >> auto-coordination from the code. > > Why? > >> Wouldn't it be more appropriate to add >> that rudder control to controls.nas? > > Nasal runs per graphical frame, FDMs may need to run faster at low > framerates. Nasal AP systems tend to become unstable below 15 fps or so (see > the F-14b). > >> Then it can be replaced if need be on a per aircraft basis , but not >> break anything otherwise. > > You can replace it now on a per aircraft basis at the simple expense of > setting a single property to false. If the aircraft is equipped with a better > system, then that system can do so. Why is that a problem? > >> And maybe it could be slip/skid-ball driven ... my whole >> point is NOT to disable it but make it configurable. > > Yes, them make it configurable on any aircraft you like. But it should not be > absent from any aircraft you haven't touched. What he probably wants is to set --enable-auto-coordination and _not_ use the hardcoded auto-coordination but his own system.
Torsten ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
