FlushAsyncLoading message after migration from 5.4.4. to 5.5.1.

[PIXEL_THUNDER]

Hi there!

We’ve migrated our project from UE5.4.4. to 5.5.1. and things are looking pretty good aside from one thing. We keep getting this same message in the log whether we’re doing anything or not, and it’s spewing it out like crazy, every frame or so. I’ve been wading through various forums but can’t seem to find an answer. Have you seen anything like that before?

LogStreaming: Display: FlushAsyncLoading(6181): 1 QueuedPackages, 0 AsyncPackages
LogStreaming: Display: FlushAsyncLoading(6182): 1 QueuedPackages, 0 AsyncPackages
LogStreaming: Display: FlushAsyncLoading(6183): 1 QueuedPackages, 0 AsyncPackages
itd.

[llikdowk (guillermo ferrando)]

This happened to us too upgrading 5.4.2 → 5.5.2.
Delving a bit in the internals by putting a breakpoint in the log and pulling the thread a bit I found this:

And apparently it was trying to load this texture but not finding them:

• STBlueNoise_vec2_128x128x64

My solution so far has been going to the path where it’s trying to find them /Engine/EngineMaterials/ and duplicate the texture that had a similar name (and I assumed similar purpose, if not the same) and renaming it.

• FastBlueNoise_vec2_128x128x64 → STBlueNoise_vec2_128x128x64

I’m not very sure of the implications of this but it has solved the verbose log.

EDIT:
Checking a bit deeper I could see a redirector of STBlueNoise_scalar_128x128x64:

My guess is that epic renamed these textures from STBlueNoise to FastBlueNoise but the rename didn’t happen cleanly.

[PIXEL_THUNDER]

Hi.
Great bit of advice! In our case, it was this file: “STBlueNoise_scalar_128x128x64”. After making a copy of some other texture and renaming it, the endless log stopped.