Search Issue Tracker

Fixed in 2018.1.X

Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X

Votes

36

Found in

5.6.3p3

Issue ID

953068

Regression

Yes

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. karl_jones

    Jan 12, 2018

    The fix for this will be available in the following patches:
    5.6.5p1
    2017.1.2p3
    2017.2.0p1
    2017.3.0b5

Comments (49)

  1. shadiradio

    Dec 06, 2017 16:55

    Is this going to be fixed for 5.6.4p4? Is there a workaround for this?

  2. shadiradio

    Nov 30, 2017 05:45

    Is there any status update on this issue? I'm worried that it won't get internal visibility because it's marked as resolved. :(

  3. nas4eva

    Nov 23, 2017 09:44

    This is still not fixed in 5.6.4p3

    Please, please, please fix this!

  4. nas4eva

    Nov 23, 2017 09:44

    This is still not fixed in 5.6.3p2

    Please, please, please fix this!

  5. kuro_sk

    Nov 21, 2017 16:14

    2017.2.0f3 personal still has this problem. Why was this issue closed?

  6. Brent_The_3D_Guy

    Nov 21, 2017 12:56

    This is still not fixed in 2017.2.0f3.

    Please, please, please fix this!

  7. Filipinjo

    Nov 20, 2017 08:34

    Same problem in 2017.2.0f3

  8. shadiradio

    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.

  9. TheJimz

    Nov 09, 2017 18:41

    Not fixed in 5.6.4p2

  10. UDN_872dded5-d7f7-47fd-9f8b-194a81321fb4

    Oct 23, 2017 01:51

    I got back from 2017.x. Recent versions crashes on exit play modes.
    https://forum.unity.com/threads/unity-2017-2-0f3-crashing-on-exit-play-mode.500066/
    And have troubles in 5.6.4f1 with this critical bug.
    Should I go back to 5.5.x??

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.