CastRay on small collision meshes?

#1 Are you sure that the raycast was accurate from the view position on screen? The flat, centre of screen hud crosshair doesn't appear to be perfect.

#2 I tried looking around the grenade to all sides and it never seemed to pick it up. Also, the raycast does appear to be working properly for other objects (i.e., when I just edge it over where the collision mesh should be, the object is selected).

#3 Isn't raycast calculated on the object's bounding box, not the collision mesh?

I found I had a similar problem with interacting with buttons and small control panels. I had to make the bounding box large on these objects so the player could interact with them.

Also, I know this is obvious, but you haven't overlooked the bitmask?

#4 Did you try to integrate to your DTS a bounding box, a collision mesh and a LOS mesh.

I don't remember exactly what mesh does the raycast test for.

Nicolas Buquet
www.buquet-net.com/cv/

#5

Quote:Isn't raycast calculated on the object's bounding box, not the collision mesh?

Only on Players, who use a bounding box for all collision by default. ShapeBase objects use their collision or LOSCollision meshes for raycasts and other collision.

Quote:I had to make the bounding box large on these objects so the player could interact with them.

That sounds like the problem I'm having.

Quote:Also, I know this is obvious, but you haven't overlooked the bitmask?

Yep, definitely sure. I can use the exact same datablock with a different shape and it works fine. Also, like I said, re-exporting with a larger collision mesh makes it work fine as well.

Quote:I don't remember exactly what mesh does the raycast test for.

Looking through the code, it seems that ShapeBase casts rays against its LOSCol meshes, which are the same as its regular collision meshes if you don't provide dedicated LOS collision meshes. I'll try adding a LOS col mesh - maybe I can just make that larger. However, I'd still prefer to be able to cast rays against any small object I like. Hmm...

#6 This is an issue we had when creating small objects in Onverse. I never actually spent the time to try and debug it but we did exactly what you're thinking. Creating an LOS collsion mesh that was large enough to click.

#7 All right, well, I'm calling this a bug, and it's necessarily a problem with castRay on the TSMesh (or whatever is below mShapeInstance) level, since Shapebase::castRay doesn't really do much but call that.

#8 Would this help?

#9 That looks like it addresses the issue! I'll test it next week when I get back to my dev comp. Any idea of performance hits with that method? Three cross products instead of one? Ah well - at least there's an idea of what causes the problem. Thanks!

#10 So after getting back on my dev comp (:P...) I applied that fix to try and clear up some issues I was having with ShapeBase collision mesh raycasts. It's fixed those, so I think I can safely assume it will fix my small-mesh problem as well!

#11 Only five months later ;)