[x3d-public] A mono-Coordinate per namespace

[John Carlson]

Thanks!  Useful feedback!  I'll see what I can do to improve Blender
import/exports.

John

On Sun, Apr 21, 2024 at 4:09 PM Michalis Kamburelis <
michalis.kambi at gmail.com> wrote:

> It is not a good practice, if you push it too far.
>
> Some browsers may decide that one Coordinate -> one VBO. Sometimes
> this is good (reuse VBO), sometimes bad (if the VBO is actually really
> huge).
>
> And it means that browsers have to do extra work to calculate optimal
> (tighter) bounding volumes. A browser that calculates bounding volume
> of Shape based on Coordinate contents (not a subset of Coordinate that
> is actually used by indexes) will have large bounding box for all
> shapes. This applies to CGE/view3dscene (through there's a flag now to
> activate slower bbox calculation that looks at indexes, but I heavily
> discourage from relying on it -- it is slower).
>
> Regards,
> Michalis
>
> niedz., 21 kwi 2024 o 02:16 John Carlson via x3d-public
> <x3d-public at web3d.org> napisał(a):
> >
> > Is it good practice to DEF a mono-Coordinate in a namespace and everyone
> else USE it?  Can it have a url field?
> >
> > Where’s the best practices page?
> >
> > Thanks,
> >
> > John
> > _______________________________________________
> > x3d-public mailing list
> > x3d-public at web3d.org
> > http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240421/75bfcdd9/attachment.html>