Covers downloaded through WiiFlow do not show for Wii games

[treyus30]

Describe the bug
A clear and concise description of what the bug is.

As simple as it sounds: I have over 1300 Wii titles and confirmed their covers' existence after downloading via the built-in function. They do not show. Only a handful show and there's no pattern that I can see. I've restarted several times, reloaded themes, reloaded cache.., it's like they're just being ignored at random, perhaps due to a memory shortage?

I should note I also have over 500 Gamecube titles and a majority of their covers (downloaded the same way) show up in the separate GC category.

[eku]

This is not a forum for support but only to report bugs in the source code. Since it obviously works for others, you should look for help in the support thread.

In addition, you have not provided any information about the version used, your configuration and the media. These are requested in the bug form for a reason.

[treyus30]

The latest version, v5.5.4-1, 5TB USB HDD formatted as FAT32.

Everything else works - launching games, running the app, switching themes, downloading covers, etc... Just not displaying ALL of the covers downloaded at once (only some at random). Previously, when I had only a few titles, it was fine. Those title covers now do not show either, leading me to believe this is a bug, not a me-problem, and I don't have the knowledge to investigate the source code myself. This would seem to be due to the size of the collection, which is why I posted here. Do you have emperical evidence of it working for others at this scale?

[gingerbeardman]

I would assume there's not enough memory to load 1300 covers, but that's just a guess as to why only some are shown.

[treyus30]

I would assume there's not enough memory to load 1300 covers, but that's just a guess as to why only some are shown.

I would too. A quick solution to this would be to load only so many, and unload/load sequentially on scroll. As to how many it can keep loaded, testing would be needed, but I figure 100-500 would be enough to keep up with alphabetical scrolling.

[eku]

A quick solution to this would be to load only so many, and unload/load sequentially on scroll.

Pull Request is more than welcome.