Phys constraintsystem: Difference between revisions
Jump to navigation
Jump to search
Note:This entity is a valid base entity but only appears in the halflife2.fgd
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{wrongtitle|title=phys_constraintsystem}} | {{wrongtitle|title=phys_constraintsystem}} | ||
{{base_constraint}} | |||
==Entity Description== | ==Entity Description== | ||
An entity used to manage a group of interacting [[constraint]]s and keep them stable. All constraints on a set of entities should be placed in the same system, or they will fight each other during simulation. | An entity used to manage a group of interacting [[constraint]]s and keep them stable. All constraints on a set of entities should be placed in the same system, or they will fight each other during simulation. | ||
| Line 15: | Line 17: | ||
==Outputs== | ==Outputs== | ||
*{{o targetname}} | *{{o targetname}} | ||
Revision as of 17:25, 11 April 2008
Template:Wrongtitle Template:Base constraint
Entity Description
An entity used to manage a group of interacting constraints and keep them stable. All constraints on a set of entities should be placed in the same system, or they will fight each other during simulation.
Note:This entity is a valid base entity but only appears in the halflife2.fgdKeyvalues
- Template:Kv targetname
- additionaliterations <integer>
- Adding iterations makes the interactions among constraints in a system tighter. It will not compensate for errors due to collision, but will help in cases where objects of disparate mass are constrained to each other.