Hosting and domain costs until October 2024 have been generously sponsored by dumptruck_ds. Thank you!

Difference between revisions of "func detail"

From Quake Wiki

(func_detail)
m (func detail variants)
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Ericw-tools]] [[qbsp]] supports detail brushes which are similar in concept to Quake 2’s detail brushes.  
+
{{DISPLAYTITLE:func_detail}}
 +
[https://ericwa.github.io/ericw-tools/ Ericw-tools] [[qbsp]] supports detail brushes which are similar in concept to Quake 2’s detail brushes.  
  
They don’t seal the map. To be compatible with existing Quake 1 mapping editors, detail brushes can be added by creating an entity with classname "func_detail". When [[qbsp]] reads the map file, it will add any brushes included in a func_detail entity into the [[worldspawn]] as details and remove the func_detail entity. Any number of func_detail entities can be used (useful for grouping) and all included brushes will be added to the worldspawn.
+
They don’t seal the map. To be compatible with existing Quake 1 mapping editors, detail brushes can be added by creating an entity with classname {{code|func_detail}}. When [[qbsp]] reads the map file, it will add any brushes included in a func_detail entity into the [[worldspawn]] as details and remove the func_detail entity. Any number of func_detail entities can be used (useful for grouping) and all included brushes will be added to the worldspawn.
  
This classname used on brushes textured with [[Textures#fence_textures|fence textures]] will alpha-mask the #255 colored parts of that texture rendering those parts invisible.
+
This classname used on brushes textured with [[Textures#fence_textures|alphatested textures]] will alpha-mask the #255 colored parts of that texture rendering those parts invisible.
  
==Detail variants==
+
==<span id="func_detail_vars"></span>func_detail variants==
func_detail_illusionary
 
func_detail variant with no collision (players / monsters / gunfire) and doesn’t split world faces. Doesn’t cast shadows unless enabled with "_shadow" "1". Useful for hanging vines. Still creates BSP leafs, which is unavoidable without a new .bsp file format.
 
  
func_detail_wall  
+
'''<span id="func_detail_wall"></span>{{code|func_detail_wall}}''' :
func_detail variant that doesn’t split world faces. Useful for when you want a decoration touching a floor or wall to not split the floor/wall faces (you’ll get some overdraw instead.) If it completely covers up a world face, that face will get clipped away, so it’s not suitable for fence textures; see func_detail_fence instead.
+
This func_detail variant doesn’t split world faces. Useful for when you want a decoration touching a floor or wall to not split the floor/wall faces (you’ll get some overdraw instead.) If it completely covers up a world face, that face will get clipped away, so it’s not suitable for fence textures; see func_detail_fence instead.
  
func_detail_fence  
+
'''<span id="func_detail_fence"></span>{{code|func_detail_fence}}''' :
Similar to func_detail_wall except it’s suitable for fence textures, never clips away world faces. Useful for fences, grates, etc., that are solid and block gunfire.
+
Similar to func_detail_wall, but never clips away . It is suitable for fence textures, never clips away world faces. Useful for dense fences, grates, etc., that are solid and block gunfire.
 +
 
 +
'''<span id="func_detail_illusionary"></span>{{code|func_detail_illusionary}}''' :
 +
Similar to func_detail_fence, but with no collision (players / monsters / gunfire), and doesn’t cast shadows unless enabled with {{code|"_shadow" "1"}}. Useful for creating hanging vines or spiderwebs.<br>Combine with a clip brush for fences that can be shot through with hitscan weapons, but blocks movement and projectiles; suitable for [[Half-Life]]-style fences and 2D railings.
 +
 
 +
 
 +
Regular {{code|func_detail}} is analogous with detail brushes in Quake II, whereas {{code|func_detail_wall}} is analogous with the [https://developer.valvesoftware.com/wiki/Func_detail {{mono|func_detail}} in Source 1] (roughly) or [https://twhl.info/wiki/page/func_detail {{mono|func_detail}} with {{mono|zhlt_detaillevel 1}} in VHLT] (closely).

Latest revision as of 00:23, 15 January 2024

Ericw-tools qbsp supports detail brushes which are similar in concept to Quake 2’s detail brushes.

They don’t seal the map. To be compatible with existing Quake 1 mapping editors, detail brushes can be added by creating an entity with classname func_detail. When qbsp reads the map file, it will add any brushes included in a func_detail entity into the worldspawn as details and remove the func_detail entity. Any number of func_detail entities can be used (useful for grouping) and all included brushes will be added to the worldspawn.

This classname used on brushes textured with alphatested textures will alpha-mask the #255 colored parts of that texture rendering those parts invisible.

func_detail variants[edit]

func_detail_wall : This func_detail variant doesn’t split world faces. Useful for when you want a decoration touching a floor or wall to not split the floor/wall faces (you’ll get some overdraw instead.) If it completely covers up a world face, that face will get clipped away, so it’s not suitable for fence textures; see func_detail_fence instead.

func_detail_fence : Similar to func_detail_wall, but never clips away . It is suitable for fence textures, never clips away world faces. Useful for dense fences, grates, etc., that are solid and block gunfire.

func_detail_illusionary : Similar to func_detail_fence, but with no collision (players / monsters / gunfire), and doesn’t cast shadows unless enabled with "_shadow" "1". Useful for creating hanging vines or spiderwebs.
Combine with a clip brush for fences that can be shot through with hitscan weapons, but blocks movement and projectiles; suitable for Half-Life-style fences and 2D railings.


Regular func_detail is analogous with detail brushes in Quake II, whereas func_detail_wall is analogous with the func_detail in Source 1 (roughly) or func_detail with zhlt_detaillevel 1 in VHLT (closely).