Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.3.X
Votes
2
Found in
2019.4
2020.2.2f1
2020.3
2021.1
2021.2
Issue ID
1320962
Regression
Yes
[Vulkan] Texture Memory in Memory Profiler Module is not updated when profiling a Vulkan build
Reproduction steps:
1. Download and open the submitted project "TextureStreamingVulkanIssue.zip"
2. Open build settings (File -> Build Settings...)
3. Enable Development Build and Autoconnect Profiler settings
4. Build and run the project
5. Investigate the Profiler's Memory module
Expected result: Texture Memory value changes when the Camera zooms in/out
Actual result: Texture Memory value does not change when the Camera zooms in/out
Reproducible with: 2019.4.23f1, 2020.3.3f1, 2021.1.1f1, 2021.2.0a11
Not reproducible with: 2018.4.33f1
Reproduces with graphics APIs: Vulkan
Does not reproduce with graphics APIs: Direct3D11, Direct3D12, OpenGLCore, OpenGLES2, OpenGLES3, Metal
Notes:
The regression was introduced between Unity 2018.4 and 2019.4
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a7