 | | | Particle cache and XSIBatchserver | Particle cache and XSIBatchserver 2005-06-23 - By Guillaume Laforge
Back
>Have you had any success with "load from file"?
It's an XSI mystery for me too... I would love to know what is the purpose
of this "Particle from file" ?
Guillaume
2005/6/23, kim aldis <kim@(protected)>:
>
> Not really looked closely at it. Sorry.
>
> > -- --Original Message-- --
> > From: owner-xsi@(protected)
> > [mailto:owner-xsi@(protected)] On Behalf Of Eric Lampi
> > Sent: 23 June 2005 17:19
> > To: XSI@(protected)
> > Subject: RE: Particle cache and XSIBatchserver
> >
> > Kim,
> >
> > Have you had any success with "load from file"?
> >
> > I've tried to use it, but I never quite understood how to get
> > the material attributes to work properly.
> >
> > It just plays back the particle points with seemingly no way
> > to get at it's Ptype material settings. Am I just missing something?
> >
> > E
> >
> > --- kim aldis <kim@(protected)> wrote:
> >
> > > they're kind of odd, caches. I always found they'd rebuild cache at
> > > rendertime regardless of the state and if I write protected
> > the files
> > > it'd just fall over. I had bloody awful problems when I was messing
> > > with this but I've a feeling it was something I was doing that was
> > > messing the cache rebuild. Using scripted events or doing
> > something in
> > > the scripted events.
> > >
> > > Doing something recently and rendering not using batchserve and not
> > > using scripted events, I had problems with the cache
> > sometimes, for no
> > > apparent reason, deciding it needed rebuilding. If that
> > happens then
> > > wrong results will happen. Mostly, I think, because you've got
> > > multiple machines all fighting for the same files.
> > Corruption occurs,
> > > no doubt about it. I found myself doing a lot of
> > re-rendering on odd
> > > passes, even when I'd vedry carefully precached and tested
> > everything.
> > >
> > > There's two ways to go:
> > >
> > > *
> > >
> > > let all the machines see the same cache that's
> > built prior to
> > > rendertime. Like I said above, there could - and probably will - be
> > > problems.
> > > *
> > >
> > > Alternatively set the cache path to something like c:\temp\foo.
> > > C:/temp needs to exist on all the slaves. This way you'll have the
> > > cache recalculated on all the slaves at rendertime but they will be
> > > correct. In terms of the time it takes to render the
> > frames the cache
> > > calculation time isn't often that great. Probably safest to
> > clean the
> > > cache out before re-rendering, just in case.
> > >
> > > The other thing you need to be aware of is that it's
> > possible to have
> > > particle caches named the same in any given scene and that
> > it's highly
> > > likely there'll be identical caches across scenes in the
> > same project.
> > > They fixed the thing - I think - where all particle cache
> > files on all
> > > particle clouds were created with identical names in a
> > scene but now
> > > they get named with sequential names; particle1, particle2, etc.
> > > Manging particle cache
> > > filenames can rapidly turn ugly fast.
> > >
> > > Pretty much most of this applies to hair caching too.
> > >
> > >
> > > __ __
> > >
> > > From: owner-xsi@(protected)
> > > [mailto:owner-xsi@(protected)] On Behalf Of Marc-Andre Carbonneau
> > > Sent: 23 June 2005 12:56
> > > To: XSI@(protected)
> > > Subject: RE: Particle cache and XSIBatchserver
> > >
> > >
> > >
> > > Once cached, make you ptp files read-only
> > >
> > > I believe it works that way. Otherwise, you'll need to render
> > > everything on one machine or several machines with
> > different segment
> > > of your timeline.(use a cloud seed so they are all the same)
> > >
> > >
> > >
> > >
> > >
> > >
> > > __ __
> > >
> > >
> > > From: owner-xsi@(protected)
> > > [mailto:owner-xsi@(protected)] On Behalf Of kim aldis
> > > Sent: Thursday, June 23, 2005 5:51 AM
> > > To: XSI@(protected)
> > > Subject: RE: Particle cache and XSIBatchserver
> > >
> > >
> > >
> > > As far as I'm aware there's no reason why it shouldn't
> > work. Can you
> > > be sure that the path to the cache files is valid on all
> > your slaves?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > __ __
> > >
> > >
> > > From: owner-xsi@(protected)
> > > [mailto:owner-xsi@(protected)] On Behalf Of guillaume laforge
> > > Sent: 23 June 2005 10:42
> > > To: XSI@(protected)
> > > Subject: Particle cache and XSIBatchserver
> > >
> > > Hi list,
> > >
> > > I've seen this topic several times on the list but this time we got
> > > the pb in the studio I work actually.
> > >
> > > We can't render particules simulation with standard caching. Only
> > > standard no caching works with batchserve.
> > > I'm not a particle specialist and I don't understand why ?
> > >
> > > Is it a limitation ?
> > >
> > > Cheers,
> > >
> > > Guillaume Laforge
> > >
> > >
> >
> >
> > Freelance 3-D Animator, F/X Artist, Particle Man
> > ---
> > Unsubscribe? Mail Majordomo@(protected) with the following
> > text in body:
> > unsubscribe xsi
> >
> >
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following text in body:
> unsubscribe xsi
>
<div>>Have you had any success with "load from file"?</div>
<div> </div>
<div>It's an XSI mystery for me too... I would love to know what is the purpose
of this "Particle from file" ?</div>
<div> </div>
<div>Guillaume<br> </div><br><br>
<div><span class="gmail_quote">2005/6/23, kim aldis <<a href="mailto:kim
@(protected)">kim@(protected)</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0
.8ex; BORDER-LEFT: #ccc 1px solid">Not really looked closely at it. Sorry.<br>
<br>> -- --Original Message-- --<br>> From: <a href="mailto:owner-xsi
@(protected)">
owner-xsi@(protected)</a><br>> [mailto:<a href="mailto:owner-xsi@(protected)
.COM">owner-xsi@(protected)</a>] On Behalf Of Eric Lampi<br>> Sent: 23 June
2005 17:19<br>> To: <a href="mailto:XSI@(protected)">XSI@(protected)
</a><br>> Subject: RE: Particle cache and XSIBatchserver<br>><br>> Kim
,<br>><br>> Have you had any success with "load from file"?<br>
><br>> I've tried to use it, but I never quite understood how to get
<br>> the material attributes to work properly.<br>><br>> It just
plays back the particle points with seemingly no way<br>> to get at it's
Ptype material settings. Am I just missing something?<br>><br>>
; E
<br>><br>> --- kim aldis <<a href="mailto:kim@(protected)">kim@(protected)
.org.uk</a>> wrote:<br>><br>> > they're kind of odd, caches. I
always found they'd rebuild cache at<br>> > rendertime regardless of the
state and if I write protected
<br>> the files<br>> > it'd just fall over. I had bloody awful
problems when I was messing<br>> > with this but I've a feeling it was
something I was doing that was<br>> > messing the cache rebuild. Using
scripted events or doing
<br>> something in<br>> > the scripted events.<br>> ><br>>
> Doing something recently and rendering not using batchserve and not<br>>
> using scripted events, I had problems with the cache<br>> sometimes,
for no
<br>> > apparent reason, deciding it needed rebuilding. If that<br>>
happens then<br>> > wrong results will happen. Mostly, I think, because
you've got<br>> > multiple machines all fighting for the same files.
<br>> Corruption occurs,<br>> > no doubt about it. I found myself
doing a lot of<br>> re-rendering on odd<br>> > passes, even when I'd
vedry carefully precached and tested<br>> everything.<br>> >
<br>> > There's two ways to go:<br>> ><br>> > *<br>> >
<br>> > let all the
machines see the same cache that's<br>> built prior to<br>> >
rendertime. Like I said above, there could - and probably will - be
<br>> > problems.<br>> > *<br>> ><br>> >
Alternatively set the cache path to something like c:\temp\foo.<br>
> > C:/temp needs to exist on all the slaves. This way you'll have the<br>
> > cache recalculated on all the slaves at rendertime but they will be
<br>> > correct. In terms of the time it takes to render the
<br>> frames the cache<br>> > calculation time isn't often that great.
Probably safest to<br>> clean the<br>> > cache out before re-rendering
, just in case.
<br>> ><br>> > The other thing you need to be aware of is that it's
<br>> possible to have<br>> > particle caches named the same in any
given scene and that<br>> it's highly<br>> > likely there'll be
identical caches across scenes in the
<br>> same project.<br>> > They fixed the thing - I think - where all
particle cache<br>> files on all<br>> > particle clouds were created
with identical names in a<br>> scene but now<br>> > they get named
with sequential names; particle1, particle2, etc.
<br>> > Manging particle cache<br>> > filenames can rapidly turn
ugly fast.<br>> ><br>> > Pretty much most of this applies to hair
caching too.<br>> ><br>> ><br>> > __ __<br>>
>
<br>> > From: <a href="mailto:owner-xsi@(protected)">owner-xsi
@(protected)</a><br>> > [mailto:<a href="mailto:owner-xsi@(protected)"
>owner-xsi@(protected)</a>] On Behalf Of Marc-Andre Carbonneau<br>> >
Sent: 23 June 2005 12:56
<br>> > To: <a href="mailto:XSI@(protected)">XSI@(protected)</a><br>
> > Subject: RE: Particle cache and XSIBatchserver<br>> ><br>>
><br>> ><br>> > Once cached, make you ptp files read-only
<br>> ><br>> > I believe it works that way. Otherwise, you'll need
to render<br>> > everything on one machine or several machines with<br>
> different segment<br>> > of your timeline.(use a cloud seed so they
are all the same)
<br>> ><br>> ><br>> ><br>> ><br>> ><br>> >
<br>> > __ __<br>> ><br>> ><br>> > From: <a
href="mailto:owner-xsi@(protected)">owner-xsi@(protected)</a><br>> >
[mailto:
<a href="mailto:owner-xsi@(protected)">owner-xsi@(protected)</a>] On Behalf
Of kim aldis<br>> > Sent: Thursday, June 23, 2005 5:51 AM<br>> > To
: <a href="mailto:XSI@(protected)">XSI@(protected)</a><br>
> > Subject: RE: Particle cache and XSIBatchserver<br>> ><br>>
><br>> ><br>> > As far as I'm aware there's no reason why it
shouldn't<br>> work. Can you<br>> > be sure that the path to the cache
files is valid on all
<br>> your slaves?<br>> ><br>> ><br>> ><br>> ><br>
> ><br>> ><br>> ><br>> ><br>> > __ __
<br>> ><br>> ><br>> > From: <a href="mailto:owner-xsi
@(protected)">
owner-xsi@(protected)</a><br>> > [mailto:<a href="mailto:owner-xsi
@(protected)">owner-xsi@(protected)</a>] On Behalf Of guillaume laforge<br>
> > Sent: 23 June 2005 10:42<br>> > To: <a href="mailto:XSI
@(protected)">
XSI@(protected)</a><br>> > Subject: Particle cache and XSIBatchserver
<br>> ><br>> > Hi list,<br>> ><br>> > I've seen this
topic several times on the list but this time we got<br>> > the pb in the
studio I work actually.
<br>> ><br>> > We can't render particules simulation with standard
caching. Only<br>> > standard no caching works with batchserve.<br>>
> I'm not a particle specialist and I don't understand why ?<br>
> ><br>> > Is it a limitation ?<br>> ><br>> > Cheers,
<br>> ><br>> > Guillaume Laforge<br>> ><br>> ><br>>
<br>><br>> Freelance 3-D Animator, F/X Artist, Particle Man<br>
> ---<br>> Unsubscribe? Mail <a href="mailto:Majordomo@(protected)"
>Majordomo@(protected)</a> with the following<br>> text in body:<br>>
unsubscribe xsi<br>><br>><br><br>---<br>Unsubscribe? Mail <a href="mailto
:Majordomo@(protected)">
Majordomo@(protected)</a> with the following text in body:<br>unsubscribe xsi
<br></blockquote></div><br>
|
|
|