Hi It seems that this is an old question but still equally relevant.
It fits with some observations that I made where it seems that one of their examples breaks down when replacing their meshes by simple block meshes: https://github.com/projectchrono/chrono/issues/541 I wonder what kind of limitations there are on the collision checking between concave/convex meshes because so far, I've had plenty of issues when working with meshes. mandag den 20. maj 2024 kl. 11.00.47 UTC+2 skrev Halvor Aslaksen: > The problem seem related to the fact that the collision shape doesn't > follow the visual shape when it's falling through the air, similar to what > was described for the multicore collision case posted before this message. > Is this something that must be fixed in the source code, or something that > can be changed in my code? > > tirsdag 7. mai 2024 kl. 09:37:38 UTC+2 skrev Halvor Aslaksen: > >> Hi! >> >> When trying a simple collision case by dropping a cube made from >> ChBodyAuxRef and an imported .stl mesh on top of another trimesh .stl cube, >> they act very strangely. If I change the envelope bullet value to certain >> values (like 0,02) the initial collision is detected, before they merge >> into each other. For other values, the collision is never registered. I've >> made sure the normals point outward in my .stl mesh, and I've also tried >> with a .obj format with the same result. Is there anything I can try to fix >> this problem? >> >> Thank you! >> > -- You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/projectchrono/7b89d452-29c3-4bbb-ab2c-bf665647ca90n%40googlegroups.com.
