The Destructible Component

Features

• Runtime plane-based splitting (single or multi-plane)
• Reliable cap triangulation: fan (convex), ear-clipping (concave), CDT (holes)
• Planar UVs for caps to a selectable UV channel; sides keep UV0
• Two submeshes (sides / caps) to assign a dedicated cap material
• Optional convex MeshCollider generation and Rigidbody inheritance
• Recursive fragmentation: None, All, Depth, Volume
• Pooling + scratch buffers to reduce allocations and spikes
• Simple API: ApplyImpact(...) and ApplyImpactWithPlanes(...)
• Fast path skips island detection when a single loop is produced

API notes

• Uses breakingThreshold and useAccumulation with the impactPower you pass to decide if a split occurs. If it proceeds, it generates splitPlaneNumber planes (optionally aligned by optionalDirection).ApplyImpact(point, impactPower, out fragments, optionalDirection)
• Always splits using your planes; ignores breakingThreshold, useAccumulation, and splitPlaneNumber.ApplyImpactWithPlanes(planes, out fragments)
• If reactToCollision is enabled, impact power is derived from Unity’s relativeVelocity × collisionMultiplier, compared against breakingThreshold (respecting useAccumulation).

Included

• Triangulation (standalone usable): Geometry.Triangulation/EarClipping.cs, CDT.csScripts :Destructible (runtime plane-based splitter), FragmentPool, DestructibleDemoController
  Editor: DestructibleEditor
• PDF manual: Destructible_BSP_Splitter_Manual.pdf (offline, step-by-step + API notes)Documentation :
• Simple demo scene showcasing projectile + hitscan usageDemo content :
  Test meshes for triangulation cases (convex, concave, holes)
  Matching materials and textures for those meshes
• Destruction and Geometry.TriangulationNamespaces :

Requirements

• Unity 2022.3+ (tested with Unity 6.3 LTS)
• Meshes must be Read/Write Enabled
• Works with Built-in, URP, HDRP (renderer-agnostic)

Performance

• Reuses internal buffers; GC kept low
• Most cuts yield a single intersection loop (fast path)
• Optional colliders/rigidbodies add runtime cost proportional to fragment count

Limitations & notes

• LODGroup: recommend forcing LOD0 before splitting; avoid reactToCollision on LOD’d objects
• Cap shading: for PBR, caps may look glossier if smoothness/metallic maps don’t match planar UVs; assign a dedicated cap material or author cap textures
• Physics: fresh convex colliders may slightly inflate; dense fragments can initially overlap and depenetrate strongly

Licensing/usage

• No external dependencies. Code is namespaced (Destruction, Geometry.Triangulation).