User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
matsys:cmat_manual:keywordreference [2006-11-28 10:37] Carsten Removed the meta_noLightmap keyword description, because this keyword was removed from code (lightmap specification takes the functionality) |
matsys:cmat_manual:keywordreference [2007-05-27 12:44] Carsten Updated the clip flags description. |
||
|---|---|---|---|
| Line 102: | Line 102: | ||
| * **''lightMask $turnoff''** This is very similar to ''ambientMask'', but it only affects the per-lightsource passes. This keyword is currently not used in any Ca3DE material. | * **''lightMask $turnoff''** This is very similar to ''ambientMask'', but it only affects the per-lightsource passes. This keyword is currently not used in any Ca3DE material. | ||
| + | |||
| + | |||
| + | ===== Other Keywords ===== | ||
| + | |||
| + | There are also keywords that define other aspects of the material that are not directly related to their rendering. | ||
| + | |||
| + | * **''clip $c1, $c2, ...''** Defines for whom or for which purposes the material is considered solid in clipping (collision detection) computations. This is mostly interesting in game related settings (e.g. with player or monster clip brushes), but also programs like CaLight and others perform ray trace tests that in turn are affected by this keyword. \\ ''$c1, $c2, ...'' must be a comma-separated list of at least one of these flags: ''nothing'', ''players'', ''monsters'', ''moveables'', ''ik'', ''radiance'', ''sight'', or ''all''. The default value (i.e. if you do not use this keyword at all), is ''clip all''. When you use it, the value is first cleared and then additively rebuilt from the parameter list. \\ :!: Note that each Ca3DE map file must entirely be sealed by materials with the ''clip all'' property, or else the map has a leak. \\ Here is an explanation of the individual flags: ( FIXME Several of them not yet implemented...) | ||
| + | * ''nothing'' means that a surface with this material clips against nothing, it is non-solid. | ||
| + | * ''players'' means that the surface is solid to players, | ||
| + | * ''monsters'' means that the surface is solid to monsters (AI entities), | ||
| + | * ''moveables'' means that the surface is solid to moveable entities, | ||
| + | * ''ik'' means that the surface is solid to IK, | ||
| + | * ''projectiles'' means that the surface is solid to the projectiles of weapons, | ||
| + | * ''sight'' means that the surface blocks line-of-sight tests (used e.g. for AI), | ||
| + | * ''bspPortals'' means that the surface clips portals, that is, it is solid to the flood-fill operation of CaBSP. | ||
| + | * ''radiance'' means that the surface blocks the transfer of light energy in the Radiosity computations of CaLight (most walls do, but for example glass and decals usually don't), | ||
| + | * ''all'' means that the surface is solid to all of the above. | ||
| + | |||
| + | * **''surfaceType $st''** Defines the type of the surface. ''$st'' must be one of ''none'', ''stone'', ''metal'', ''sand'', ''wood'', ''liquid'', ''glass'', or ''plastic''. The meaning of the surface types is solely defined by the game code, it will usually use them to play footstep sounds, ricochet effects, etc. | ||
matsys/cmat_manual/keywordreference.txt ยท Last modified: 2013-01-07 12:07 (external edit)