On Sat, 3 Jul 2004 01:19:27 +0100
Lee Elliott [EMAIL PROTECTED] wrote:
As I understand it, the 3d model and texture handling in FG is done via
plib, which treats the texture map path incorporated in the .ac model
file as a relative path.
Relative to what? To the directory containing the .ac
Chris Metzler wrote:
On Sat, 3 Jul 2004 01:19:27 +0100
Lee Elliott [EMAIL PROTECTED] wrote:
As I understand it, the 3d model and texture handling in FG is done via
plib, which treats the texture map path incorporated in the .ac model
file as a relative path.
Relative to what? To the directory
Hi
I'm new around here, and to the FG/plib way of doing these things,
but i'd like to point that there are a lot of textures that can be shared, take
a look at the 747 for example, and so my ideal directory structure would be
like:
example:
a 757 with a panel.rgb, gear.rgb and fuselage.rgb
On Saturday 03 July 2004 09:49, Erik Hofman wrote:
Chris Metzler wrote:
On Sat, 3 Jul 2004 01:19:27 +0100
Lee Elliott [EMAIL PROTECTED] wrote:
As I understand it, the 3d model and texture handling in FG is done via
plib, which treats the texture map path incorporated in the .ac model
On Fri, 02 Jul 2004 16:43:23 -0500
Curtis L. Olson [EMAIL PROTECTED] wrote:
For a particalar model it would be possible to just modify the existing
textures to give it a new livery.
If you want to create an entirely new livery without disturbing the
original, you could make a copy of the
Have pity on me; I'm new to this stuff.
As I get it now, the textures applied to 3D models are specified in the
.ac file (or .3ds file or whatever). This, in turn, means that if you
want a different paint job for the Cessna, or different airline's
livery for the 737, you need a different .ac
On Friday 02 July 2004 23:07, Chris Metzler wrote:
Have pity on me; I'm new to this stuff.
As I get it now, the textures applied to 3D models are specified in the
.ac file (or .3ds file or whatever). This, in turn, means that if you
want a different paint job for the Cessna, or different
Chris Metzler wrote:
Have pity on me; I'm new to this stuff.
As I get it now, the textures applied to 3D models are specified in the
.ac file (or .3ds file or whatever). This, in turn, means that if you
want a different paint job for the Cessna, or different airline's
livery for the 737, you need
Chris Metzler wrote:
[...] a different paint job/livery effectively means a new aircraft.
Is this right?
Pretty much. Although this wouldn't really be hard to fix, if anyone
wants to give it a shot. One way to go about it would be to provide a
mapping somehwere in the aircraft properties
Chris Metzler wrote:
Have pity on me; I'm new to this stuff.
As I get it now, the textures applied to 3D models are specified in the
.ac file (or .3ds file or whatever). This, in turn, means that if you
want a different paint job for the Cessna, or different airline's
livery for the 737, you need
Here is an idea:
Right now, if we want to include an external model, we can do something like:
model
pathdirectory/*.xml/path
/model
What we can do is add a new type of tags called textures. It will be
something like this:
texture
pathdirectory/*.xml/path
/texture
By using these texture
On Saturday 03 July 2004 00:00, Ampere K. Hardraade wrote:
Here is an idea:
Right now, if we want to include an external model, we can do something
like: model
pathdirectory/*.xml/path
/model
What we can do is add a new type of tags called textures. It will be
something like this:
On Fri, 2 Jul 2004 23:23:29 +0200
Durk Talsma [EMAIL PROTECTED] wrote:
When more AI traffic will be added later on, I can see a need to make
this more flexible.
Yeah, that was one of the reasons I asked -- I remember seeing livery
tags in the XML file you demonstrated for scheduled AI flight
13 matches
Mail list logo
