Search Issue Tracker
By Design
Votes
1
Found in
2021.3.28f1
2022.3.4f1
2023.1.3f1
2023.2.0a23
Issue ID
UUM-42134
Regression
No
Graphics.CopyTexture doesn't work correctly when using Texture Streaming
How to reproduce:
1. Open the user-attached project “TextureStream”
2. Click Build And Run
3. In the Player, click "Load Tex0", "Apply Tex0" and then "Copy Tex0 to Tex1" buttons
4. Observe the two Cubes
Expected result: The textures on both Cubes are identical
Actual result: The texture on the second Cube is different
Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a23
Reproducible on: Windows 11 Pro, macOS 13.4 (Intel)
Note: Not reproducible in the Editor
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This issue is "by design", even if the error reporting (or rather, the lack of it) doesn't make it immediately obvious what is happening.
The Graphics.CopyTexture does not load the mipmap levels needed to perform the copy.
If you wish to copy a full texture, you must thus ensure that all mipmap levels are loaded using, for example, "m_tex0.requestedMipmapLevel = 0" followed by a wait until "m_tex0.IsRequestedMipmapLevelLoaded()" is "true" -- only then will the CopyTexture look correct.