bagginsbill opened this issue on Feb 01, 2009 · 207 posts
bagginsbill posted Fri, 17 April 2009 at 10:21 AM
Oh boy. So you decide to bring up the complicated scenario, heheh.
Monitors are supposed to be set so that they display sRGB content directly, which is approximately a gamma of 2.2.
Any material that is constructed while staring at the results on such a monitor (such as hand-drawing a texture color map) is encoded with the gamma level of the monitor at the time of construction. I don't mean the data is impacted in some way, I mean that the human making color choices was impacted by the gamma of her monitor. So you need to respect the monitor response curve that the author was using, not you, when dealing with her material as incoming material that requires anti-GC.
Now if you want to design an output for your extra bright gamma 1.5 monitor, then you want your outgoing GC = 1.5, but you STILL need your incoming anti-GC to be 2.2, unless the incoming material was designed while LOOKING AT YOUR MONITOR. If you judged a color combination nice on your monitor, you must assume that the linear value is anti-GC(1.5). If the incoming material was judged nice on somebody else's workstation, then you must assume they were using 2.2.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)