Zpics
have their advantages. They are floating point and
contain the exact distance to the camera of the each pixel in softimage
units,
there is no data loss and it’s consistent between frames. Since they
are a
dump of the Zbuffer, they are not anti-aliased, but that’s what you
need for
Z-compositing. Or at least, that’s the best you can do – z-compositing
is never
great.
Hi Alan,
Thanks for your suggestion we will try out.
Leoung
Alan Fregtman wrote:
Does it have to be zpic? I've had good luck saving the depth
renderchannel/framebuffer of a render as a 16bit *.SGI. Works great.
As for RPF, it apparently needs to be implemented by mental images and
they don't feel like doing so, according to this post:
http://www.highend3d.com/boards/lofiversion/index.php/t161451.html
Cheers,
-- Alan
On Thu, Feb 28, 2008 at 7:58 PM, digimata <digimata(at)digimata.com> wrote:
This is our first venture in using zpic from XSI and sending to our
Aftereffect's guy.
We are using XSI 6.01 and he is using Aftereffect 7.0
We gave him a pic file and a zpic file to test.
XSI rendered out a "test.pic" and a "test.zt"
It didn't work in Aftereffect until we change the zpic file's extention
to .zpic
The next problem we have is the zpic data is inverted.
Anyone else run into this problem or we doing something incorrect here.
The Aftereffect guy enquired why SXI/MR. doesn't generate RPF (Rich
Pixel Format) files
like many other 3D packages.
Thanks,
Leoung
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi