Hi,
I have encountered problems with the HACD decomposition of objects with holes. While "normal"
decomposition works very well, when I try to decompose a tube like shape (but also other shapes with holes, no matter if through or blind hole) the algorithm works for hours without finding any solution. My current tube consists of 1705 triangles. It is essential for me to conserve the hole and tube-shape. Filling it up is not an option.
Are there any special settings for such objects or ist this just a limitation of the decomposition algorithm? I'm using the default parametrs, but even playing with the settings didn't show any improvement...
All hints and experiences are highly appreciated!
Markus
Update: Finally it seems to work, but the decomposition of a simple tube shape took the whole night... is this normal?
HACD Convex Decomposition of tubes and holes
-
- Posts: 178
- Joined: Fri Apr 18, 2008 2:20 pm
Re: HACD Convex Decomposition of tubes and holes
I have also noticed huge (x100) building times when using the new HACD algorithm, compared to the older convex decomposition implementation, but that only happens in debug mode.
are you running a debug mode ?
are you running a debug mode ?
-
- Posts: 2
- Joined: Sun Feb 10, 2013 2:37 pm
Re: HACD Convex Decomposition of tubes and holes
Yes, I'm working in debug mainly, but I'll test wiht disabled debug! However, I am using the "old" HACD (the new one is V-HACD, or which one do you mean?)
and found out that it becomes much faster when I simplify my mesh (ok, that's not really a surprise...).
But still I didn't find the optimal settings for symmerical object with sharp edges: Either it decomposes EACH tringle into one convex shape (when SetConcavity = 0), or it performs very bad and closes holes and so on (when SetConcavity > 0, even for very, very small values)...
and found out that it becomes much faster when I simplify my mesh (ok, that's not really a surprise...).
But still I didn't find the optimal settings for symmerical object with sharp edges: Either it decomposes EACH tringle into one convex shape (when SetConcavity = 0), or it performs very bad and closes holes and so on (when SetConcavity > 0, even for very, very small values)...