Error when using toWorldVec when scale is 0

[Dan Ebberts]

Possibly, depending on what you want to happen. You could encase the toWorldVec() in a try/catch clause, but then you have to decide what you want the result to be in that case:

try{
  thisComp.layer(2).toWorldVec([1,0,0])
}catch(e){
  [1,0,0]
}

Or maybe you could have an invisible layer that isn’t scaled parented to the layer that is scaled and get the x vector from the one that isn’t scaled. It depends on what your situation is.

[Simon Bjork]

Thanks for the reply Dan.

Yes, that would work. But as the toWorlVec is both rotation and scale, I guess rotation is lost as well in that case?

I’m exporting objects to other applications and therefore I need to extract the world matrix of objects.

[Dan Ebberts]

I’m guessing the math behind toWorldVec just doesn’t work if scale is zero. So at that point maybe rotation has no meaning? I’m not sure.

[Simon Bjork]

Yes, I think so too. It would have been nice if it internally changed 0 to 0.0001 or something. I guess the only way around this is to build the matrices from scratch manually.

Or just alert the user if the scale is 0.