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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #984954