![]() |
fusionworks zdepth clipped - Printable Version +- Sitni Sati Forums (https://forum.afterworks.com) +-- Forum: Products (https://forum.afterworks.com/forumdisplay.php?fid=4) +--- Forum: FumeFX [max] (https://forum.afterworks.com/forumdisplay.php?fid=8) +--- Thread: fusionworks zdepth clipped (/showthread.php?tid=822) |
fusionworks zdepth clipped - Capitanred - 05-19-2009 maybe it's my settings, but when I do not specify the right distance range, the image is clipped between 0 and 1. if it's not my settings, it'd be nice to get this in the next version ![]() Re: fusionworks zdepth clipped - sitnisati - 05-27-2009 Hello, hmm.. colors go from 0 to 255 and you have to specify correct range so that the whole distancen (can go from 0 to millions) can be 'compressed' in that tiny range. Is this what you were thinking about ? Kresimir Re: fusionworks zdepth clipped - Capitanred - 05-27-2009 not quite. usually I specify a range in units away from the camera, which will be the displayed area on my monitor. so value 0([0,0,0]) furthest to 1([255,255,255]) nearest. but if there is something which is outside this range, then it's value should just go below 0.0 or over 1.0 this way I can in comp shift the display range. right now it just clamps the values to 0 and 1. everything outside is either invisible or full white and flat. I think if I would specify it now to 0 to 1'000'000'000 I would be able to do what I had in mind. but i don't know if the float precision is enough to give me a range if my objects are in a space of 0-100 for example. Re: fusionworks zdepth clipped - Jordan - 05-28-2009 So how do you suppose a value over 255 is to be stored in an 8 bit image? I think this is the problem yes? Fume wont save to a 16bit or 32bit float image properly (I believe, let me know if im wrong!!!!!!)? Still either way you should just specify your z-Depth range you want to use in comp by the distance you set in max. Any thing over or under will be flat white or black. Re: fusionworks zdepth clipped - Capitanred - 05-28-2009 well...saving to exr usually does the float thing. it just doesn't do it in the zdepth. as I said in the begining, maybe I missed a checkbox. but there are fume renders which have vlaues over 1 and below 0.(16bit or 32bit) Re: fusionworks zdepth clipped - sitnisati - 05-31-2009 z depth does not go in exr (only colors does) - it goes in 0-255 range regardless of the image format. Kresimir Re: fusionworks zdepth clipped - p Hagar - 03-19-2012 I have this problem too with Fusionworks z depth. Is it a bug? My ranges are correct but the results look clipped. See attachment please. Any help would be appreciated. Thanks, Patrick |