I'll answer this in part - could be any number of the AE controls pulling eval and draw request (from vis, to count)... I'm not entirely sure why i was asking this, its obvious, and i known it ... i guess i'm curious about the bigger questions... and perhaps if anyone is particularly particle bent, why particleShapes changing their 'geometry' behave differently than any (?) of the other shapes who will trigger draws with the changing data input (if i use the same data stream and plug it in to a crv, without AE ever seeing it, it updates fine in response to data/geometry input changes)... probably a function of their dynamic nature, that you cant trust states until full frame steps are evaluated, different than static geo... though they have this semi-updating character based on viewport draws..
I'm getting hard crashes with particles and viewport 2.0. Particles not updating if they change counts (standard nodes, ..using, say, 'soft body' with enforced history count ... fine with regular emitters [again, prob to do with frame change based states?]). Thanks. -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/118625cc-9fdc-4b22-b3b6-dd5e8cebd1c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
