Horde3D

I imported a model that had a mesh that did not contain any vertices. This caused h3dGetNodeAABB to report a huge bounding box for the scene node.
The problem is in ModelNode::updateLocalMeshAABBs(). If a mesh does not contain any vertices, bBMin and bBMax are assigned the value +- MaxFloat and never reassigned since there aren't any vertices.

The solution could be to add a

around the assignment and inner loop.

Good spot! What is _vertRStart and _vertREnd in this case? Because normally the loop should be processed if both are equal for at least one vertex even if there are no vertices part of the mesh if the geometry resource has some vertices defined. I guess in this case _vertRStart and _vertREnd are zero and the first vertex position in the resource would be used. That's something that would be probably wrong too, but it shouldn't cause a huge bounding box but one around the first vertex in the geometry resource, should it? And if the resource does not contain any vertex I would think that mesh._vertRStart < _geometryRes->getVertCount() does not succeed and therefore would result in an empty AABB (else case).

The resource contained multiple meshes, so even though this mesh had no vertices, _geometryRes->getVertCount() was non-zero. I think _vertREnd was 71 and _vertRStart was 72 or something like that.

Ah ok, so vertRStart was bigger than vertREnd.

I guess the following patch should fix it (as you already suggested), shouldn't it?

I'm using the same fix locally and it appears to work.

Thanks for the feedback, fixed it in the trunk