Redacted

Comments

• Richard Haseltine Posts: 96,809

  September 2012 edited December 1969

  Looks plausible - formerly drop to floor did the same, switching the scale from the master control to the axis controls but now it doesn't (and drop to floor is a script).
• ketthrove Posts: 63

  September 2012 edited December 1969

  The set value on the properties did not change, however there was a new variant of DzNode::setLocalTransform that was written that tries to maintain the value in the general scale property. DzNode::setWSTransform now calls this new variant. So depending on what you do before or after the setValue on a scale property, it may cause what you are seeing. The new variant of setLocalTransform will cause the general scale to be set to a non-one value when any two of the component scales matches values.