Hi, thanks for your feedback - you've raised two very good points. The performance has been mentioned before and as you say it's not the quickest because it copies the pixels into new textures to create the shattered pieces. I like your idea of using the same texture and modifying the sprites' vertices so we'll make that change in an update. In terms of the randomness of shattering the pieces, we've had a think about this and we may go down the route of allowing you to shatter the pieces in different ways which can be configured on the component. So we might leave the square grid-style setting that we have now (with optional zig-zag shapes) but also introduce something like a radial shatter from a centre point, which might give you the glass shattering effect you're after. If you have any more suggestions or want to discuss anything else, please feel free to drop us an e-mail. We'd be very interested in how you want to achieve the glass shattering effect - hopefully we can come up with something you can use. UPDATE 21-Nov-2019 Sprite Shatter version 2.0.0 has now been released which improves performance by using sprite vertices to create shatter pieces rather than copying the texture pixel by pixel. This means the shattered pieces can use the same texture as the original sprite which also reduces memory overhead. We've also introduced a new shatter type named "radial" which shatters outwards from a central point. Hopefully this will help you achieve the glass shattering effect you are after. Hope these changes help - we'd love to hear what you think!

Thanks so much for the review, we're really glad you're happy with Sprite Shatter! We'll include support for flipping in the next release. Sprite flipping was introduced in Unity 5.3 so wasn't included in the initial release. Thanks for letting us know about this.

Thank you for bring this to our attention. We have tried to replicate the problem, but managed to successfully publish and run a WebGL project (of the example scene included in the package) in Unity 5.2.1f1 without the error you reported. It may be version-specific, or it may be because WebGL is still in preview mode in Unity, but it seems you managed to get round the issue. If anyone else is having a problem then we'll happily look into it - just contact us and let us know what version of Unity you are using and attach an example project if necessary.