-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for models? #61
Comments
Hello, When you absolutly need objects that are not closed in themselves (Concave), you need to create multiple "convex" bodies and join them together to a body acting as a single body with the generic joint and all degrees of freedom restraint. For your question about .obj, there is no actual code that allows to import a .obj to be a collider, which in most cases you would not want anyways. A physical collider should for performance reasons be an object with as few as possible vertices. Luckily .obj is an open format and within any text editor you can easily see the actual vertices of your object with the prefix "v" you pretty much only need to copy those as a Vec3 Array to use them as a collider in OIMO. (You do not need the vn = vertexnormal, or vt=vertextangent only v) |
Supporting Trimesh will be a nice feature as well as HeightField and CCD. I need to rewrite the collision system because it needs mid-phase collision detection though... |
I know that a single triangle’s bounding box can be simulated using multiple bounding boxes, so that means we can load .obj files. Its it possible to add triangles that way?
The text was updated successfully, but these errors were encountered: