[ExtraFPS] Khronos neutral tone mapping has odd high end
complete
Frionil Fang
Preamble: I have no idea about the fineries of tone mappers, but this seems a little on the weird side and even if it's intended, it's not ideal.
The Khronos neutral tonemapper upper end is a little odd, making the sun on most sky settings without a very subdued sun turn into a peach-colored disc with a sharp core. It's like the saturation and luminance curves have very sharp steps in them at high HDR, resulting in the glow around the sun first getting extremely saturated, then the luminance steps up sharply and results in a "core". The effect is less pronounced at higher sun angles, but especially sunsets/rises look off. Basically the sun color needs to be below 50% luminance to avoid the oversaturation and core-forming, but that requires more ambient light etc. to compensate scene brightness.
Is there something that could be done to avoid the saturation-blowout of extremely bright light sources or is retooling even PBR-aware settings required once again to avoid a peach sun?
Comparison images have old mixed-ACES on left, Khronos on right.
Log In
This post was marked as
complete
Dan Linden
tracked
Dan Linden
Thank you for the feedback!
As of ExtraFPS 7.1.11.11565212741, currently in RC, the default tonemapper is once again ACES. The Khronos neutral tonemapper will remain as an option.
Issue tracked at https://github.com/secondlife/viewer/issues/2913
Andred Darwin
Wanted to add to this...
- Some ( not all ) current PBR materials (Already uploaded, ready for "sale" or "update") display noticeably different, specially "in-world outdoors" under EEP using the Khronos tonemapper... what would be the fix (Reds displaying more like "orange")?
- The color picker becomes a best guess comparing color shown at the picker and result in-world (even using lights, blues and reds are completely different, less noticeable for dark colors)
- There are no clear instructions on how to make Substance generate those colors, and the config.ocio available at one of the links at the Wiki, crashes Substance...
Even if there is a great benefit adding that tonemapper, the "Default", probably, should be the ACES one... at least until you guys have a chance to iron out the specifics... it's not like this rollout (almost 1 year already) has been anything close to smooth, adding another (very noticeable) change without checking all the details and with clear instructions on how to make the recommended authoring tool actually replicate those colors does not sound like a good idea.
The ExtraFPS build, is a bit faster, but quite a disappointment to see how it handles colors with that default tonemapper as of today.
Dan Linden
under review