Search Issue Tracker
By Design
Votes
3
Found in
5.4.1f1
Issue ID
834054
Regression
No
Negative scale isn't taken into account when calculating Transform.localToWorldMatrix
Resolved as by design: This is working as expected. The scale of an object doesn't affect the direction of this object, this is a choice that was made in the first release of Unity.
Steps to reproduce:
1. Open attached project "834054.zip"
2. Open scene "Negative Scale Redux"
3. Expand whole "Root 1 - WL" hierarchy
4. Select "Broken Axis" GO and notice that Y and Z axis do not match axis calculated by transform.localToWorldMatrix * Vector3.[Direction]
Note: this doesn't happen with X axis because none of the parent objects have negative X scale.
Reproduced with: 5.2.5f1, 5.3.6p6, 5.4.1p2, 5.5.0b5
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Ewanuk
Jan 19, 2017 16:33
Has there been any movement on this? This is a core part of the engine that's causing us real headaches and blocking core features.