VS Renganathan writes:
How about leaving the ascii format as it is 'without further support', so
that we could continue using it. If its possible to leave it in a working
condition without breaking that would be wonderful. Afterall the ascii
format's similarity with Wavefront .obj format
Curt asked:
Is anyone still using this ancient file format?
Yes.
Does anyone have any objections to ending support
in flightgear for it?
Is it easy to create a atg2btg converter (I only have btg2atg) or does
someone write a btg importer/exporter to plib? If so, then it is
completely ok by
Wolfram Kuss writes:
Is it easy to create a atg2btg converter (I only have btg2atg) or does
someone write a btg importer/exporter to plib? If so, then it is
completely ok by me.
Mostly I don't change the scenery (only add objects via ind file etc)
and also I work on this very seldomly, so
So Curtis L. Olson says:
Wolfram Kuss writes:
Is it easy to create a atg2btg converter (I only have btg2atg) or
does someone write a btg importer/exporter to plib? If so, then it is
completely ok by me.
Mostly I don't change the scenery (only add objects via ind file etc)
and also I work
There is a binary to ascii converter named btg2atg (atg = ascii terra
gear, btg = binary terra gear), but not vice versa, at least not that
I know of.
Bye bye,
Wolfram.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Wolfram Kuss writes:
There is a binary to ascii converter named btg2atg (atg = ascii terra
gear, btg = binary terra gear), but not vice versa, at least not that
I know of.
There's not a reverse converter, but it wouldn't be that hard to do if
someone wanted to make one ...
Curt.
--
Curtis
Wolfram Kuss wrote:
Curt asked:
Is anyone still using this ancient file format?
Yes.
Does anyone have any objections to ending support
in flightgear for it?
Is it easy to create a atg2btg converter (I only have btg2atg) or does
someone write a btg importer/exporter to plib? If
Wolfram Kuss writes:
There is a binary to ascii converter named btg2atg (atg = ascii terra
gear, btg = binary terra gear), but not vice versa, at least not that
I know of.
There's not a reverse converter, but it wouldn't be that hard to do if
someone wanted to make one ...
I assert that
I would be able to clean up a *lot* of code if I could jettison
support for the old 'ascii' scenery format. None of the scenery on
the ftp server is in the old ascii format. It consumes more space to
represent the same geometry, file loading is slower, it hasn't been
updated to support newer
Curtis L. Olson writes:
Is anyone still using this ancient file format? Does anyone have any
objections to ending support in flightgear for it?
I think that PPE has support for the old ASCII format but not the new
binary one. Other than that, chuck it.
All the best,
David
--
David
One thing to remember, once you leave the ASCII format, the platform's
byte order becomes important. When you start storing data in binary
format, you might want to use network format so the standard hton*()
routines can be used. This probably seems obvious, but most of the
network code I
Jonathan Polley writes:
One thing to remember, once you leave the ASCII format, the platform's
byte order becomes important. When you start storing data in binary
format, you might want to use network format so the standard hton*()
routines can be used. This probably seems obvious, but
12 matches
Mail list logo
