Particle Collision Event Editor problems with expression in Per Particle (Array)

Anonymous

Particle Collision Event Editor problems with expression in Per Particle (Array)

Anonymous
Not applicable

Hi,

I want to make debris collide with ground and break into smaller pieces like this video. https://youtu.be/Io3r6-WOAdU

 

I used Instancer with several objects and created the new particle by Particle Collision Event Editor. The original particle works with random expression in Per Particle (Array) Attributes to make random object index, scale, rotation and so on. However, the new particle made by Particle Collision Event Editor does not seem to work with any expression in Per Particle (Array) Attributes. It does not instance random object index or random scale/rotation. 

 

The attached screenshot has the second particle instanced objects highlighted which are all the same cubes.

 

Could anyone please tell me how I can make this work?

 

Thank you!

0 Likes
Reply
Accepted solutions (1)
890 Views
4 Replies
Replies (4)

mspeer
Consultant
Consultant

Hi!

 

Please upload a scene-file.

0 Likes

Anonymous
Not applicable

Sorry about that. I'm new to this.

 

I uploaded the test scene file below.

https://www.dropbox.com/s/fulrf96cku051sb/particleCollision_randomInstancer_test.mb?dl=0

 

Please let me know if anything.

0 Likes

mspeer
Consultant
Consultant
Accepted solution

Hi!

This looks like a bug, but could also be a limitation

No creation event will be triggered for the particles created by the collision event.

In this case i suggest to use the inbuilt curves for nParticles and for example use Mass Scale with Input: "Randomized ID" and then use Mass for Object Index (or simply use Mass Scale Randomize). You can do the same with other Curves and Attributes.

0 Likes

Anonymous
Not applicable

It worked! Thank you so much for your help!

Like you said, I just switched the "Mass Scale Input" to "Randomized ID" and set the "Input Max" and "Mass Scale Randomize", and then I set the "Object Index" to "Mass". Now it seems to be working like the screenshot below. 

0 Likes