Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.15f1
2019.4
2020.1.0b10
2020.1.0b11
2020.2.0a12
Issue ID
1252798
Regression
Yes
Mesh.GetUVs returns canAccess = false when the mesh is Instantiated / Cloned
Reproduction steps:
1. Open attached project "SetUv.zip" and scene "SampleScene"
2. In Hierarchy window, select GameObject
3. In Inspector window, right click "NewBehaviorScript" component -> "using GetUvs method"
4. Observe Console window
Expected result: No exception is thrown
Actual result: "'Not allowed to access uv on mesh" exception is thrown
Reproducible with: 2019.3.15f1, 2019.4.0f1, 2020.1.0b10, 2020.1.0b11, 2020.2.0a12, 2020.2.0a14
Not reproducible with: 2018.4.23f1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a13
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
- Ligtmaps disappear when entering the Play Mode
- [Vulkan] [Android] Visual corruption is visible on some Android devices in the Player when Depth Of Field is enabled in Global Volume and the Vulkan Graphics API is selected
- An image bleeds out of the borders of a Mask when the project is opened with the iOS Build Support module
- Shadows do not appear on the Material with a custom shader which uses screen space shadow map in HDRP when Ray Traced Shadows are enabled
- An emoji is not shown in the UI Builder Viewport and the Game view when it is placed in the Labels text attribute and Usage Hints is set to Dynamic Color
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a16
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b15
Resolution Note (fix version 2019.4):
Fixed in 2019.4.3f1