Difference between revisions of "Point Light Attenuation"
(→Explanation) |
|||
| Line 41: | Line 41: | ||
{{note|Note that all mentioned renderers also include an additional range-based masking to slightly fade lighting away near the limit, as this is necessary for performance. But if range is set adequately to only kick in where the original falloff is dim, its effect is perceptually negligible}} | {{note|Note that all mentioned renderers also include an additional range-based masking to slightly fade lighting away near the limit, as this is necessary for performance. But if range is set adequately to only kick in where the original falloff is dim, its effect is perceptually negligible}} | ||
| − | {{note|Keep in mind that physical falloff is not scaled with Range, but mainly influenced by light’s brightness. It is highly recommended to enable tonemapper when | + | {{note|Keep in mind that physical falloff is not scaled with Range, but mainly influenced by light’s brightness. It is highly recommended to enable tonemapper when using it.}} |
= What value should I use? = | = What value should I use? = | ||
Revision as of 06:54, 30 May 2019
Explanation
In real world, lighting attenuation is governed by the inverse-square law:
However, in computer graphics things are a little trickier. Inverse-square law works for real lights because they have area, hence the projection of this area on receiver geometry gets exponentially smaller with distance. Point lights are an approximation and using the law on them produces one obvious problem: as distance approaches zero, lighting intensity approaches infinity.
There are multiple ways to solve it.
Standard Unity rendering pipeline uses a fake falloff curve that looks similar to this:
r = Light Range
This is an arbitrary hand-tweaked function. It does in fact resembles the inverse square curve, except fixed at distance of 5 and then scaled based on Range parameter. It has a nice property of being exactly 1 in the center. Scaling the same gradient allowed Unity to even store it inside a texture. A 8-bit texture unfortunately, that also lacks precision and produces visible banding when rendering with gamma correction.
Bakery's "physical falloff" defaulted to a different formula:
As Unity, it also has the "+1" part to replace infinity with 1, but its range is unlimited and falls off based on distance. A similar function is also used in UE4 (you need access to UE4 github repository to open that link).
However, the "1" constant is still arbitrary and will look different depending on scene size/units.
Frostbite and HDRP use almost unfiltered inverse-square falloff, but clamp it to prevent dividing by zero:
s = Light Size
In both of these renderers, light size is hardcoded to be 0.01 (1cm), which means brightest value of the untinted light is 10000.
Bakery now has an option called Falloff min size. This is exactly the Light Size used in HDRP/Frostbite formula. With this parameter, new Bakery falloff looks like that:
With Light Size being 0.01, it looks similar to HDRP formula, except instead of clamping it will slightly rescale the curve. With a value of 1 it works like the original Bakery falloff.
What value should I use?
When matching Bakery light to a HDRP light, Faloff min size will be automatically set to 0.01 to look identical. This value makes sense if your point light does indeed represent a 1cm emissive surface. However, there are cases when you can set it to a higher value:
- When literally using point lights for larger surfaces (e.g. lamp of a traffic light).
- When building for mobile platforms where lightmap compression is limited and cannot represent extremely bright values well; or tonemapping not possible.
