I would like to announce a new Unity3d package Exploder: Realtime mesh explosion system.
Exploder is an ultimate realtime mesh explosion system for Unity. It can explode any game object in a matter of milliseconds! Just tag your favorite game object and call methodExplode from the script. It comes with tons of settings and adjustments based on more than one year of community feedback.
Looks great, just had some fun blowing up stuff in the demo scenes and it worked a treat. Also seems like UV-mapping is taken into consideration nicely. I need this for an upcoming game so Iāll be a likely customer soon!
Just bought it and having a blast with it One thing, usually the exploded object gets divided into bits, but sometimes it just stayes in one piece identical to the original (but as an fragment object) Is it scaling, import scaling or something like that confusing the divider algorithm?
@operatio apps: I had that happening to meshes with holes. Once those holes were closed, it didnāt happen anymore. Not sure if it was just a coincidenceā¦
@woodn, that was no coincidence, now it works correctly. Awesome, thanks. Do you also know anything about UV coordinates and texture in the cut planes?
canāt say for sure as I havenāt purchased yet, but a sprite is just a quad with a texture on it so you should be to do the same thing to it as you would any other model.
Just purchased this package and so far we are pretty impressed. We do have one question though and that concerns the āForceā property and trying to reduce the āblastā of the explosion.
It seems like anything below 10 and the blast seems to stay the same. For a couple of our scenarios, we need a much smaller force blast to happen. Weāve even tried 1.0, 0.1, 0.001, just to see what force and each of the pieces still get thrown pretty far. Basically we are looking for a scenario where say a Vase that just breaks into pieces and falls (maybe very very very light explosive force) but right now, we can only get the vase to explode as if we had a large piece of dynamite inside.
The cutting algorithm looks for meshes in selected radius, meshes close to the center will be cut into more pieces than meshes far from the center. Like in real explosion. It is possible that your object was too far from the center and therefore it got assigned only one fragment piece.
I have just tested with a plane in the āsimple demoā and unfortunately it does not work properly, I will look for the solution today and make an update. I will keep you informed.
yes I know about this, the reason is that I am using box colliders for fragment pieces. I decided for box colliders because of performance. Now when the mesh is cut into pieces and all pieces got assigned box collider it will āexplodeā regardless of small āForceā property because of their collision.
The solution for you is to enable āMesh collidersā (property of Exploder object). However as you probably know mesh colliders are much slower than box colliders. I would like to make some improvements in this area, ignoring collision for fragment pieces and/or compute mesh colliders by myself (convex hull).
@reindeer games I was hoping to have it work much like the uv layout. predefined colors transfer and cross sections get assigned a definable color. Iām hoping to achieve the effect seen in the attached image. (the inner walls would be defined as an inner cube in the model and donāt need to be generated)
Ok, I understand. You want a predefined color (material) for cross sections. Yes I can make it, it should be easy. I will make another script object with fragment options (material for cross section, also can be useful for another future options like sound effect ā¦). And you can assign this script to your object and when it breaks it will apply the settings.
No, it was in center of the radius. So it looks like @woodnās solution was it - closing all holes in the mesh. We had holes on intersecting mesh-parts that where hidden by other mesh-parts. After closing them it fragmentet perfectly, before it did work only about 20% of the time.
Assigning a material for cross section would be great! An additional option could be to use a UV-portion of the already applied material. E.g. set like UV(0,0,10,10). Would be useful on iOS to limit materials/textures, but also for keeping it faster to set up if you donāt need spesific materials with other shaders.
One thing, usually the exploded object gets divided into bits, but sometimes it just stayes in one piece identical to the original (but as an fragment object) Is it scaling, import scaling or something like that confusing the divider algorithm?
