kyraia opened this issue on Oct 02, 2007 · 95 posts
bagginsbill posted Fri, 05 October 2007 at 10:30 AM
Quote - I made some changes in the Calibrate_BLACK node and set the second value_2 to 1,0000 also, this remove the tint from the background complete and it don't make the background image darker no more.
Cath,
That node is a Math_Functions:Add node. Because you placed a 1 in Value_2, it adds them and produces 2. While you can get away with that on that node, it isn't what I intended for you to do. Just put a 2 in Value_1, or a 2.5, or 3, or 4. The purpose of that node is to detect where there is NOT a shadow, so that the shadow catcher effect is 0 (BLACK). That's why you tune upward until you get black in calibration mode.
The Calibrate_WHITE node is also a Math_Functions:Add node. BUT BE CAREFUL! There is something plugged into Value_1 - I need you to edit Value_1 always, not Value_2. If you edit Calibrate_WHITE Value_2, it will not include the plugged in value and the results will be wrong. The purpose of this node is so you can tune upward to determine where the maximum tinting should occur. I want to see 1 (WHITE) where you want the maximum shadow catcher effect.
These two calibration nodes are very important. Any time you change your lights, do a calibration render again to make sure you're getting black and white. If you don't get black for the un-shadows regions, it accidentally tints the whole picture, just as you discovered.
If Poser had a Simple_Number node (something like the Simple_Color node), then I would have used it, so there would be no confusion or possibility of mistake. But, alas, there is no such node. The closest thing is to use a Math_Functions node and just ignore Value_2 - leave it at 0. It is true that some of my parameter nodes don't care which one you change, but don't rely on that behavior. It is accidental. Always use Value_1 and pretend Value_2 isn't there.
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)