V-Ray default Color Mapping settings ensure a 1:1 mapping of all the user operations and the final result. You could also post a wish to add a color multiply control in the color correct node. Color mapping (sometimes also called tone mapping) dictates which color operations are performed between the user interface inputs and the values rendered and the way the rendered pixels are displayed through the VFB on the user monitor. That would probably be the easiest way to colorize a black and white image. So I'd take the color correction map, but it in a composite map, make a new map that's set to red ontop, and set that layer to multiply. What you really want to do is multiply your image with red. Because the saturation is a multiply, a saturated of 0 multiplied by anything produces 0. The warning went away and it has yet to pop up when I opened the file from a fresh restart. In max 2014, you have a greyscale color, then you turn up the saturation. I uninstalled the color correction plug-in after installing it off of the website that Tommy posted. Because the saturation is an add, it's adding hue color red to the image, causing it to turn red. In max 2013, you have a greyscale color, then you turn up the saturation. First, you don't even need to use the tint, you can reproduce the issue entirely with saturation. So what's happening in your case is this. Well, looks like max 2014 is now doing a multiply. ![]() ![]() I was never 100% sure on the math, but it always looked to me that the Saturation in max 2013 and before was doing an add/subtract, which led to the odd results, wheras photoshop was doing a multiply, which led to more predictable and better looking results. Here's the original bug:īasically, turning down the saturation on images produced nasty artifacts. There was a bug fixed that changed the functionality a bit.
0 Comments
Leave a Reply. |