On Wed, 2002-11-13 at 08:16, Arnt Karlsen wrote: > On Wed, 13 Nov 2002 09:39:05 -0500, > David Megginson <[EMAIL PROTECTED]> wrote in message > <[EMAIL PROTECTED]>: > > > JD Fenech writes: > > > > > Major note: I've been trying to follow FG development for somewhat > > > over a year, and still haven't been able to really figure out how > > > FDMs are handled (are they internal to the software, or are they > > > externally loaded). > > > > The FDMs are the aerodynamic engines (special-use physics engines). > > Unlike most simulators, FlightGear contains several different > > aerodynamic engines: JSBSim (the default), YASim, LaRCsim, UIUC (based > > on LaRCsim), and a few other special-use ones. > > > > The three major FDMs are runtime-configurable using external files so > > that they can simulate the physics of many different aircraft types: > > > > - JSBSim uses XML files scattered throughout $FG_ROOT/Aircraft/ > > - YASim uses XML files stored under $FG_ROOT/Aircraft-yasim/ > > - UIUC uses INI-like files stored under $FG_ROOT/Aircraft-uiuc/ > > > > Before you say anything, yes, I agree that this is wrong. We either > > want something like > > > > $FG_ROOT/Aircraft/fdms/jsbsim/c172r.xml > > $FG_ROOT/Aircraft/fdms/yasim/c172r.xml > > $FG_ROOT/Aircraft/fdms/uiuc/c172r.dat > > > > or something like > > > > $FG_ROOT/Aircraft/c172r/aero/jsbsim.xml > > $FG_ROOT/Aircraft/c172r/aero/yasim.xml > > $FG_ROOT/Aircraft/c172r/aero/uiuc.xml > > ..I like a birds view building block approach: JSBSim can be run as an > external fdm to FG. How about making this the standard approach? > Engine models imho should be called externally again, from the fdms. > All of this is built on top of zlib, plib, SimGear etc. Modules. > With clear interfaces.
I can see the appeal of multiple processes in some instances (such as the need to avoid mixing GPL and non-GPL code). Otherwise, it's unnecessary complication, especially from a users point of view. > > ..some of us like hot OpenGL graphics and neat sceneries to plan and > tweak our next air show. At other times, we analyse and tweak an > airframe or an engine, and then we prefer to burn our cpu cycles in > the fdm and engine models and can live with slow vesa-type graphics. You really don't need to be concerned about such a trade ... the fdms simply do not consume alot of cpu cycles. > > > depending on whether we want to group the aero files together with > > others using the same FDM or together with others for the same > > aircraft type. We could even replace 'aero' with 'physics' to make it > > clear to new users what's going on, since physics engines are starting > > to be heavily used in the 3D gaming world. > > > > > "The modern definition of 'racist' is someone who is winning an > > > argument with a liberal." > > > > > > --Peter Brimelow > > > > What's the modern definition of 'liberal'? > > ..someone who feels Saddam deserves yet another chance. ;-) > > -- > ..med vennlig hilsen = with Kind Regards from Arnt... ;-) > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
