HEEEEELP!!! 2004-02-27 - By Eric Lampi
Back
Thanks for the suggestion, but you really need to look
at the file and see what I am talking about.
This was just a test scene I made to try and
troubleshoot the MB on what I am currently working on.
I have tried that and everything else I can think of
including but not limited to- New ptp name, new ptp
location, offset p-cloud start frame, different rate
value, numerous different MB setting, different rate
distributions methods - gaussian and unimform and
various seed values, sub-emission values, offset
p-cloud duration and time reference, various versions
of XSI, different machines... I have change every
seed value I can find.
It doesn't happen in standard no-cache mode, but
that's pretty useless when you have numerous passes
and 2k files to render on a renderfarm.
Looks like it'll be 2-D MB for me.
(deep breath) *SIGH*
On a personal note, I am really getting tired of
fighting with the p-system every time I use it. There
are so many screwed up aspects to it that I generally
spend 2 days for every one day in production trying to
fix and work around the most basic things.
Motion blur does not work. P-types you have to spend
considerable effort with expressions and custom
parameters to even come close (and it's only close) to
being able to matte and occlude p-types. With
anything else, you can set up an element pass in
seconds, just dragging and dropping objects and
materials - it's a joy, especially for those of use
who used to do it the old Soft 3-D way.
I am really pretty angry right now, and I am wondering
many more versions are going to pass before these
things are fixed. I called support and there's no bug
logged about this problem, which I was surprised to
hear since I have always seen it.
It's great to see new features, and there are people
who are working hard to make XSI better, I know, I
appreciate it. Support has tried to help me, but
their solutions just didn't work out. Bottom line is
what good are new features when you can't even render
the with MB and p-type passes and partitions like
anything else in XSI.
I'm going to leave now and throw myself out a window.
Have a great weekend everyone!
Eric
--- Simon Pickard <mail@(protected)> wrote:
> Go into you simulate folder for this project and
> delete any cache files in
> there and try re rendering. Might be ones got messed
> up for some reason.
>
> Regards,
>
> Simon
>
>
>
> "Take a look at this file. Particle's MB look like
> it's really f-ed up.
>
> It's set to frame 69, quick preview has defaul MB
> turned on. Nothing fancy. You can see the
> wireframe
> that the particle's vectors raditate out from the
> emitter
>
> Now do a quick preview, the MB is wrong on this
> frame.
> Click on the window to close the render region, now
> if
> you see what I have been seeing, the particle's
> vectors on the wireframe switch!
>
> Advance one frame forward or backward, and they look
> and render as expected. Go back to 69 and it's
> screwy. Turn off MB in the preview options, render
> egion again, and there's no change in the vectors,
> it's just that frame!!
>
> By the way, this happens in 3.51, and in beta 3.
>
> I NEED a way to work around this!!!!
>
> Thanks,
>
> Eric Lampi"
>
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the
> following text in body:
> unsubscribe xsi
=====
Freelance 3-D Animator, F/X Artist
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
