Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-07 Thread Lee Elliott
On Monday 05 July 2004 15:17, David Megginson wrote: Erik Hofman wrote: Ok. Until some kind soul decides to use texture filenames without an extension this should be fixed in CVS now. Thanks, Erik -- that's excellent. All the best, David Yes:) - well done Erik - thanks. LeeE

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-06 Thread Mathias Fröhlich
On Montag, 5. Juli 2004 14:25, Erik Hofman wrote: It turned out to be easier than I suspected. I've put a patch in CVS that allows one to add a texture-path/texture-path tag to the animation configuration file. The specified path should be defined relative to the model path. For some unknown

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-06 Thread Ampere K. Hardraade
This is good news indeed! Thanks! Regards, Ampere On July 5, 2004 09:40 am, Erik Hofman wrote: Ok. Until some kind soul decides to use texture filenames without an extension this should be fixed in CVS now. Erik ___ Flightgear-devel mailing

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-05 Thread Mathias Fröhlich
On Sonntag, 4. Juli 2004 13:20, Erik Hofman wrote: It looks like this makes it easy to support different liveries with just a minimal set of changes (actually only the exterior textures should be different) without any changes to plib. It does require some (fundamental) changes to SimGear

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-05 Thread Erik Hofman
Mathias Fröhlich wrote: On Sonntag, 4. Juli 2004 13:20, Erik Hofman wrote: It looks like this makes it easy to support different liveries with just a minimal set of changes (actually only the exterior textures should be different) without any changes to plib. It does require some (fundamental)

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-05 Thread Erik Hofman
David Megginson wrote: Erik Hofman wrote: It turned out to be easier than I suspected. I've put a patch in CVS that allows one to add a texture-path/texture-path tag to the animation configuration file. The specified path should be defined relative to the model path. For some unknown reason it

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-05 Thread Erik Hofman
David Megginson wrote: Erik Hofman wrote: It turned out to be easier than I suspected. I've put a patch in CVS that allows one to add a texture-path/texture-path tag to the animation configuration file. The specified path should be defined relative to the model path. For some unknown reason it

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-05 Thread David Megginson
Erik Hofman wrote: Ok. Until some kind soul decides to use texture filenames without an extension this should be fixed in CVS now. Thanks, Erik -- that's excellent. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED]

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-04 Thread Erik Hofman
Norman Vine wrote: Lee Elliott writes: I think we need to push a patch to the plib developers list that optionally lets one specify the texture directory when loading a geometry file, but still default to the geometries own directory. void ssgLoaderOptions::setTextureDir ( const char *s ) {

RE: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-03 Thread Norman Vine
Lee Elliott writes: I think we need to push a patch to the plib developers list that optionally lets one specify the texture directory when loading a geometry file, but still default to the geometries own directory. see ssgLoad.cxx void ssgLoaderOptions::setModelDir ( const char *s

Re: [Flightgear-devel] Does changing paintjob/livery requirea duplicate aircraft?

2004-07-03 Thread Erik Hofman
Norman Vine wrote: Lee Elliott writes: I think we need to push a patch to the plib developers list that optionally lets one specify the texture directory when loading a geometry file, but still default to the geometries own directory. see ssgLoad.cxx void ssgLoaderOptions::setModelDir (