[Bf-python] Possible bug with transformations
Tron Thomas
tron.thomas at verizon.net
Thu Dec 29 17:31:52 CET 2005
Yeah, I'm not sure that I made it clear in my original post what I was
trying to accomplish, so it is not surprising there might have been some
confusion. I suspect this resize behavior for the vector is different
from what was in version 2.37, because my script was working fine in
that version, and now I'm having to make changes. At least now I have
an idea as to why things are not working as expected.
>Date: Wed, 28 Dec 2005 09:23:41 -0800
>From: Ken Hughes <khughes at pacific.edu>
>Subject: Re: [Bf-python] Possible bug with transformations
>To: Blender Foundation Python list <bf-python at projects.blender.org>
>Message-ID: <43B2CA1D.9050601 at pacific.edu>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Sorry, totally misunderstood what you were getting at.
>
>When you do position.resize4D(), the new fourth component is zero, so
>when you multiply with the transform matrix the translation is not
>applied. I verified by setting position[3]=1 befor the multiplication.
>
>Something similar was added to the bug tracker on the 25th related to
>resizing matrices (bug #3661), but I'm not sure if this is a bug. I
>don't think you would always want the new vector element to be set to 1.
>
>Ken
>
>
More information about the Bf-python
mailing list