Search Issue Tracker
Fixed
Votes
0
Found in
5.5.0p4
Issue ID
873836
Regression
No
Instantiate<T>(Object, Transform) still uses world space by default
Reproduction steps:
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
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
- Select Preset "None" icon changes after switching tabs
- [Android] Crash when using xxHash3 and targeting the ARMv7 Architecture with IL2CPP Scripting Backend
- GameObject reference in a Script Component becomes missing when unpacking a variant of another Prefab variant
- Project Settings vertical separator position is not synchronized with the mouse position when dragging it horizontally
- Crash on PhysicsDebugDraw::SelectFiltering::Update when entering play mode with Physics Debug window docked and unfocused
Gianvy
Apr 12, 2017 20:09
The problem persists in the version 5.6.0f3
marf
Apr 12, 2017 20:05
Same problem here!