Search Issue Tracker

Fixed in Unity 2018.1



Found in


Issue ID




Game object transform.position is incorrect after Object.Instantiate after Awake() function call

Scene Management



Priority: 2Necessary for shipping a final release


Severity: 3Secondary functionality broken

How to reproduce:
1. Download attached project files and open "test" Scene
2. Enter Play mode. Notice now the world-space location in Awake is printing the prefab location as opposed to the location passed to instantiate:
Parent(Clone): World-space location: (-10.0, 20.0, 0.0)
Child: World-space location: (-10.0, 20.0, 0.0)

Not reproduced:
1. Open project with Unity 5.6.3p2 and hit "play". Notice that "World-space location" printed in SpawnLog.Awake now outputs location as expected according to SpawnPrefab-script:
Parent(Clone): World-space location: (50.0, 100.0, 0.0)
Child: World-space location: (50.0, 100.0, 0.0)

Actual result: Instantiate(Prefab, new Vector3(50, 100, 0), Quaternion.identity) applies world position incorect in Debug.Log(transform.postion) after Awake() function call

Reproduced with: 5.6.3p4, 2017.1.1p3, 2017.2.0f1, 2017.3.0b2
Not reproduced with: 5.6.3p2, 2017.1f1, 2017.2.0b8, 2017.3.0a5
Regression since: 5.6.3p3
Fixed in 2017.1.2p3, 2017.2.0p1, 2017.3.0b5

Response avatar


Jan 12, 2018

The fix for this will be available in the following patches:

Comments (41)

  1. 2090af95e7a8ee50f1c4b23d2cc71fd0?d=mm


    Sep 11, 2018 15:44

    I encountered the same issue on v2017.3.1f1

  2. 0097e1b88719b9cce9f3317a1a63899a?d=mm


    Mar 21, 2018 03:57

    not fixed Unity 2017.3.1p2

  3. 5c3c2d061656ed7182880a3ddea47c5f?d=mm


    Feb 06, 2018 11:10

    Not fixed.

  4. 5bea8535f26b570ac592f267db64f554?d=mm


    Jan 16, 2018 12:16

    Anyone can send a sample project?
    No, the error is not resolved.
    In my case, when my player shoot, the instantiated muzzle prefab is a bit down of the correct position.

  5. Dc1b254760f44d16cd4f684456bf554f?d=mm


    Jan 15, 2018 16:06

    QA have retested 2017.3.0f3 and confirmed that this bug is still fixed. If you are still having issues then do please submit a bug report with an example project so we can further investigate.

  6. Dc1b254760f44d16cd4f684456bf554f?d=mm


    Jan 13, 2018 00:00

    We are investigating the new 2017.3 reports. Thanks.

  7. B388a33b7f780c80e1d9dd1efc66d2f2?d=mm


    Jan 10, 2018 11:16

    Also getting this issue since upgrading to 2017.3

  8. 1da1dec26ade61caa2624d767bf35ddb?d=mm


    Jan 07, 2018 18:12

    "Voting disabled for resolved issues" Piss off.

    This has been broken on 5.6.4 for nearly FOUR MONTHS and it's regressed in 2017.3!!!!

    Wtf, Unity.

  9. 9bdc4a5a7a0199050356b2ae387f0fbb?d=mm


    Jan 06, 2018 19:50

    Still not fixed in 2017.3.0f3 .........

    I will downgrade ........

  10. E2034f7753b52d221306edf828d6353e?d=mm


    Jan 03, 2018 19:54

    I am also seeing this in 2017.3.0f3. The workaround in my case was to call SetPositionAndRotation on the newly instantiated object. Setting the prefab transform prior to calling Instantiate did not work for me.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.