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
Comments (1)
-
Peter77
Jun 27, 2020 03:41
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
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