I have a question while examining the slate source code regarding the usage of texture atlases. The engine processes image texture atlases and font texture atlases separately. The image texture atlas is created in FSlateRHIResourceManager::LoadUsedTextures, and the font atlas is created in FSlateElementBatcher::AddTextElement. My question is, does the engine distinguish between static and dynamic atlases? When packaging a mobile game, some of the image and font texture atlases should be pre-packaged to avoid the time-consuming dynamic generation of atlases during runtime. However, I didn’t see any indication that the engine handles this preloading of atlases. Does anyone know how the engine manages this preloading? Any information would be appreciated.