Phys bone follower: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(Re-wrote the page with new information)
(These only generate for models with collisionjoints, and should not be placed directly in a map)
Line 1: Line 1:
{{stub}}
{{stub}}
{{ent not in fgd}}
{{ent not in fgd|nolink=1|because=it is generated as part of another entity, and does not function on its own}}
{{base point|phys_bone_follower}}
{{base point|phys_bone_follower}} All props that use a model with [[$collisionjoints]] will generate these. One bone follower is created for every convex piece of its [[collision model]]. These can quickly eat up the [[Entity limit|entity count]]! Enabling the "Disable Bone Followers" keyvalue on the prop will disable bone followers, although the prop will no longer have a functioning collision model, and the model will not be able to [[ragdoll]]. The .phy of a model can also be deleted to remove the collision model and save file space, though this will affect all instances of that model.
 
All props (except [[prop_static]] and [[prop_detail]]), generate phys_bone_followers if they have a [[collision model]]. These bone followers are created for every convex piece of its [[collision model]]. These can quickly eat up the [[Entity limit|edict count]]! However, if the "Disable Bone Followers" keyvalue on the prop entity is set to Yes, the prop will disable bone followers, although the prop will no longer have a functioning collision model, and the model will not be able to [[ragdoll]]. The .phy of a model can also be deleted to remove the collision model and save file space as an alternative.


[[File:Phys bone follower example.jpg|thumb|An example of phys_bone_followers on a complex model. 15 phys_bone_followers are created for each convex piece of the collision model, resulting in 16 entities! The IN represents the server traffic, a staggering amount for 1 model.]]
[[File:Phys bone follower example.jpg|thumb|An example of phys_bone_followers on a complex model. 15 phys_bone_followers are created for each convex piece of the collision model, resulting in 16 entities! The IN represents the server traffic, a staggering amount for 1 model.]]

Revision as of 16:11, 14 June 2020

Stub

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

Icon-NotInFGD.png
This entity is not in the FGD by default.
It should not be put directly in a map because it is generated as part of another entity, and does not function on its own.

Template:Base point All props that use a model with $collisionjoints will generate these. One bone follower is created for every convex piece of its collision model. These can quickly eat up the entity count! Enabling the "Disable Bone Followers" keyvalue on the prop will disable bone followers, although the prop will no longer have a functioning collision model, and the model will not be able to ragdoll. The .phy of a model can also be deleted to remove the collision model and save file space, though this will affect all instances of that model.

An example of phys_bone_followers on a complex model. 15 phys_bone_followers are created for each convex piece of the collision model, resulting in 16 entities! The IN represents the server traffic, a staggering amount for 1 model.

External links

  • Mapping Tricks phys_bone_follower information, and also where the image was received from.