Search Issue Tracker
Fixed in 5.3.5
Votes
16
Found in
5.4.0b7
Issue ID
774484
Regression
Yes
After importing model with "Optimize Game Object" enabled leads to incorrect GameObject scaling
To reproduce follow the steps:
1. Open "Bug_Report" project
2. Open "Scale_Error" scene
3. Observe the scene - one of two objects are scaled incorrectly
4. Incorrect scaled GameObject model import settings has model has "optimize gameobject" checked.
5. After disabling "optimize GameObject" does not affect GameObject unless it's added into the scene after the changes
Reproduced in 5.4.0b7, 5.4.0b8, 5.3.3p2, 5.3.2f1
Not reproducible: 5.2.4
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
Arainami
Mar 18, 2016 09:38
The same problem. In versions 5.3 and 5.4 beta, our game turns into a mess because of the option Optimize Game Objects