Re: TBoundSphere performance

Since we are on the topic of TBoundSphere, dont mind me asking one question.
I have a problem working with TMesh which is related to the TBoundSphere and
its picking. My situation is described below:-

I have a few meshes created with TMesh by specifying the vertices, normals
and texture coordinates. When I add all the meshes under 1 TGroup class, the
boundSphere and picking seems to work fine. 

The problem comes when I have a hierarchy of several TGroup classes and the
TMesh are added into the lowest part. An example would be
Model>Geo>Mesh>Triangle where Model, Geo and Mesh (there can be several Geo
and Mesh objects) are subclasses of  TGroups and Triangle is the created
TMesh. When done this way, the TMesh objects cannot be picked or displayed
properly (invisible at certain angle and distance), I suspect its a problem
with the TBoundSphere. Anyone encounter this problem? 

Additional information to this scenario :-

-initBounds is sent to the Model class only after all the TMesh objects are
created and added to their respective parents.
-boundsDepth is set to 2.

Any information in helping me solve this problem would be very much
appreciated.

Thanks.
--

-- 
View this message in context: http://www.nabble.com/TBoundSphere-performance-tp20544414p20549022.html
Sent from the Croquet - Dev mailing list archive at Nabble.com.