Search Issue Tracker

Fixed in 2018.1

Fixed in 5.6, 2017.1, 2017.2, 2017.3



Found in


Issue ID




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

Scene Management


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

  1. Response avatar


    Jan 12, 2018

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

Comments (43)

  1. 471449662f4b4a1349075cc68084986b?d=mm


    Nov 20, 2017 08:34

    Same problem in 2017.2.0f3

  2. 0e34cac96faf280850d9858607c3c57e?d=mm


    Nov 14, 2017 17:47

    5.6.x really needs a fix for this. I can't imagine any project not using the value of transform.position inside Awake() in *some* scripts.

  3. F74a5d0646a3fe1aebde2c436e7a3c9c?d=mm


    Nov 09, 2017 18:41

    Not fixed in 5.6.4p2

  4. Bdb915962f1346cd36705a16a8b06c66?d=mm


    Oct 23, 2017 01:51

    I got back from 2017.x. Recent versions crashes on exit play modes.
    And have troubles in 5.6.4f1 with this critical bug.
    Should I go back to 5.5.x??

  5. 142aeb3efc075dfe82adfdd9baaa8bb9?d=mm


    Oct 21, 2017 11:57

    I'm having this issue in Unity 2017.2.0f3 as well. Awake is defiantly called at the prefab's original position and not the supplied instantiate position. Prewarmed particles also briefly appear at the original prefab position.

  6. F74a5d0646a3fe1aebde2c436e7a3c9c?d=mm


    Oct 20, 2017 21:14

    So no fix for Unity 5.6 ?

  7. F74a5d0646a3fe1aebde2c436e7a3c9c?d=mm


    Oct 16, 2017 21:35

    This is not fixed in 5.6.4f1.

  8. 0927b87e0d6cf58e6a225245a3d45bcc?d=mm


    Oct 13, 2017 17:05

    It happened in 2017.1.p1 and in future patches too, while it was totally fine still in 2017.1.f1.

  9. F7dd45640ced2bc8b5c72357650d18fd?d=mm


    Oct 13, 2017 12:17

    Still same problem i 2017.2.0f3 . Can somebody please look into this?
    Why is this bug set to FIXED when its clearly not.

  10. 584d5bd0fc4b47548ca13a1e5594ec1b?d=mm


    Sep 26, 2017 02:16

    This issue produce critical bug. Our company's project were stuck.

Add comment

Log in to post comment

All about bugs

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