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

func_lod

From Valve Developer Community
Revision as of 09:35, 8 January 2024 by Thunder4ik (talk | contribs) (→‎top: Unicodifying, replaced: {{language subpage → {{langsp)
Jump to navigation Jump to search
Underlinked - Logo.png
This article needs more Wikipedia icon links to other articles to help Wikipedia icon integrate it into the encyclopedia. Please help improve this article by adding links Wikipedia icon that are relevant to the context within the existing text.
January 2024
English (en)Translate (Translate)
C++ Class hierarchy
CFunc_LOD
CBaseEntity
C++ func_lod.cpp

func_lod is an e2 available in all Source Source games.

It is a brush-built model that fades out over a specified distance. Useful for creating world detail that doesn't need to be drawn far away, for performance reasons. Template:Brushmodel

Note.pngNote:The fading is not always consistent; brushes may suddenly "pop" into view depending on where the player is looking. This happens because of a hardware issues with rendering translucent materials. Low-end cards will fade nearer than the distance specified, and smaller objects fade nearer than a larger object with the same fade distance.

Keyvalues

Disappear Distance (DisappearDist) <integer>
Distance at which these brushes should fade out. Acts as "Min Disappear Distance" (and +800 as max distance) in L4D and newer games.
Min Disappear Distance (DisappearMinDist) <integer> (in all games since Left 4 Dead)
Distance at which these brushes should start fading out.
Max Disappear Distance (DisappearMaxDist) <integer> (in all games since Left 4 Dead)
Distance at which these brushes should finish fading out.
Solid (Solid) <choices>
Set whether or not these brushes should collide with other entities.
  • 0: Solid
  • 1: Nonsolid
Note.pngNote:Using AddOutput this entity can be only changed from solid to nonsolid.
Name (targetname) <string>[ Edit ]
The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentname or target).
Also displayed in Hammer's 2D views and Entity Report.
See also:  Generic Keyvalues, Inputs and Outputs available to all entities