Well first of all, all passes are rendered in their own folder. Here
we are talking about a folder of 229 files.
Second I absolutely don't see why it should take 4 friggin minutes to
loop over 229 files to perform whatever knows what operation. I hate
making such statement but even a FileSytemObject call is a million
times faster than that.
Something is really wrong here, I don't see any reason in the world
in such circumpstances to take such a long time to get to see the file
browser. Btw, it's not displaying the files that seem to be the
problem, it's opening the god damn file browser itself. When it is
open and I browser directories, there is no problem, it's very fast
and all is well. It's also true that the longest I wait before opening
the file browser, the longest it will take to open it the next time. I
have never encountered such lags with the Windows Explorer under
normal circumpstances, I don't see why it should be different with the
Flipbook file browser. Something really is wrong here.
And lastly, I'm a Windows user reading on a Linux file server.
Comparing the number of files in a directory and performance of a file
browser with the number of polygons and render time is like comparing
apples and oranges if you ask. They are both fruits, but with
different qualities.
On 9/1/05, kim aldis <kim(at)cg-soup.com> wrote:
> Why? It's exactly what you'd expect. Just like the number of polygons in a
> scene affects rendertime.
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
