Search Issue Tracker
Duplicate
Votes
1
Found in
2017.3.0a1
2017.3.0f3
Issue ID
984925
Regression
Yes
Instantiated UI elements get incorrect values in ScrollView's content's localposition
Steps to reproduce:
1. Open user attached project
2. Open the scene named "testscene"
3. Notice that testscript.cs is set to instantiate an object in localposition at (15,-15,0)
4. Run the scene
5. Notice an "Image" game object instantiated at position 0, 0, 0
Expected result: game object should be spawned at the correct position set by transform.localPosition
Reproduced in: 2018.1.0b1, 2017.3.0f3, 2017.3.0a1
Not reproduced in: 2017.2.1p1, 2017.1.2p4
Regression since: 2017.3.0a1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #984954