Expensive: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
In game design, an | {{LanguageBar}} | ||
In game design, an [[expensive]] entity/effect/function/whatever is one that takes an unusually long time to process at runtime. As an example, in Source, expensive-to-draw entities include [[Adding Water|water]] and [[lighting|dynamic light sources]] (except titles which use [[deferred lighting|deferred]] or [[clustered rendering|clustered forward]] shading technique). | |||
Care must be taken when implementing expensive concepts, and if possible they should be avoided or | Care must be taken when implementing expensive concepts, and if possible, they should be avoided or optimized. On the other hand, if you have an area that is otherwise very cheap to draw, you have enough leeway to add something more expensive. | ||
==See also == | ==See also == | ||
| Line 9: | Line 11: | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
{{stub}} | |||
Latest revision as of 07:18, 19 May 2025
In game design, an expensive entity/effect/function/whatever is one that takes an unusually long time to process at runtime. As an example, in Source, expensive-to-draw entities include water and dynamic light sources (except titles which use deferred or clustered forward shading technique).
Care must be taken when implementing expensive concepts, and if possible, they should be avoided or optimized. On the other hand, if you have an area that is otherwise very cheap to draw, you have enough leeway to add something more expensive.
See also