Jonathan Polley writes: > > On Saturday, September 28, 2002, at 04:49 PM, Curtis L. Olson wrote: > > > I did a bit of code shuffling with respect to the ExternalNet fdm and > > moved it to it's own subdirectory. > > > > The goal is to also include in that subdir some stand along FDM > > wrapper apps that interface to FlightGear via the ExternalNet > > interface. These would act as examples for people interested in > > integrating other FDM codes this way. > > > > I've started down the path of wrapping JSBSim up, but I'm running out > > of time so hopefully I can hand that off to one of their developers. > > > > I also removed the External fdm because it is replaced by a better > > named NullFDM fdm. The --fdm=external option is stull supported for > > backwards compatibility but maps to --fdm=null (which does the same > > thing.) > > So the only command line change would be to go from > > --native=socket,in,30,,5500,udp --fdm=external > > to > > --native=socket,in,30,,5500,udp --fdm=null
Right, but --fdm=external still works even though --fdm=null is the 'official' way to do it ... > How much of the FGNetFDM strcuture (src/Network/net_fdm.hxx) is being > filled in by the current FDMs? The last time I was playing with it, > the FDMs were just generating position and orientation information. Well, based on n=1, almost all if not all of the values are getting filled in by the fdm. But it is likely that not all fdm's will generate entirely the same output fields, and not all of them will care about entirely the same inputs. I'm thinking of this as a work in progress and expect to add fields in the future to support additional fdm features and more complex aircraft. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program 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
