Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.2
2022.1
2022.1.0a15
Issue ID
1380932
Regression
No
Position values are not loaded from Transform Default Preset
How to reproduce:
1. Create a new Unity project
2. Select Main Camera Game Object
3. Change every Transform value
4. Save Transform values to a Preset
5. Select created Preset
6. Add to Preset Default
7. Create a new empty Game Object
8. Select it and observe Transform
Expected result: Transform values should be the same as in Default Preset.
Actual result: Rotation and Scale values are the same as in a Default Preset. Position values are set to 0.
Reproduced with: 2022.1.0a15, 2021.2.3f1, 2020.3.23f1, 2019.4.32f1.
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
Resolution Note:
Position of newly created GameObjects in a scene are based on the current camera position and rotation in order to always appear in the middle of the scene view.