Search Issue Tracker
Fixed in 2021.3.19f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a1
Votes
0
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-21771
Regression
Yes
Unnecessary amounts of warnings are logged when using Graphics.CopyTexture()
How to reproduce:
1. Open the user-attached “CopyTextureSpamBugRepro.zip” project
2. Open the “SampleScene” Scene
3. Enter Play Mode
4. Open the Console window
Expected result: Small (~50) and or no amount of “Graphics.CopyTexture called on texture…“ warnings being logged
Actual result: Abyssmal amount of “Graphics.CopyTexture called on texture…“ warnings are being spammed (~2000+)
Reproducible with: 2021.2.0a1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a24
Not reproducible with: 2020.3.43f1, 2021.1.0a10
Reproduced on: macOS Monterey 12.6 (Intel), Windows 10 (10.0.19044) 64bit
Notes:
- Related Forum Thread: https://forum.unity.com/threads/how-can-i-get-master-texture-limit-logs-to-stop-spamming.1307874
- The main issue is that an unnecessary amount of warnings are being spammed which in turn causes performance degradation in builds as a secondary issue
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.1):
Fixed in: 2023.1.0b3
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.6f1