Func detail: Difference between revisions
Jump to navigation
Jump to search
m (→Entity Description: Added a useful link.) |
|||
| Line 3: | Line 3: | ||
Like all [[brush entity|brush entities]], func_details do not contribute to [[vvis|visibility]] calculations. However unlike other entities, func_details do not retain any actual entity data after a [[compile]], and therefore are similar to [[world brush|world brushes]] in every other respect - they are solid (unless materials specify otherwise) and block light just like a normal world brush. Thus, they are ideal for optimizing "visual detail" brushes like columns, debris, fences, or even small buildings. | Like all [[brush entity|brush entities]], func_details do not contribute to [[vvis|visibility]] calculations. However unlike other entities, func_details do not retain any actual entity data after a [[compile]], and therefore are similar to [[world brush|world brushes]] in every other respect - they are solid (unless materials specify otherwise) and block light just like a normal world brush. Thus, they are ideal for optimizing "visual detail" brushes like columns, debris, fences, or even small buildings. | ||
To read about the useage of [[func_detail]], see [[BSP Map Optimization#Detail Brushes|BSP Map Optimization - Detail Brushes]]. | |||
==Keyvalues== | ==Keyvalues== | ||
Revision as of 18:35, 2 March 2006
Entity Description
Like all brush entities, func_details do not contribute to visibility calculations. However unlike other entities, func_details do not retain any actual entity data after a compile, and therefore are similar to world brushes in every other respect - they are solid (unless materials specify otherwise) and block light just like a normal world brush. Thus, they are ideal for optimizing "visual detail" brushes like columns, debris, fences, or even small buildings.
To read about the useage of func_detail, see BSP Map Optimization - Detail Brushes.