Real-Time Physics Simulation Forum

Sorry to bring back this old post, but I needed some more details answered if possible. 1. I was curious as to what the stackAlloc object (inside the collision configuration) is used for and what it's size should be based on. 2. In my world I have a large number of static objects that make up the gr...

Excellent news.

I will be grabbing the SVN later this week and trying out the Kinematic controller stuff. I'll offer whatever feedback I can after that.
I hope to use this feature in my current project.

Why do the KinematicCharacterController functions take a btDynamicsWorld instead of a btCollisionWorld?

Isn't the whole point of doing the Kinematic version is to use just collision and not dynamics?

Shouldn't indices always be unsigned?

It doesn't make sense to have negative indices into the vertex array.

The only way to scale is at the shape level.

The only sharing I get when using meshes is the raw vertex/index data that is passed into btTriangleIndexVertexArray (which is then passed into the btBvhTriangleMeshShape). The bt objects are not very big, and they refer back to your raw vertex/index data.

Any word on this?

Doing a convexTest (using a sphereShape) against an object that is a btBvhTriangleMeshShape always results in the hitPoint being ~0.04f away from the actual mesh. This appears to be the default collision margin. I've tried setting the margin on the btBvhTriangleMeshShape and it seems to have no affe...

The project I am working on is using Bullet for collision only, and I need help with stuff I haven't found in the docs or demos. First, the project is a seamless world that is streaming in chunks as you move around, and at any given time there will be about 1000-2000 btCollisionObjects. The majority...

I created an account with the username "Reltham"

I'd like to see/use a wiki, please!

Did this ever get put in?

I'm having issues with querySingleObject not returning any results if the start and end points are the same (or very near each other).

Just a comment on the debug draw stuff. It doesn't appear to ever do any debug drawing if you don't use Dynamics (i.e. CollisionWorld only).

I think the reason you had to cast away the const was that you didn't get the new version of btCollisionShape.cpp/h.

I ran into the same performance issue with rayTest. I was able to get a big savings by having btCollisionObject cache it's Aabb, and have rayTest use that cached Aabb rather than calculate it from the btCollisionShape's Aabb and the btCollisionObject's transform. I had btCollisionObject update it's ...

I got around the problem of "hitting yourself" in rayTest by deriving my own ClosestRayResultCallback from bullet's, like this: struct MyClosestRayResultCallback : public btCollisionWorld::ClosestRayResultCallback { MyClosestRayResultCallback(const btVector3& rayFromWorld, const btVect...