for point A I always assumed it a was refresh issue of the operator stack... because reloading the scene would also bring back the duplicated point clouds attributes.
instead of duplicating a pointcloud with a cache attached, creating a new empty pointcloud and loading the cache would always work. and yes for changing attributes on B is a workaround I use - reloading the clip or repointing it to the same file 'refreshes' its attribute list. On 11 September 2013 07:01, Vincent Fortin <[email protected]> wrote: >>+1 for better mixer integration Vincent :) > I'm curious to know what kind of issues people are having with the mixer. > On my side the main problem is that the pointcloud hosting the MixerOp > looses all attributes. I end up with a bunch of black dots moving around. > It happens pretty randomly but I've managed to isolate a few problematic > scenarios: > > A) load a cache on an empty pointcloud. Duplicate that point cloud. The new > pointcloud is either empty (no particles) or displays as black dots. Not > sure what is going on here: the mixer clip gets duplicated and apparently > assigned to the new pointcloud but fails to display. Worse, if you delete > the new pointcloud, then the original one goes black dots. Only way to fix > that is to clear the source path and paste it back. But I noticed that from > that point on the problem will come back more often as if the mixer was > "corrupted". > > B) If the attribute description of a cache file changes, the mixer will crap > out. That means that if you overwrite a cache file on your hard drive with a > newer version that doesn't have exactly the same content, any pointcloud in > any scene reading that cache will go "black dots". > > C) Mixer applied on top of a reference model: bad idea. It's not 100% > reproducible but happens a lot. Same black dots issue. I don't think it > comes from the delta as this is not stored in there, right? Nonetheless it's > a reference model issue for sure. > > Somehow I get the feeling that this kind of problem happens more frequently > as the scene grows in complexity. Moving pointclouds around from a Model to > another suddenly becomes unreliable as the mixer doesn't alway get > copied/updated properly. > > I hope people can share their experiences so we can get this thing working > properly ONE DAY ;-) > Or maybe I should try using the CacheOnFile node for reading only. > > > On Tue, Sep 10, 2013 at 7:04 PM, Morten Bartholdy <[email protected]> > wrote: >> >> I would definately vote for a reworked centralized cacheing tool which >> left no doubt what is being done. I agree with Eric that the current >> implementation is a mess. >> >> >> >> +1 for better mixer integration Vincent :) >> >> >> >> Morten >> >> >> >> >> >> >> >> >> Den 10. september 2013 kl. 18:06 skrev Vincent Fortin <[email protected]>: >> >> The best way I've found to work around the custom attribute issue is to >> lay down a Log Value node with "Log" actually turned off. I find the usual >> "Attribute Display" trick unreliable especially in batch mode. >> >> I always use the CacheObjectsIntoFile method (aka Cache Manage). Frankly >> for an "out of the box" tool I wouldn't say the Cache Manager sucks. Do you >> have any particular issues other than the custom attribute caching bug? >> >> What really drives me nuts is the total unreliability of the mixer when it >> comes to reading icecaches. I have noticed many scenarios where attributes >> simply vanish for no reason. Only way to bring them back is to clear the >> Source path and paste it back in. Using the mixer for caches is a great >> feature IMHO, too bad it's so unreliable :-( >> >> >> On Tue, Sep 10, 2013 at 12:01 PM, Eric Thivierge < [email protected] >> > wrote: >> >> You're welcome. :) >> >> http://exocortex.com/products/ crate >> >> >> > >
