On Tue, Oct 4, 2011 at 3:10 AM, James Turner <zakal...@mac.com> wrote:
>
> On 2 Oct 2011, at 19:00, J. Holden wrote:
>
> > Still, as a scenery developer and not a programmer, I'm still wondering
> what the limit is before the "swirlies" start floating around. Is it
> vertices? Fans? Triangles?
>
> It's 65536 vertices per BTG, in total. Strictly, this isn't true - the BTG
> format already supports 2^32 vertices / normals / colors in the file, but
> any object (tri / strip / fan) can only specify any index from 0..65535, so
> the higher vertices can't be used in any meaningful way.
>
> The good news is, I have the code to read a newer version basically done,
> which will make all the indices 32-bit, while of course keeping
> compatibility with existing BTG files of the current versions.
>
> Bad news is, we also need to update the writer code, and then measure how
> much the file size increases, after gzip compression.
>
Hi James,
Here's a random idea on the writer side:
Would it be possible to do something like:
if (size of any of my structures are > 65535) then
write_32bit_index_btg()
else
write_16bit_index_btg()
endif
Then we'd be spending are larger index bits on the files that need them, but
not paying the penalty across the board on every scenery file.
Curt.
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
