"Curtis L. Olson" <[EMAIL PROTECTED]> said: > The DCS system would take care of loading and attaching the 3d models > to the correct place in the scene graph and removing them. It would > call the update() routine for each of their "engines". And it would > probably provide some sort of property interface to the positions, > orientations, and velocities of these dynamics entities. > > That doesn't solve all the problems and address all the issues, but I > think it would be a good start. >
I've been working toward this sort of thing...slowly severing the ties between the model code and the viewer so that we can have multiples of both. The new viewer interface will make it possible to have multiple FDM's and changes I'm planning for the model code over the next week will make it entirely autonomous. Already I have it generating its own local matrix (had to for the tower view). Once this is done we can see what we have and figure out a system for managing the components. As for Justin's project, rendering the moving ship should be quite easy once all I have planned now for the viewer/model is done (probably within a week). All that will be necessary is something that will update the position and orientation values for the ship. It can be a simple as a script that updates properties through the tcp interface every half second. The bigger problem (or so it seems to me :-)) is the one Andy brought up. How you model stopping on a moving runway. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
