Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2019.3.12f1
2020.1.0b3
2020.2.0a2
Issue ID
1268152
Regression
Yes
A GameObject that is copy pasted to a different parent does not have the same world position as the original GameObject
How to reproduce:
1. Open the attached 'project-1268152.zip' project
2. In the Hierarchy window copy the 'Capsule' object (child of 'Plane')
3. Paste it as a child of the 'Plane (1)' object
Expected result: the new object is in the same position as the original
Actual result: the new object is in a translated position relative to the new parent
Reproducible with: 2019.3.12f1, 2019.4.7f1, 2020.1.0b3, 2020.1.2f1, 2020.2.0a2, 2020.2.0a20
Not reproducible with: 2018.4.26f1, 2019.3.11f1, 2020.1.0a1, 2020.1.0b2, 2020.2.0a1
Comments (2)
-
cassius
Oct 24, 2020 02:05
I thought this was a feature, not a bug. I use it all the time, dozens of times per day in fact. It's a very useful way to get objects parented within the scene view that are not Prefab'ed.
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b2
Resolution Note (fix version 2020.1):
Fixed in 2020.1.9f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.13f1