Yes, that is, unfortunately, a typical behavior of XSI. I once wrote a
script that would scan the Filemon log and sort the directories by
number of operations..... the root shared network directory
(\\linuxserver\animation) had been hit over 4,000x while opening a
scene..... and that was just that directory, for a total of
29,000-30,000 hits on the server file system. Ugh!
Note, however, that many software widgets do a similar thing.
For instance, if you set the Filemon filter to firefox.exe, go in
firefox and run File > Open File..., start browsing the file system,
you should see similar things happening. I suspect that software that
behave this way use a standard Windows library that checks directory
attributes (like permissions) for every single directory along the way
to a file. Oh well, just speculating here.
There are you few things you can do to help.
*Cleaning your project list was a good one. I usually put into
workgroups an event that sets the project addition preference to
"never add new projects".
*Keeping everything outside projects, except scenes, is also a
solution that I use. The problem is that when you do that, you break
away from relative paths, and thus the project cannot be easily moved.
I think this solution works better for "industrial" types of
production (like tv series, animation film, where there are tons of
shots).
*In the same spirit, I usually keep only "Scenes" and "system" in the
XSI project.
*At Big Bang there was a point where the problem went really bad (30
minutes wait). I don't remember how he came up with that, but a
colleague found out that the network shared directory was considered a
XSI project by XSI, and the only solution was to put a "system"
directory with a dsprojectinfo file in it. This, however, had the
effect that we could no longer create XSI projects directly on the
server. I had to create a project locally and copy that project on the
server to create new project.
Cheers
Bernard
On Wed, Apr 2, 2008 at 9:39 AM, Martin Winkler
<martin.winkler(at)playhead.de> wrote:
> Wednesday, April 2, 2008, 3:20:40 PM, you wrote:
>
> > It's no garanty it will help you find the problem, but it might give you a hint.
>
> Thanks Bernard, I tried that thing (which is a quite handy tool for
> other situations, too, it seems).. in fact, whenever the file
> dialogue is invoked, xsi seems to scan each and every directory from
> the root-pointer of the last file-operation on, according to that
> tool.
>
> ie. when I am within my project structure in \composites and click
> [...] for example in an file-io-node of fxtree, he still
> scans the whole \render_pictures etc which may contain hundrets of
> thousands of files in subfolders..
>
> If the last file operation was at the root of the whole drive for
> some reason, he tries and scan the whole damn thing, before actually
> opening the window.
>
> This of course explains why it might take minutes unter certain
> circumstances...
>
> Yet i have to figure out why it does all that..
>
>
>
> --
>
>
> Martin G. Winkler mailto:martin.winkler(at)playhead.de
>
>
>
> ---
> 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
