Talk:Reference mesh: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(Default mesh / Sub-mesh)
(→‎Moved: clear semantics)
Line 1: Line 1:
== Moved ==
== Moved ==
A "mesh" can also be collision, and this page doesn't seem to be talking about the term itself. --[[user:TomEdwards|TomEdwards]] 08:53, 2 May 2008 (PDT)
A "mesh" can also be collision, and this page doesn't seem to be talking about the term itself. --[[user:TomEdwards|TomEdwards]] 08:53, 2 May 2008 (PDT)
: No. In this context a [http://en.wikipedia.org/wiki/Mesh mesh] has ''deformable'' geometry whereas Collision models are made from ''rigid'' hulls. Unlike Meshes, Hulls do not include [[weightmap]]s, [[UV map]]s or [[Skin]]s.- see [[Mesh#Disambiguation]] --[[User:Beeswax|Beeswax]] 14:53, 2 May 2008 (PDT)


== Default mesh / Sub-mesh ==
== Default mesh / Sub-mesh ==

Revision as of 14:53, 2 May 2008

Moved

A "mesh" can also be collision, and this page doesn't seem to be talking about the term itself. --TomEdwards 08:53, 2 May 2008 (PDT)

No. In this context a mesh has deformable geometry whereas Collision models are made from rigid hulls. Unlike Meshes, Hulls do not include weightmaps, UV maps or Skins.- see Mesh#Disambiguation --Beeswax 14:53, 2 May 2008 (PDT)

Default mesh / Sub-mesh

I've run some experiments and I don't see the distinction between a "default" reference mesh and a "sub" reference mesh. It's simply a case of what QC command you use when compiling them into a model - not any kind of property of the meshes themselves.

In the same area, "sub-models" are actually entirely different entities, which have naught at all to do with the reference mesh. --TomEdwards 09:19, 2 May 2008 (PDT)