Strange Instantiate behaviour in 2017.1.1p2

I updated to 2017.1.1p2 yesterday and I'm seeing some weird behaviour with Instantiate. If I instantiate a prefab at a set location, when I check the location in Awake on a script attached to the prefab I get the wrong value. So:

GameObject.Instantiate(m_Prefab, new Vector3(123, 456, 789), Quaternion.identity);

Then in the prefab setup:

void Awake()
{
Debug.Log("Awake: " + transform.position);
}
void Start()
{
Debug.Log("Start: " + transform.position);
}

I get this:
Awake: (0.0, 0.0, 0.0)
Start: (123.0, 456.0, 789.0)

I have tried this in a fresh new project and it always happens. I came from 5.6.2p2 and I've checked 2017.1.0p5 and this works fine (same test project). Anyone else seeing this?

thanks

 

Happening to me too. Tested in 2017.1.1p3. Worked fine in 2017.1.0p4.

Might be related to this? https://issuetracker.unity3d.com/is...ect-dot-instantiate-after-awake-function-call

 

Just checked it with 2017.1.2f1, still happens. Any idea on when a fix will be in? We spawn objects in Awake calls using position, so this is basically a show stopper for us.

 

Great. Thanks Karl.

 

Does anybody know if this is fixed in 2017.1.2p1?

 

Thanks Karl!

I'll ask again when p2 comes out

- David L

 

It seems this is still the issue even in 2017.2, even though the previously linked bugreport is marked as resolved?
https://issuetracker.unity3d.com/is...ion-in-awake-method-of-an-instantiated-prefab

I encountered it today after upgrading from 5.6 to 2017.2... In the place I am dealing with it it is sort of solvable by delaying the functionality to the Start method, but I must say it is not elegant/does feel very wrong, and I'm not sure what other scripts might suffer from it that are used somewhere further in the game where I did not yet test.

 

Any idea if this is going to be fixed in a 5.6.4 patch soon? It's still broken in 5.6.4p4.

 

Thanks very much for the update Karl!
Is there a timetable / known update window for 5.6.5?

 

Fantastic, thanks for the info Karl.

 

Crossing my fingers.

 

Any ETA on this fix/update? I've had a major content patch ready for a month, held up by this bug. I'm hoping to release it before the holiday sales.

 

Is there a chance that the 5.6.5 drop will still make it today? I'm not sure how everyone is getting by for the past few months without being able to access transform.position inside Awake()... am I crazy?

I know that a local workaround is to set the prefab or object's position before instantiating (even though this causes a lot of unnecessary version control changes), but is there a workaround for online/unet games? NetworkServer.Spawn() will have the incorrect transform.position in Awake() on clients.

 

oh my god.

https://unity3d.com/unity/whats-new/unity-5.6.5

 

Actually on my first quick test, it appears to work properly locally. Karl - can you confirm that this is fixed in the latest 5.6.5 release, but is just missing from the release notes?

 

Had position issues with 5.6.4p4, but things seem to be back to normal with 5.6.5f1 now.

 

When will this issue fixed? i got it in latest version 2017.3.1f1. not able to work on a project with a bug like this??

 

When I looked this up, it was fixed in b5 it said, for 2017.3.0.

I just tested it on my copy of Unity to be sure, and it's giving the correct results.
My version: 2017.3.1p2

Patches here: https://unity3d.com/unity/qa/patch-releases

 

real? this not work in 2017.3.1p3
WTF???

void Awake()->this.transform.position = Vector3.one;
void Awake()->Debug.Log(this.transform.position);
Log->(0,0,0)

It's humiliating!!!!

 

update to 2017.4, it is the LTS version and you should be on it if your using 2017.X

 

If you can create the bug in a small repo, file a bug report.