Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a1, 7000.0.0a1
Votes
1
Found in
2022.1.21f1
2022.2.0b12
2023.1.0a15
2023.2.0a1
2023.3.0a1
7000.0.0a1
Issue ID
UUM-22094
Regression
No
CubemapInspector error spam when a native Cubemap texture is being inspected
How to reproduce:
# Open the project “IN_19061”
# Enter the Play Mode
# Select the "CubemapRepro" GameObject in the hierarchy.
# Observe the Console
Expected result: no errors (a warning regarding native textures may pop up, this is being fixed separately)
Actual result: multiple errors -> "Can't read from Cubemap" and "Texture of width 128 and height 128 is not accessible."
Reproducible with: 2022.1.21f1, 2022.2.0b12, 2023.1.0a15
Couldn’t test with: 2020.3.40f1, 2021.3.12f1 (due to compiler errors)
Reproducible on: Windows 10 Pro
Note: not reproducible in Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment