Hopefully this won't affect too many people but for those of you doing communication between multiple copies of flightgear, or with an external flight model process, please take note.
The "External" flight model is a bit misleading in it's name. I'm planning to create a "Null" flight model as a replacement. I'll probably leave the "external" flight model in the code for a while for backwards compatibility, but once my changes are in place, I encourage you to use the "null" fdm instead. The "null" fdm does absolutely nothing. It is simply a placeholder to make everything happy. The expectation is that all the flight model variables will be set some other place ... most likely from an external source (file replay, separate proprietary fdm process, etc.) Hopefully this is just a very minor change for those that are affected and this naming scheme will make more sense to people. Regards, Curt. -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
