You won't get a performance boost.
Bounding boxes will now always be bigger (as they should be), as all I added in transformBox is that all 8 corners of the old bounding box are included in the new bounding box. So occlusion will be done in less cases.
Search found 3 matches
- Sun Jul 03, 2005 2:07 pm
- Forum: Bug reports
- Topic: matrix4::transformBox broken
- Replies: 7
- Views: 2119
- Wed Jun 29, 2005 6:24 pm
- Forum: Advanced Help
- Topic: Moving a bounding box
- Replies: 1
- Views: 580
- Wed Jun 29, 2005 6:18 pm
- Forum: Bug reports
- Topic: matrix4::transformBox broken
- Replies: 7
- Views: 2119
matrix4::transformBox broken
I can't really believe nobody noticed this before...
matrix4::transformBox consists of the following code:
//! Transforms a axis aligned bounding box
inline void matrix4::transformBox( core::aabbox3d<f32> &box) const
{
transformVect(box.MinEdge);
transformVect(box.MaxEdge);
box.repair ...
matrix4::transformBox consists of the following code:
//! Transforms a axis aligned bounding box
inline void matrix4::transformBox( core::aabbox3d<f32> &box) const
{
transformVect(box.MinEdge);
transformVect(box.MaxEdge);
box.repair ...