Tweet
Apologies for what may be a repeat thread but I cant seem to find anything that is current so to speak. I've started working in a new studio and this is my first time using next with max 2018. Previously I was using 3.6 something and Max 2017.
I'm having an issue where the image in the frame buffer doesn't match the file output or even the material previews in the material editor. If you change colour mapping mode to 'colour mapping and gamma' then materials in the frame buffer match the previews from the material editor relatively speaking when you consider the effects if lighting etc. If you save this image from the frame buffer obviously its blown out because the gamma has been baked into the render and then also applied again when the image has been output. At least that's my understanding of what is going on.
Without changing colour mapping mode to the above setting the image in the frame bugger seems very dark and the shaders seem to be 'burnt'. The image outputs as I would expect it to look though. In my previous experience there has always been a difference in the frame buffer and output image but I'm sure it was never this drastic.
I don't think its a bug and likely I've forgotten something in the settings so if anyone has some ideas that would be helpful There's a screen grab from a test render attached to illustrate.
Thanks
I'm having an issue where the image in the frame buffer doesn't match the file output or even the material previews in the material editor. If you change colour mapping mode to 'colour mapping and gamma' then materials in the frame buffer match the previews from the material editor relatively speaking when you consider the effects if lighting etc. If you save this image from the frame buffer obviously its blown out because the gamma has been baked into the render and then also applied again when the image has been output. At least that's my understanding of what is going on.
Without changing colour mapping mode to the above setting the image in the frame bugger seems very dark and the shaders seem to be 'burnt'. The image outputs as I would expect it to look though. In my previous experience there has always been a difference in the frame buffer and output image but I'm sure it was never this drastic.
I don't think its a bug and likely I've forgotten something in the settings so if anyone has some ideas that would be helpful There's a screen grab from a test render attached to illustrate.
Thanks
Comment