Search Issue Tracker
Instantiate<T>(Object, Transform) still uses world space by default
1. Open project attached (InstantiateBug).
2. Open scene "Scene"
3. Press Play.
4. Check gameobject "Parent" children's position.
Expected result: Children will have identical position.
Actual result: Children have different position.
Notes: Instantiate(Object, Transform) function started using local position by default in 5.5: "Using Object.Instantiate(Object, Transform) will now use the Object position as the local position by default."
Instantiate<T>(Object, Transform) was not affected by these changes. Due to that, those functions work differently.
Reproduced on: 5.5.0f3, 5.5.1f1, 5.6.0b5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Animator.Rebind() resets game object position to the original instantiation position
- Deprecated field 'wantsFullScreenLayout' warning is thrown in Xcode
- WebGL build does not comply with Input.simulateMouseWithTouches on mobile
- Running Unity via command line with -buildTarget results in incorrect PlayerSettings tab
- Sharp, glossy outlines when terrain textures intersect