I could be off-topic there, but just thought I should share, in case anyone else has the same problem. Gamma correction compensates for the differences in color display on different output devices, so that images look the same when viewed on different monitors. I had made an original object and 22 more instances, and when I applied the material, instead of applying only to the original object, I applied it to ALL 23 object (stupid, I know). The one time I had such an issue, I found out that it was my fault. I don't know though if this has anything to do with long saving times, since this didn't happen to me. the color field 'Basic Parameters/Map:' set to 50 neutral grey (RGB 127/127/127 or 0.5/0.5/0. I loaded it, and just changed it with a simple bitmap. In 2013 and before you can tint pure grey (scale) maps/base colors (like my greyscale concrete.jpg), in 2014 you can only tint tinted maps/base colors the hue tint works like the hue shift. Somewhere in there I found the map causing all the problem (I believe it says 'ColorCorrect' inside brackets so that you can find it). Final Cut Pro or Apple FCP - A Video Editing Software Cutting and pasting of audio and video Color correction Selection of scenes from multiple takes Adding. Otherwise there may be a confusion, as the apparent tuning of materials will be produced in gamma 1. So (if I remember correctly, since it's been a while since I did it), I just created a new Vray Material, opened the diffuse map slot and browsed to the scene materials (which now contains all the scene maps). Since the renderer operates in a unusual gamma we got to set 3ds Max display mode to gamma 2.2 for 'Material Editor' and 'Color Selector' colors to become correct. And although I deleted the object, the map remained in my scene. The ColorCorrect plugin was applied to one of the maps in my scene. Actually I did manage to remove the warning.
0 Comments
Leave a Reply. |