4.19 Physical Lights

[rosegoldslugs]

@Tim_Hobson

Hey everyone,

Apologies for the delay. I don’t have an “official” response yet to all the concerns in this thread but know that we’re carrying on some active conversations right now with some of the engineers and are looking at how we can address this in our Documentation.

We’re evaluating how we can best approach this to make the most of the new physical lighting units. Whether that is through examples in the doc, an example map, or something else is still to be determined, but we’re actively looking at improving this. Also, in 4.21 we’ll enable pre-exposure by default, which should help lessen confusion. There is also some setup between the physical lighting units and post process that we want to address to better tie these together and provide detailed example setups as a starting point.

We’ll be evaluating notes from our engineers along with reviewing concerns in this (lengthy) thread. I don’t currently have an ETA for the changes to be implemented in the documentation but hopefully around the 4.21 release timeframe or shortly thereafter.

If anyone has any thoughts or suggestions (that haven’t already been mentioned), please feel free to post them here as we start to look at this over the next week or so.

I noticed that with Pre-Exposure enabled in the current build, the Pixel Inspector doesn’t show the same values as with it disabled. Will this be fixed at the same time? When using physical units, I’ve had to work with it disabled, get my HDR Luminance values to be around the correct cd/m²/nits, then enable it again afterwards. Not a fun process since it has to keep recompiling shaders each time

Thanks for the heads up though! Looking forward to what you guys do to make it more intuitive.