Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2021.3.47f1
2022.3.55f1
6000.0.33f1
6000.1.0b1
6000.2.0a1
Issue ID
UUM-92138
Regression
No
Initialization order is incorrect when instantiating GameObject using PrefabUtility.InstantiatePrefab
How to reproduce:
1. Open the attached “IN-92312” project
2. Open the “SampleScene” and enter Play mode
3. Observe the position of the two cubes
Expected result: Both cubes are placed at coordinates (2, 0, 0)
Actual result: The cube created with Instantiate is placed at coordinates (2, 0, 0), whereas the cube created with PrefabUtility.InstantiatePrefab incorrectly remains at coordinates (0, 0, 0)
Reproducible in: 2021.3.0f1, 2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0b1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment