Documentation

Unity Engine

User Manual

Script Reference

Unity Engine

Make a texture compatible with asynchronous texture loading

Configure a texture or a mesh so Unity can load it in the background.
Read time 1 minuteLast updated 22 days ago
A texture is eligible for the asynchronous upload pipeline if the following conditions are met:
  • The texture is not read/write enabled.
  • The texture is not in the Resources folder.
  • If the build target is Android, LZ4 compression is enabled in the Build Profiles window.
Note that if you load a texture using 
LoadImage(byte[] data)
, this forces Unity to use the synchronous upload pipeline, even if the above conditions are met.
A mesh is eligible for the asynchronous upload pipeline if the following conditions are met:
  • The mesh is not read/write enabled.
  • The mesh is not in the Resources folder.
  • The mesh has no BlendShapes.
  • Unity has not applied Dynamic Batching to the mesh, either because the mesh is ineligible for Dynamic Batching or because Dynamic Batching is disabled. For more information on Dynamic Batching, see Draw call batching.
  • The mesh vertex/index data is not needed by a Particle System, a Terrain, or a Mesh Collider.
  • The mesh has no bone weights.
  • The mesh topology is not quads.
  • The meshCompression for the mesh asset is set to Off. If the build target is Android, LZ4 compression is enabled in the Build Profiles window.
In all other circumstances, Unity loads textures and meshes synchronously.