Real-Time Physics Simulation Forum

This is a weird issue, how much force are you applying for the car to have such a strange behavior ? Btw, to retrieve informations about the wheels, you can use the getWheelInfo() method on the raycast vehicle, for example, to know if the wheel is in contact with the road you can use this code : boo...

I had the same issues as you and went to the same conclusion, I assumed the wiki notes might be based on an older version of bullet and this behavior has changed. For sure, in the recent versions there's no such thing as "one way collision" like the wiki seems to imply, since bullet checks...

Your Makefile seems overcomplicated, the building process has been simplified a lot in the Android NDK r4, you don't have to have to mess around with separate folders and multiple makefiles anymore, you just have to create one simple makefile in "YourProject/jni/..." and put your native so...

The answer is probably that your shape is somehow concave, when using a ConvexHullShape, it'll take all the points and produce some kind of bounding box out of these, (you can't have holes or acute angles on the outside, I hope you understand what i mean, i'm not a native English speaker, huh) You'l...

Of course, take a look at the RayCast demo : btCollisionWorld::ClosestRayResultCallback cb(source, destination); collisionworld->rayTest (source, destination, cb); Once you've done that, and if the ray hit something, "cb" contains everything you need such as the position of the hit, the no...

Thanks that helped me solve the issue.
I was indeed applying the speed of the vehicle before calling stepSimulation() which resulted in variable results, doing it in a tick callback fixed this.

I'm making a small racing game for Android and decided to use Bullet as the Physics engine, so I'm using a btRaycastVehicle and some TriMesh, and so far the simulation is fine, and the speed is great. But I've encountered an issue concerning determinism, after looking into it a bit more, it seems th...