Creating custom gibs: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
mNo edit summary
Line 18: Line 18:
  {  
  {  
  break { "model" "mycustomgib1" "health" "1" "fadetime" "0" }  
  break { "model" "mycustomgib1" "health" "1" "fadetime" "0" }  
  break { "model" "mycustomgib1" "health" "1" "fadetime" "0" }  
  break { "model" "mycustomgib2" "health" "1" "fadetime" "0" }  
  }
  }



Revision as of 09:09, 6 May 2008

Stub

This article or section is a stub. You can help by expanding it.

By default, a model whose propdata allows it to break when its health reaches zero, will spawn a bunch of generic gibs according to its base_type material. Whilst this saves a bit of work, it not nearly as satisfying as using a set of custom gibs that actually look like parts of your breakable model.


Modeling

  • Use the original model as a reference, and place gibs over it.
  • Export each gib separately

Compiling

Each gib

Breakable model

$collisiontext
{ 
	break { "model" "mycustomgib1" "health" "1" "fadetime" "0" } 
	break { "model" "mycustomgib2" "health" "1" "fadetime" "0" } 
}
  • break options
    • model
    • ragdoll
    • offset
    • health
    • fadetime
    • fademindist
    • fademaxdist
    • debris
    • burst
    • placementbone
    • placementattachment

See also