Bug with async texture compilation in editor

Development Rendering
, ,
1

Hi,

I just wanted to provide some additional information for a bug that my colleague has reported: [Textures not loading until [Content removed] and https://issues.unrealengine.com/issue/UE-305449

This seems to be caused by a bug in the experimental async texture compilation feature. It goes away if you turn it off in the editor preferences.

The problem seems to be that sometimes the manager doesn’t track all the textures, especially if you load assets asynchronously. So some of the textures will remain default textures. You can check if a texture is still compiling by calling UTexture::IsDefaultTexture() but the problem seems to be that the manager is not even aware of the texture. Our workaround is to call FTextureCompilingManager::Get().AddTextures() for all the loaded textures where we are observing this bug.

No response needed, just wanted to provide some additional information.

Thank you.

PS: This also happens in 5.6.1.

2

Hi George,

Thanks for the extra information. I have made the team aware of your notes. We are currently backlogging this item because we cannot reproduce the issue independently. Do you have a small project available to share with us?

3

Unfortunately, the one case where we can repro it reliably (3 out of 4 times) depends on a lot of custom code so it would be quite a lot of effort to recreate it in an independent project. But if we find an easier repro, we will let you know!

4

Ok, that sounds good. I will close out the case for now, but if you end up putting together a repro project, feel free to open the ticket again.