Re: [Flightgear-devel] Took advantage of Erik's...
Ampere K. Hardraade wrote: No. What I want to do is tell each of these animation file where the livery resides. I want to be able to tell all of them with in one single file, instead of having to create a new xml file for every animation file. Ah, That's what you meant. I don't think that multiple includes would solve this problem either. One solution might be putting the texture path into a property (and let the top-level model animation configuration file override the default) but that would mean that *every* model has to include a texture path... We would have to think a bit more about this. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
Right now, if one wants to specify a new livery for some of the animation files, he/she will have to do this: aircraft-set.xml + main.xml [ + livery1.xml [ [ + animation1.xml [ + livery2.xml [ [ + animation2.xml [ [ + animation3.xml We can make it possible to do something like this instead: aircraft-set.xml + main.xml [ + livery.xml [ [ + animation1.xml [ [ + animation2.xml [ [ + animation3.xml Regards, Ampere On July 25, 2004 04:31 am, Erik Hofman wrote: Ampere K. Hardraade wrote: No. What I want to do is tell each of these animation file where the livery resides. I want to be able to tell all of them with in one single file, instead of having to create a new xml file for every animation file. Ah, That's what you meant. I don't think that multiple includes would solve this problem either. One solution might be putting the texture path into a property (and let the top-level model animation configuration file override the default) but that would mean that *every* model has to include a texture path... We would have to think a bit more about this. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
Ampere K. Hardraade wrote: Right now, if one wants to specify a new livery for some of the animation files, he/she will have to do this: aircraft-set.xml + main.xml [ + livery1.xml [ [ + animation1.xml [ + livery2.xml [ [ + animation2.xml [ [ + animation3.xml Maybe I am overlooking what is involved but it seems strange to have a different animation file for each livery. Are you sure you cannot put the main animations in a file that can be included by every livery file ? -Fred We can make it possible to do something like this instead: aircraft-set.xml + main.xml [ + livery.xml [ [ + animation1.xml [ [ + animation2.xml [ [ + animation3.xml Regards, Ampere On July 25, 2004 04:31 am, Erik Hofman wrote: Ampere K. Hardraade wrote: No. What I want to do is tell each of these animation file where the livery resides. I want to be able to tell all of them with in one single file, instead of having to create a new xml file for every animation file. Ah, That's what you meant. I don't think that multiple includes would solve this problem either. One solution might be putting the texture path into a property (and let the top-level model animation configuration file override the default) but that would mean that *every* model has to include a texture path... We would have to think a bit more about this. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
Ampere K. Hardraade wrote: I'm sorry, but I still don't get it. Take a look at FlightGear/data/Aircraft/f16/Models/f16.xml: ?xml version=1.0? PropertyList pathf16.ac/path offsets z-m0.15/z-m pitch-deg0.3/pitch-deg /offsets !-- Submodels -- model nameRudderPedals/name pathAircraft/f16/Models/rudder_pedals.xml/path offsets x-m-5.05/x-m y-m0.0/y-m z-m0.14/z-m /offsets /model model nameThrottle/name pathAircraft/f16/Models/throttle.xml/path offsets x-m-4.25/x-m y-m-0.435/y-m z-m0.185/z-m /offsets /model !-- Panels -- model nameICP/name pathAircraft/f16/Models/icp.ac/path offsets x-m-4.635/x-m y-m0.0/y-m ... You can see it is possible to include another animation file in the main animation file just by pointing to the second order animation file (rudder pedals and throttle in this case) instead of pointing to the geometry file directly. I believe this is what you want, isn't it? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
No. What I want to do is tell each of these animation file where the livery resides. I want to be able to tell all of them with in one single file, instead of having to create a new xml file for every animation file. Regards, Ampere On July 24, 2004 03:37 am, Erik Hofman wrote: I believe this is what you want, isn't it? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
I'm sorry, but I still don't get it. Thanks in advance, Ampere On July 22, 2004 03:44 am, Erik Hofman wrote: Ampere K. Hardraade wrote: Thank you. So, is there anyway to include more than one XML file? The reason I ask is because I have multiple mesh files, and each of them has its own XML animation file. I would like to tell all of them where the livery resides in in one single XML file. In most cases it is possible to include an .xml file rather than a .ac or .3ds file. Then you could specify the .3ds (or .ac) file in the included .xml file again (including animations that apply to that object). Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
Ampere K. Hardraade wrote: Thank you. So, is there anyway to include more than one XML file? The reason I ask is because I have multiple mesh files, and each of them has its own XML animation file. I would like to tell all of them where the livery resides in in one single XML file. In most cases it is possible to include an .xml file rather than a .ac or .3ds file. Then you could specify the .3ds (or .ac) file in the included .xml file again (including animations that apply to that object). Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
Ampere K. Hardraade wrote: ...code last weekend, and did this: http://www.cs.yorku.ca/~cs233144/PROTOTYPE.jpg this: http://www.cs.yorku.ca/~cs233144/FINNAIR.jpg and this: http://www.cs.yorku.ca/~cs233144/KLM.jpg Very well done Ampere! I've put them in CVS. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
Thank you. So, is there anyway to include more than one XML file? The reason I ask is because I have multiple mesh files, and each of them has its own XML animation file. I would like to tell all of them where the livery resides in in one single XML file. Regards, Ampere On July 21, 2004 02:50 am, Erik Hofman wrote: Very well done Ampere! I've put them in CVS. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Took advantage of Erik's...
Nice! I just downloaded your update and modified the model files to include the 747 CRT displays to the cockpit. I've also changed my KLM traffic patterns to use the new livery instead. Cheers, Durk ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
