Does AssetManager Reload All Textures After Android OpenGL Context Loss?
0 reputation · 08 Nov 2020, 09:33 UTC
I am working with LibGDX AssetManager on Android and need to confirm whether the manager is responsible for restoring every managed texture after an OpenGL context loss, or whether each screen must handle reloading manually.
The documented behavior indicates that LibGDX may restore some Texture pixel data automatically, but AssetManager does not guarantee reloading every managed asset. Custom AssetLoader results and manually uploaded Pixmap data are explicitly excluded from automatic restoration. Desktop backends also handle context loss differently, so I cannot assume one behavior applies everywhere.
Because AssetManager holds strong references and uses explicit reference counting, I need to know whether calling finishLoading() after resume is sufficient, or whether I must track which assets failed and reload them individually.
Does AssetManager automatically reload all managed textures after Android OpenGL context restoration? If not, which asset types require manual reloading, and should I call unload() before reloading to avoid duplicate GPU handles?