B3D levels and pick objects inside him

link3rn3l · Post by **link3rn3l** » Sat Mar 22, 2008 3:25 pm

use B3D levels develop with http://www.blitzbasic.com/Products/maplet.php
not work with this funtions

getSceneNodeFromScreenCoordinatesBB
getSceneNodeFromCameraBB

i like point MD2 objects inside B3D levels but not work,,

only work with BSP levels ,, why?

possible bug?

hybrid · Post by **hybrid** » Sat Mar 22, 2008 11:17 pm

Yes, skinned meshes have problems with bounding boxes and getMesh(x) calls, but no hot-fix, yet.

Luke · Post by **Luke** » Mon Mar 24, 2008 3:00 am

I cannot see how this could be related to the bounding boxes problems.

could you post an example or some code and the mesh?

hybrid · Post by **hybrid** » Mon Mar 24, 2008 9:35 pm

The bounding boxes are not correctly calculated and updated for Skinned Meshes. Just check the meshes in the meshviewer with enabled debug output.

link3rn3l · Post by **link3rn3l** » Tue Mar 25, 2008 3:39 am

Luke wrote:I cannot see how this could be related to the bounding boxes problems.

could you post an example or some code and the mesh?

test working:

1. load q3 bsp as octree
2. load md2 as animatenode
3. test camera point functions

all working

test error:

1. load b3d level as octree
2. load md2 as animatenode
3. test camera point functions

function not return nothing

Why not working, if all test is load with octreee??

only work with q3 bsp maps?

is more easy create b3d levels

P.D.: the b3d test mesh is included in maplet :
http://www.blitzbasic.com/Products/maplet.php

..

hybrid · Post by **hybrid** » Tue Mar 25, 2008 10:17 am

So what happens if you don't use an octree. There had been several error reports about octree loading. Also show your full code (the actual C++ code you use), because it might just happen that you create an empty octree selector instead of a wrong one.

Luke · Post by **Luke** » Wed Mar 26, 2008 12:03 am

The bounding boxes are not correctly calculated and updated for Skinned Meshes. Just check the meshes in the meshviewer with enabled debug output.

why aren't they correctly calculated? and being updated isn't a problem, as it's a static mesh.

anyway I'll have a look

hybrid · Post by **hybrid** » Wed Mar 26, 2008 12:08 am

I think the bounding boxes are calculated based on the binding pose of the animation. Using the getMesh(0) method you get the first frame, i.e. the transformed mesh.

hybrid · Post by **hybrid** » Thu Mar 27, 2008 9:22 am

Ok, the only b3d file I found with a (just slightly) incorrect box is the beast model from Psionic. You can see that one leg is outside the bbox in the initial frame. .x has far more problems due to initially transformed submeshes.