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
- "Initialization Mode" and "Update Mode" drop-downs are not localized in the Custom Render Texture asset
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
This is a duplicate of issue #984954