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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment