On December 23, 2004 07:14 am, Roy Vegard Ovesen wrote:
> > When I am modelling airliners, I always put the engines in a seperated
> > model file.  This way, I can swap out the engines without touching the
> > main model.
> >
> > My question is: what should I do in order to have one animation code that
> > works for all engines?  For example: I have one XML file for the engine;
> > how can I make it so that the same script will work on engine 1, 2, 3,
> > and 4, all with different N1 and N2?
>
> For the 2d panel config there is an alias feature that addresses the kind
> of problem you are describing here. The navcom radio 2d instruments use it
> all the time. It allows you to make _one_ xml config file for an
> instrument, and tie it to arbitrary properties when you include it in you
> 2d panel config file. Take a look at the number two navcom radios and the
> number two vor gauges in 2d panel configs.

Interesting, but I don't think that's what I want.

Thanks anyway,
Ampere

_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to