Search Issue Tracker
Fix in review
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.
- Editor DPI scaling issues - menus/tabs/etc. appearing in wrong location when opened/dragged
- Second Hierarchy window is focused when creating object in main Hierarchy
- Editor crashes when deleting in-use SpeedTree Terrain assets
- Error CS0266 when using Implicit operator to convert Nullable<> struct to non-nullable
- [UWP] Ping doesn't work and an exception is thrown when Ping.isDone