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
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
-
MadeFromPolygons
Feb 06, 2018 11:10
Not fixed.
-
Fowi
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. -
karl_jones
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.
-
karl_jones
Jan 13, 2018 00:00
We are investigating the new 2017.3 reports. Thanks.
-
Justin-Wasilenko
Jan 10, 2018 11:16
Also getting this issue since upgrading to 2017.3
-
topherr
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.
-
Blackvz
Jan 06, 2018 19:50
Still not fixed in 2017.3.0f3 .........
I will downgrade ........
-
Adam-VisualVocal
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.
-
MalteJoeFrid
Jan 03, 2018 15:00
Still not fixed. Our whole project is stalled dead because of this error.
-
Fowi
Dec 29, 2017 03:34
Error. Not resolved yet. I am using 2017.3.0f3.
Important error!!!
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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