nCloth caching

#1

I’ve come across what I assume is a bug with the nucleus caching system, I’m just looking for a workaround, or at least confirmation that is broken.

I have a character with multiple cloth pieces skirt01, skirt02 and skirt03. I can select them all and write out a “per-geometry” cache for them once and it does it. Each piece gets their own file(s) with the geo name included e.g. skirt01_cache, skirt02_cache and skirt03_cache, everything works as expected.
If I then select all the pieces again and attempt to write a second cache for each of them, I get a warning -

“// Warning: file: /apps/Linux64/aw/maya2012/scripts/others/doCreateNclothCache.mel line 326: Ignoring per-geometry flag due to existing cache groups. //”

And it writes them all into a single cache file. Which means when I try to use the paint blend weights tool, it freaks out trying to read from two completely different cache files.

It seems to be that if a piece of geo already has an nCache node associated with it, that the per-geo flag is ignored instead of being handled gracefully (adding a 01 or such like to the end of the second cache name)
Is this expected behaviour? Is there a work around which doesn’t require disconnecting the cache node, simming a second cache and then reattaching the first cache manually?

Cheers,

Paul.

#2

I have noticed that when geometry has a name like skirt_01 or skirt01 and the “skirt” sequence runs 1, 2, 3 etc. nucleus and ncache in general may freak out. i believe this is because the shape node gets the number attached at the end.

this may help… rename the geometry skirt_01GEO that way the shape node will always be skirt01GEOShape1.

#3

Thanks, but I’m not sure that’s the issue unfortunately. My geometry has an _mesh suffix, skirt01 was just an example.

#4

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.