Search Issue Tracker
Fixed
Fixed in 2021.3.29f1, 2022.3.6f1, 2023.1.2f1, 2023.2.0a21
Votes
0
Found in
2020.3.19f1
2021.3.20f1
2022.2.8f1
2023.1.0b7
2023.2.0a5
Issue ID
UUM-30877
Regression
No
Graphics.CopyTexture is called with mismatching mip counts when Anti-aliasing is used
Reproduction steps:
1. Open the attached project “TextureBug“
2. Select the Custom Render Texture “Assets/Texture”
3. Save Project (CTRL+S)
4. Observe the Console Window
Expected results: The project is saved without any errors
Actual results: “Graphics.CopyTexture called with mismatching mip counts“ error is logged in the Console Window
Reproducible with: 2020.3.19f1, 2021.3.20f1, 2022.2.8f1, 2023.1.0b7, 2023.2.0a5
Reproducible on: Windows 11
Note: Issue is reproducible when Custom Render Texture has “Enable Mip Maps” and “Double Buffered” properties enabled, and Anti-aliasing is set to “8 samples”
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
- [iOS] Back Triple Camera is not focusing manually and automatically
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
Resolution Note (fix version 2023.2.0a21):
Fixed mismatch mipcount error with double buffer and anti-aliasing on.