Search Issue Tracker
Fixed in 5.4.2
Votes
1
Found in
5.4.0f1
Issue ID
815816
Regression
Yes
Duplicating a GameObject twice, causes a change in the duplicated transforms Scale value.
How to reproduce:
1. Open the attached project and the only scene in it.
2. In the Hierarchy, select Banana/A/B and notice that B GameObject uses a Scale of 1,1,1.
3. Duplicate B GameObject.
4. Duplicate B(1) GameObject and observe that the second duplicated GameObject now uses a Scale value of 1.000001
Expected behavior: The Scale value should not change when duplicating a GameObject.
Actual behavior: Duplicating a GameObject twice, causes a change in the duplicated transforms Scale value.
Reproducible: 5.4.0f2, 5.5.0a4
Not reproducible: 5.3.6f1, 5.2.4f1
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
Add comment