QUOTE(dickagm @ 06/11/07, 04:20 PM) [snapback]267911[/snapback]
and then I'm saveing it as TGA converting z channel to Black and White luminance.
Argh! Fchek is made for viewing the data. However the data is not back and white! Its a floating point value of -1/dsitance, because you need to see it somehow its been linearized to 8 bit texture space. However if you go ahead and use thet in a comp application your going to be shooting yourself in the leg.
See fchhek does something called normalization, so the furtest frame in the image gets darkest value and the closest white. However for a post effect you dont want that, you want the data intact (unfortunately after effects for example cant read in the z depth data its just totaly blind to floating data like this, in fact AE is blind to raw data period. So i suggest for your peace of mind to either use digital fusion or shake because they have access to the raw data).*
Why? Well the max min range varies form frame to frame, and so will your black and white imagery. This has led to the very common misconception that the depth is variant it isnt just normalized depth is variant. So you will end p having a mess of it all when you comp. Offcourse you may luck out in having stable range. but don't count on it.
So either pull out the data at some custom range, or use the real data in comp.
Ps maya can open it, but only for certain operations ist still no use as textre but is of use for image planes and rendering.
*to Aron Ross this is the kind of stuff you get when you do purely artist friendly, sometimes the raw is the way to go and not enabling can be more of a hinder than anything else. Which brings in a valid point i heard today. Ease of use is in contradiction t effect of use. So when you optimize ease of use you alienate the hardcore users so in way you'd need to have 2 guis one easy to learn and one hard. Off course can you imagine the pain switching over.