I recently added convex decomposition as a CollisionShape type in the Urho3D engine.
The following asserts get thrown for me related to introducing this:
dgMeshEffect3.cpp (line 753):
- Code: Select all
dgAssert (0);
dgIntersections.cpp (lines 164-167)
- Code: Select all
dgAssert (p0.m_w == dgFloat32(0.0f));
dgAssert (p1.m_w == dgFloat32(0.0f));
dgAssert (boxP0.m_w == dgFloat32(0.0f));
dgAssert (boxP1.m_w == dgFloat32(0.0f));
So as an experiment I commented out the asserts to allow the program to run.
After this I get a final assert at the exit of my program indicating memory leaks:
dgMemory.cpp (line 170):
- Code: Select all
dgAssert (m_memoryUsed == 0);
I made a further experiment and commented out that line as well. As expected a third party memory leak detector also detected the memory leak at the exit of my program.
Is there a way the asserts can be turned into traces or something for enabling runtime support for debug mode? Also do you think there a good fix for the memory leaks?
The asserts in dgIntersections.cpp looks like its a check for small boxes? I am not sure what the first assert is about.
Thanks again for your time!