Cheap: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
ThunderKeil (talk | contribs) (added clarification for alternative uses of the term ( translation not updated )) |
||
| Line 6: | Line 6: | ||
Many cheap things can be drawn on-screen/simulated in the world at once, but they are ''generally'' of low visual or computational quality. Decals and other 2D images are examples of cheap objects that do not (necessarily) lack quality. | Many cheap things can be drawn on-screen/simulated in the world at once, but they are ''generally'' of low visual or computational quality. Decals and other 2D images are examples of cheap objects that do not (necessarily) lack quality. | ||
The term is also used in reference to <i>relatively</i> cheap processes, when more than one is available. Such as [[Water_Shader|water]] that uses a cubemap instead of proper reflections. | |||
==See also == | ==See also == | ||
Revision as of 15:59, 13 September 2019
In game design, a cheap entity/effect/function/whatever is one that can be processed very quickly at run-time. As an example, in Source, cheap to draw objects are displacement surfaces, brushes and decals.
Many cheap things can be drawn on-screen/simulated in the world at once, but they are generally of low visual or computational quality. Decals and other 2D images are examples of cheap objects that do not (necessarily) lack quality.
The term is also used in reference to relatively cheap processes, when more than one is available. Such as water that uses a cubemap instead of proper reflections.