> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/performance/lighting.md). # Lighting The Depence 3D Engine is specifically optimized to render several thousand light sources. Nevertheless, the size and complexity of the light source are crucial. Especially multi-LED fixtures have not just one but sometimes dozens of individually controllable light sources. Depending on the quality settings, Depence can handle these separately. The following points generally affect performance the most: * Multi-source fixtures, i.e., lamps with multiple light sources * Light sources that shine directly into the camera * Shadow calculation * Area lights * Too many omni lights ### **Beams & Projection Deactivation** For each fixture, you have the option to deactivate the volumetric light beam and/or the projection. ### **Shadows** As soon as a light source (or the scene objects) moves, the shadow must be recalculated. This also highly depends on the complexity of the scene! Check your scene for models that do not necessarily need to cast a shadow or are never reached by lamps. Deactivate the "Cast Shadow" property for these models. ### **Area Lights** An area light is a very complex light source due to the realistic reflections concerning surface roughness. Use as few area lights as possible. You can also make them visible only for video/image rendering via the visibility extension. {% hint style="info" %} Area lights are also active when, for example, video content is dark! {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.depence.com/performance/lighting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.