Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the number of lights supported in OmniLight and SpotLight docs #43724

Merged
merged 1 commit into from
Nov 20, 2020

Conversation

Calinou
Copy link
Member

@Calinou Calinou commented Nov 20, 2020

Follow-up to #43606.

@Calinou Calinou requested a review from a team as a code owner November 20, 2020 13:08
@Calinou Calinou added this to the 3.2 milestone Nov 20, 2020
@@ -5,7 +5,7 @@
</brief_description>
<description>
An Omnidirectional light is a type of [Light] that emits light in all directions. The light is attenuated by distance and this attenuation can be configured by changing its energy, radius, and attenuation parameters.
[b]Note:[/b] Due to current rendering engine limitations, only 8 OmniLights may affect a single mesh [i]resource[/i] at once. Consider splitting your level into several meshes to decrease the likelihood that more than 8 lights will affect the same mesh resource. Splitting the level mesh will also improve frustum culling effectiveness, leading to greater performance.
[b]Note:[/b] By default, only 32 OmniLights may affect a single mesh [i]resource[/i] at once. Consider splitting your level into several meshes to decrease the likelihood that more than 32 lights will affect the same mesh resource. Splitting the level mesh will also improve frustum culling effectiveness, leading to greater performance. If you need to use more lights per mesh, you can increase [member ProjectSettings.rendering/limits/rendering/max_lights_per_object] at the cost of shader compilation times.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if the comment / advice on mesh splitting is still relevant though since you can bump up the max number.
Maybe this should just be a note referencing the project settings (without saying its value which could change and would thus need to be updated here).

Copy link
Member Author

@Calinou Calinou Nov 20, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using a lot of lights on large meshes will still be much slower, so I'd recommend bumping the limit only as a last resort.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright :)

@akien-mga akien-mga merged commit 279f4fb into godotengine:3.2 Nov 20, 2020
@akien-mga
Copy link
Member

Thanks!

@Calinou Calinou deleted the doc-update-light-limits branch March 31, 2021 09:44
@akien-mga akien-mga modified the milestones: 3.2, 3.3 Apr 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants