Search Issue Tracker
Active
Votes
0
Found in
2019.4
2020.3
2020.3.18f1
2021.2
2022.1
Issue ID
1388862
Regression
No
Incompatible texture type is used after getting out of play mode
How to reproduce:
1. Open the project "MetalTexture3D.zip"
2. Notice that the sphere in the scene is white.
3. Enter the Play Mode
4. Exit the Play Mode
5. Observe the sphere's color
6. In Metal, observe the console
Expected result: The sphere is white after step 4.
Actual result: The sphere is either black (D3D11, D3D12, OpenGL, Vulkan) or disappeared (Metal). Also on Metal warnings appear: "Metal: Shader[Vuforia/VFX/Lit/VolumeTexture]: Incompatible texture type [MTLTextureType2D] of texture bound at index 0, expected [MTLTextureType3D]"
Reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Texture Compression default texture format is set to PVRTC when building via script BuildPipeline.BuildPlayer
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
Add comment