You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The base spec and all extensions follow the same rules:
All JSON numbers, e.g., base color factor, specular color factor, clearcoat factor, thickness factor, are linear multipliers.
Non-color textures, e.g., metallic roughness texture, transmission texture, contain linear values, i.e., an 8-bit value of 0x80 means 0.502.
Color textures, e.g., base color texture, sheen color texture, specular color texture, contain sRGB-encoded values, i.e., an 8-bit value of 0x80 means 0.216.
Volume attenuation color is a bit unique because it is not texturable but the general rule still applies: JSON numbers are linear. We should clarify the extension spec.
I really wish we could use the terms "Linear", "sRGB" or "Rec. 709", and "D65" when describing these factors. I understand that we're dancing around a tricky distinction — multiplicands whose product is a Linear-Rec709-D65 color. But I don't think "linear multiplier" is giving the reader enough context to understand that. Particularly as more tools begin supporting additional linear color spaces.
While looking into a few color management problems I've come across at least one extension where the intended color space is not specified.
These readmes explicitly mention intended color space:
These don't:
The text was updated successfully, but these errors were encountered: