Jon S. Berndt writes: > > The cleanest solution is to have a separate property tree for each > > instance; globals could manage that, and make sure that the right one > > is always returned. > > In at least one of those cases (i.e. the dumb bombs dropping - or even a > guided missile) it's fine if the FGFS side does nothing with it. But, can > you imagine how cool it would be to see a simulated IR view from a missile > fast approaching another aircraft?
That should work. Think of the property tree as the processor state, and each vehicle as a separate process. FlightGear can (eventually) manage a kind of multitasking simply by making different property trees current, transparently to the rest of the program. All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
