Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

when to call geometry. computeBoundingBox() ?

See original GitHub issue

Is there a rule on when to call geometry. computeBoundingBox()and other compute function ?

Issue Analytics

State:
Created 12 years ago
Comments:14 (13 by maintainers)

Top GitHub Comments

5reactions

Arnachecommented, Aug 18, 2017

I know it’s an old topic but the following comment by @alteredq really ought to be in the manual if it is still valid for the current version:

Bounding box is not used internally for anything, it’s there in case you need it somewhere at the application level. It’s not computed at all anywhere automatically, you need to compute it yourself.

Bounding sphere is used for frustum culling and with Ray / Projector. It’s computed automatically just on creation of objects. You need to recompute it manually if you change vertices (change positions, add / remove vertices)

1reaction

alteredqcommented, Jan 23, 2012

Bounding box is not used internally for anything, it’s there in case you need it somewhere at the application level. It’s not computed at all anywhere automatically, you need to compute it yourself.

Bounding sphere is used for frustum culling and with Ray / Projector. It’s computed automatically just on creation of objects. You need to recompute it manually if you change vertices (change positions, add / remove vertices).