So whats the problem? I’m using LWF and in my max gamma settings my input is set to 2.2 and I dont have any problems. I use more bitmaps than procedurals so it makes more sense to just leave the input at 2.2. If you dont want to do that, and you also dont want to specify it each time, then how else do you think you would specify it?
It is not recommended for LWF? well that depends on who you speak to. I DO recommend setting it to 2.2
Your link for example say to leave it at 1.0, but then everytime you load a bitmap, you have to specify 2.2 which is an extra step. You said you don’t want this extra step and you also dont want to set it to 2.2 in max input settings? So then what you want? Those are your 2 options. Setting input to 2.2 saves you an extra step everytime you load a bitmap. Unless you using a linear EXR or HDRI for input. I’m sure you input WAAAAY more jpg and png than exr and hdri, so then why make extra work for yourself? You have to specify 2.2 somewhere, might as well put it in input and forget about it.
For exr and hdri you set it to override 1.0 (unless you left your input at 1, in which case there is no need to override)
If however you set input to 2.2, then you don’t need to override for most bitmaps when loading the map, unless you load exr or hdri in which case then you will override to 1
(normal jpgs etc is usualy needs 2.2 - linear things needs 1)
“Ideally, gamma (or sRGB) correction should be done only on File textures used as colors, and not on colors in procedural textures, results from procedural textures, bitmap textures used for bump and displacement etc. This is the correct workflow.”