ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
AssetManager load queue stalls at 75% progress In a libgdx project using AssetManager to load multiple textures asynchronously, the getProgress() method reports 0.75 and never reaches 1.0 even after repeated calls to update() . The AssetManager is initialized on the main thread, and update() is invoked inside the render loop. All assets are queued with load(
Problem Statement When an asset that references other assets is unloaded via AssetManager.unload(), the dependent assets continue to occupy GPU and RAM memory, even though their reference counts drop to zero. Constraints AssetManager uses a global reference counter but does not traverse the dependency graph on unload. The API is identical across desktop, And
AssetManager provides load, get and update APIs for asynchronous asset loading with automatic dependency graph resolution in libGDX core. Reference counting is manual via references; AssetManager.dispose() decrements counts but does not auto-unload assets when count reaches zero, requiring explicit unload calls. Behavior around failed loads and manual refere
Goal: determine whether calling AssetManager.update() every render frame causes intermittent frame hitches while large textures load asynchronously in a libgdx desktop application. Constraints and uncertainty: AssetManager performs incremental decoding on the OpenGL context thread when update() is invoked, but per-frame cost depends on asset size, backend, a
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 re
libgdx
android