Closed kmindspark closed 3 years ago
I think this can be floating-point arithmetic issue. The error means that 0 distance primitive pairs on the input are detected. It could be that the compiler over-optimized floating-point arithmetic so that it is fast but not accurate? Eliminate extremely tiny edges or gaps in the input should also help.
Hmm...I've tried varying meshes but the issue seems to remain. Do you know if there is a way to turn off this "over-optimization" of floating point arithmetic?
You can try to build in Debug mode to remove all optimizations. This should help rule this out.
I actually just ran the cmake and make commands once more and the error disappeared. Not sure why, but it works now :)
Thanks for the help.
I get this error when trying to run IPC on a custom rope mesh.
A friend is able to run the same .txt file with the same mesh on a different computer. Do you have any suggestions on what the root cause may be? The tutorials run fine for me.