Initialization order is incorrect when instantiating GameObject using PrefabUtility.InstantiatePrefab

Unity: Scene Management

Won't Fix

6.5.X

6.4.X

6.3.X

6.2.X

6.1.X

6.0.X

2022.3.X

2021.3.X

Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

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

Initialization order is incorrect when instantiating GameObject using PrefabUtility.InstantiatePrefab

Unity: Scene Management

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Initialization order is incorrect when instantiating GameObject using PrefabUtility.InstantiatePrefab

Unity: Scene Management

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?