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
m (Robot: fixing template case.) |
m (Robot: fixing template case.) |
||
| Line 8: | Line 8: | ||
==Keyvalues== | ==Keyvalues== | ||
*{{ | *{{KV Targetname}} | ||
*'''additionaliterations''' <integer> | *'''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. | :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. | ||
Revision as of 19:57, 19 January 2009
Template:Wrongtitle Template:Base point
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
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentnameortarget).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
- 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.