This article's documentation is for anything that uses the Source engine. Click here for more information.

3D model: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(various tweaks)
m (SirYodaJedi moved page 3D Model to 3D model over redirect)
 
(32 intermediate revisions by 16 users not shown)
Line 1: Line 1:
{{LanguageBar}}
{{Source topicon}}
[[File:Xsimodtool-workspace.jpg|thumb|A model being edited in the [[Softimage Mod Tool]].]]
[[File:Xsimodtool-workspace.jpg|thumb|A model being edited in the [[Softimage Mod Tool]].]]
 
{{modernConfusion|BSP brushes are also [[binary space partitioning|compiled into models]]; these are internally referred to as [[bmodel]]s.}}
A '''model''' is a collection of [[Wikipedia:Point (geometry)|points]], or vertices, that form a 3D shape known as a [[mesh]]. The gaps between the points are usually filled with [[Wikipedia:Polygon (computer graphics)|polygons]], and these polygons are usually covered with a [[material]].
A '''3D model''' (hereinafter referred to as the "model") is a collection of [[Wikipedia:Point (geometry)|points]], or vertices, that form a 3D shape known as a [[mesh]]. The gaps between the points are usually filled with [[Wikipedia:Polygon (computer graphics)|polygons]], and these polygons are usually covered with a [[material]].


Models are used for almost every 3D object in Source that isn't a part of a map's underlying [[brush]] geometry. [[NPC]]s, physics objects, guns, and sometimes even buildings are all models.
Models are used for almost every 3D object in Source that isn't a part of a map's underlying [[brush]] geometry. [[NPC]]s, physics objects, guns, and sometimes even buildings are all models.


Models are created in external modelling packages that are not part of the Source SDK. Valve recommend the [[Softimage Mod Tool]], but there are [[Exporting a model|other options]]. The SDK tool [[studiomdl]] is used to compile the packages' files into the [[MDL]] file format that Source understands; see [[Compiling a model]] for more information.
Models are created in external modelling packages that are not part of the Source SDK. Valve currently uses [[Maya]], but there are [[Exporting a model|other options]]. The SDK tool [[studiomdl]] is used to [[Compiling a model|compile]] files exported from a modelling package into the binary {{ext|mdl|2}} format that Source understands.
 
==World vs. View==
 
[[File:Citadel.jpg|thumb|A [[Half-Life 2]] scene consisting entirely of world models.]]


; World Models
To ensure consistency an entity will normally choose its own world model; the three main exceptions to this are {{ent|prop_static}}, {{ent|prop_physics}}, and {{ent|prop_dynamic}}.
: Used by [[Entity|entities]] which appear in the 3D world. To ensure consistency an entity will normally choose its own world model; the three main exceptions to this are <code>[[prop_static]]</code>, <code>[[prop_physics]]</code>, and <code>[[prop_dynamic]]</code>.
; View Models
: Hands and weapons that are designed solely to appear as part of a first-person UI. They are typically far more detailed than world models.


== Why use a model? ==
== Why use a model? ==
[[File:Citadel.jpg|thumb|A [[Half-Life 2]] scene consisting entirely of models.]]


; Detail
; Detail
: A model can have many, many times more vertices than a brush. [[LOD Models|Level of detail]] allows the detail to be toned down when it is too far away to be appreciated, saving performance.
: A model can have many, many times more vertices than a brush. [[LOD Models|Level of detail]] allows the detail to be toned down when it is too far away to be appreciated, improving performance.
; [[Skeletal animation]]
; [[Skeletal animation|Skeleton]] and [[Flex animation|vertex]] animation
: Detailed, efficient, lifelike animation can be achieved with a model. Walking, talking, running, jumping!
: Detailed and lifelike animation can be achieved with a model. Walking, talking, running, jumping!
; Dynamism
; Dynamism
: Unless specifically made to behave otherwise, a model's position, lighting and animation are all completely dynamic. They can go anywhere and do anything.
: Unless specifically made to behave otherwise, a model's position, lighting and animation are all completely dynamic. They can go anywhere and do anything.
; Replication
; Replication
: Every instance of a model is guaranteed to look the same, and you can change all of them at once by modifying one small set of files.
: Every instance of a model is guaranteed to look the same, and you can change all of them at once by modifying one small set of files.
== Console commands ==
; {{cmd|r_flushlod}}
: Reload all models from disc.
; {{cmd|r_drawmodelstatsoverlay|<1/0>}}
: Print the name of the model under the crosshair to the screen.


== See also ==
== See also ==
 
* {{ent|prop_static}}, {{ent|prop_dynamic}} and {{ent|prop_physics}}
*[[prop_static]], [[prop_dynamic]] and [[prop_physics]]
* [[Viewmodel]]
*[[:Category:World Models]]
* [[:Category:World Models]]
*[[Model Viewer|Half-Life Model Viewer]]
* [[Model Viewer|Half-Life Model Viewer]]
*[[Anatomy of a Model]]
* [[Anatomy of a Model]]
*[[Model Creation Overview]]
* [[Model Creation Overview]]
*[[:Category:Modeling]]
* <code>[[:Category:CBaseAnimating|CBaseAnimating]]</code>
*[[MDL]] (Source Model file format)
* [[Prop Download Sites]]
 
* [[:Category:Modeling]]
* [[MDL]] (Model file formats)
[[Category:Glossary]]
[[Category:Glossary]]
[[Category:Level Design]]
[[Category:Level Design]]
[[Category:Modeling]]
[[Category:Modeling]]
{{stub}}

Latest revision as of 16:10, 13 December 2024

English (en)Русский (ru)中文 (zh)Translate (Translate)

A model being edited in the Softimage Mod Tool.
Warning.pngRisk of Confusion:BSP brushes are also compiled into models; these are internally referred to as bmodels.

A 3D model (hereinafter referred to as the "model") is a collection of points, or vertices, that form a 3D shape known as a mesh. The gaps between the points are usually filled with polygons, and these polygons are usually covered with a material.

Models are used for almost every 3D object in Source that isn't a part of a map's underlying brush geometry. NPCs, physics objects, guns, and sometimes even buildings are all models.

Models are created in external modelling packages that are not part of the Source SDK. Valve currently uses Maya, but there are other options. The SDK tool studiomdl is used to compile files exported from a modelling package into the binary mdl format that Source understands.

To ensure consistency an entity will normally choose its own world model; the three main exceptions to this are prop_static, prop_physics, and prop_dynamic.

Why use a model?

A Half-Life 2 scene consisting entirely of models.
Detail
A model can have many, many times more vertices than a brush. Level of detail allows the detail to be toned down when it is too far away to be appreciated, improving performance.
Skeleton and vertex animation
Detailed and lifelike animation can be achieved with a model. Walking, talking, running, jumping!
Dynamism
Unless specifically made to behave otherwise, a model's position, lighting and animation are all completely dynamic. They can go anywhere and do anything.
Replication
Every instance of a model is guaranteed to look the same, and you can change all of them at once by modifying one small set of files.

Console commands

r_flushlod
Reload all models from disc.
r_drawmodelstatsoverlay <1/0>
Print the name of the model under the crosshair to the screen.

See also


Stub

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

Retrieved from "https://developer.valvesoftware.com/w/index.php?title=3D_model&oldid=459152"