I'm saying don't load old scenes with resize nodes and expect the
behaviour to change, try it with a new scene, I don't think backward
compatibility requires explanation.
------------------
Luc-Eric Rousseau
Team Leader, User Interface
Softimage|XSI
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM
> [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Matt Lind
> Posted At: Friday, September 30, 2005 4:25 PM
> Posted To: xsi
> Conversation: resize node in FX tree
> Subject: RE: resize node in FX tree
>
>
> >Note that you need to try this with a scene created at least in XSI
> >4.2, because the resize node checks the scene version and
> emulates old
> >bugs in order to maintain compatibility. If you worked
> around a bug,
> >for example by adding 1 to the desired size, I must maintain that
> >behaviour in existing scenes. Cuz I'm that nice of a guy.
>
> Emulate old bugs - what kind of BS is that? Features I can
> understand, but bugs?
>
> My workflow has always been to make something however it's
> supposed to function so that when a bug is fixed it will
> automatically 'work' as expected from that point on. The
> time between a bug's discovery and it's resolution is almost
> always shorter than the time from when the bug is fixed to
> the remainder of time the content uses the tool - including
> archive after completion. So what you're telling me here is
> I'll be forever penalized for thinking and planning ahead
> because XSI outdumbed itself? If XSI is checking scene
> version, and I load an old scene, then how do I eliminate the
> legacy checking to make it work properly without having to
> rebuild all the nodes?
>
> A little golf analogy may be appropriate here: The hallmark
> of a well designed course is it only penalizes bad shots/players.
>
>
> Matt
>
> ------------------------------
> Matt Lind
> Animator / Technical Director
> SOFTIMAGE certified instructor:
> SOFTIMAGE|3D
> SOFTIMAGE|XSI
> Mantom, Chicago
> Matt(at)Mantom.net
>
>
>
> RE: resize node in FX tree
> Date : Fri, 30 Sep 2005 15:54:51 -0400
> To : <XSI(at)Softimage.COM>
> From : "Luc-Eric Rousseau" <lucer(at)Softimage.COM>
> Subject : RE: resize node in FX tree
>
> Things should always work the way users expect, but sometimes
> implementation
> gets in the way.
>
> The output side of the operator is calculated by the
> algorithm, it is the
> true size that the effect will produce given its input
> parameters. The
> Resize node is just a different UI on the transform 3D, so
> when you put an
> exact pixel value what it does is in fact figure out the
> right numbers to
> poke in a transform matrix to produce the output. The image
> size produced
> is the result of that matrix transform, not the number you
> entered you
> entered in the PPG. It must work this way because I need to
> stamp out any
> time that the results are not correct, and not hide the bugs
> by forcing the
> output to exact pixel. Which would give an image the right
> size, but with
> some aliasing garbage or missing lines.
>
> I'd like to have clear repro steps on how to have it not work
> right, so we
> can address any remain issue.
>
> Note that you need to try this with a scene created at least
> in XSI 4.2,
> because the resize node checks the scene version and emulates
> old bugs in
> order to maintain compatibility. If you worked around a bug,
> for example by
> adding 1 to the desired size, I must maintain that behaviour
> in existing
> scenes. Cuz I'm that nice of a guy.
>
>
> ------------------
> Luc-Eric Rousseau
> Team Leader, User Interface
> Softimage|XSI
>
>
> ---
> 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
