Question Profiling texture streaming

Hi,

I'm currently testing texture streaming on mobile(android/ios), after setting all paras according to the docs, the streaming mipmap seems to be working.

However, the memory size data from profiler is not accurate(I use wifi to connect to my android phone). The test scene has only one camera and one texture, at the original distance the texture size in memory is a reasonable number, after moving the camera closer/further in the runtime the number goes down to 300+ bytes. The test texture is 2048 * 2048 rgba etc2, I don't think the size of it in memory can go down to 300+ bytes when moving closer.

So is it an editor profiler bug or I'm not using it correctly?

 

I just found this thread because I was having the same issue trying to profile texture streaming on Android and taking memory captures. All streamed textures appeared to be around 300 bytes regardless of their actual state.

After more testing I found out that this is related to Vulkan. Forcing the build to use OpenGL, the profiler works as expected and we can see the texture memory vary when mipmaps are loaded.

The same issue happens on PC if I force Vulkan. The profiler tracks the texture memory correctly with DX11 but not If I do a build with Vulkan.

There is probably an issue with the way the mipmap streaming is implemented with Vulkan where it does not report the memory correctly to the profiler.

 

I created a sample and reported as case# 1320962.

 

For anyone following, the bug was reproduced by QA:
https://issuetracker.unity3d.com/product/unity/issues/guid/1320962