Decimation Master is Broken

[Snugg]

I think maybe Decimation Master is broken in 2022.0.2 - I’ve had multiple failures in the past week where it just sits there with near 0% activity in Task Manager when it gets to the point of ‘reordering…’ It just sits there forever and never gets to the point where I can choose what level of decimation I need.

It does this with low and high poly count models. I’ve deleted the cache…manually tracked down and deleted cache via Windows Explorer. I also have my config where it deletes the cache automatically on startup etc.

There doesn’t seem to be any rhyme or reason to it…I decimated one model of a fish OK, then imported a mirrored version of the same fish and it failed to decimate. (I use ZB for 3D scan cleanup - models are already watertight).

What’s interesting is prior to 2022.0.2 (even in 2022.0.0) - if you pressed any decimation amount before pre-processing, it would yell at you saying you needed to pre-process first. Not now…It either just works without pre-processing OR it just hangs up trying to reorder the pre-processed result.

QUESTION: What’s the best way to report bugs etc in ZB?

[zber2]

Hi @Snugg

Did you try a Mesh Integrity check first?

@Snugg

QUESTION: What’s the best way to report bugs etc in ZB?

Pixologic Support

[Snugg]

HA! That was exactly it. Thanks brother. I appreciate it!

What’s weird is some of the models were already Dynameshed and I didn’t think I’d have to check integrity of one that was DM’d. But hey…we all know the deal. Every day is a new opportunity to learn something new. I’ll add the mesh integrity/fix to my workflow. Thank you very much!