Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X
Votes
3
Found in
2022.1.21f1
2022.2.0b12
2023.1.0a15
2023.2.0a1
2023.3.0a3
6000.0.0b11
6000.1.0a7
7000.0.0a1
Issue ID
UUM-33953
Regression
No
Warning "Registering a native texture with depth=0 while the actual texture has depth=1" is thrown when in Play Mode and creating a Cubemap from another Cubemap's native texture
Note: this bug was split off from https://jira.unity3d.com/browse/UUM-22094 because it exclusively concerned DX11.
(UUM-22094 fixes the CubemapInspector issue from the original report)
The repro project can be retrieved from the original ticket (too heavy to upload here). The original description can be found below:
How to reproduce:
1. Open the project "IN_19061"
2. Enter the Play Mode
3. Observe the Console
Expected result: no warning
Actual result: warning "Registering a native texture with depth=0 while the actual texture has depth=1"
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
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
- 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
xc
Jul 26, 2024 08:11
Found in 2021.3.37f1
Warning:
Registering a native texture with depth=1 while the actual texture has depth=0