On 21/05/2013 at 06:28, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Is the effector used in the fracture object?
Originally posted by xxxxxxxx
I guess the cache isnot yet generated at the point you want to access it.
Yes, it is.
As I show in the above post, cache = gen.GetCache() does return the same Object in both the Fracture and the Cloner. It goes wrong with cache.GetChildren()
Simplified this as much I can. Here's the file : http://www.mediafire.com/?tjes5wipm8y2hta
So I use a Cloner and a Fracture and I do this :
cache = gen.GetCache()
clones = cache.GetChildren()
print clones
1. Works with the Cloner.
2. Doesn't work with the Fracture Object : gen.GetCache does, cache.GetChildren does not.
3. I also added a Horrible Xpresso workaround :
When I "refresh" the Fracture Object with a bit of Xpresso , all of a sudden it works (!!), and cache.GetChildren() returns the list I expect.
Problem is that "refresh" consists of modulating between "Explode Segments" and "Explode Segments & Connect". That's ugly and horrible, and will probably do more harm than good.
So, I guess need a way to "refresh" the Fracture Object somehow from inside the Effector's Python.
Any takers ?
I'm either too stupid or not creative enough, but hours of browsing and testing didn't get me any closer.
Thanks for enlightening me,
d