Fracture Voronoi

Submitted by Garp on Sun, 2009-04-05 04:47

Version:

1.1

This script breaks any mesh while preserving its volume.

Additional Info:

v1.0: The object is broken in a number of chunks equal to 'Nb Parts' to the power of 'Iterations', using Voronoi cells. The final number appears on the 'Break' button.
The creation process is visible in the viewport.
For a similar result, it is faster to use several iterations with a small number of parts than creating all the parts in one iteration.
Note that the original object is just hidden, not deleted.

v1.1: In this version, the code has been improved and runs much faster. But there is no viewport feedback any more.
Materials:
- the outer faces keep their original material IDs and the new faces are assigned a unique ID. The value that appears by default is the highest ID in use (by the original object) + 1.
- mapping coordinates (if any) are preserved and somehow 'projected' onto the new faces.
- an extra planar mapping is applied to all the pieces at once and set on its own channel, typically for use with 3D procedural maps, so the pattern flows continuously from piece to piece but sticks to them when they are moved apart.
Hierarchy:
- when using several iterations, it is possible to keep the intermediate generations of parts.
- when linked, each part is parented to the one it is derived from.
- generations are set on their own layers, which are hidden except for the last one.

Enjoy :)

Attachment	Size
FractureVoronoi_v1.1.ms	10.85 KB
FractureVoronoi_v1.0.ms	4.67 KB

Comments

Submitted by Rogerio Nobre on Sun, 2012-09-23 17:05.

Thanks for Script

Very useful script! Thanks for sharing.

Submitted by Garp on Wed, 2012-06-06 07:28.

Not really.

What it could use though is a faster algorithm. Right now it's about the worst possible way of doing it.
And the code is damn uggly.
One day I'd like to try something like the DeWall algorithm. One day...

Submitted by JokerMartini on Tue, 2012-06-05 17:42.

You ever consider further

You ever consider further developing this?

John Martini
Digital Artist
http://www.JokerMartini.com (new site)

Submitted by HillBilly on Thu, 2012-04-19 13:58.

"No ""+"" function for undefined" problem fixed

Thanks Garp,I had the very same problem when running the script and it works fine now that I'm running it inside the 0-100 range!

Submitted by Garp on Sun, 2012-04-01 23:01.

Hi.

Could it be that you used it outside the 0-100 frame range? If so, it's a bug I never came around to fixing. The script creates particles inside the mesh and uses their positions for the pieces. By default, the particles disappear after frame 100, hence the 'undefined'.
If it's not it, then I have no idea.

Submitted by Socratis on Sun, 2012-04-01 20:16.

Small Problem

Hi there I'm pretty new in 3dsmax and decided to use this script for a wall im building. When I select a brick(a box) and i click break into x pieces a MAXScript Rollout Handler Exception comes up saying --No ""+"" function for undefined. Why would that error come up? Thanks!

Submitted by skye19 on Thu, 2011-12-08 06:37.

Material mapping

Firstly, great plugin.

Secondly, the mapping for my material, however, does not stay the same which is a problem for me. Is there a way to fix this so that it remains intact before and after fracture?

I'm using version 1.1 which states that the mapping remains, but this is not the case for me. I have an object with a rock texture material that breaks at a certain time. It will look weird if the material mapping changes suddenly before it fractures.

thanks!

Submitted by missterlobster on Wed, 2011-12-07 13:34.