Okay here's something interesting, and i know the answer is "Just keep the filelist cache, doofus", but because i'm still fixing and moving around ROM libraries, i'm not ready to "finalize" those yet. So every time i've been testing this setup, i have the .wfc cache files for boxarts for the console already installed, but i delete the gameslists, the contents of \wiiflow\cache\lists primarily. So what happens when i load up a console's list "for the first time" on an SD card is that there's a period where the console switches to showing the WiiFlow logo and its "loading" animation. For the vast majority of consoles, this time is negligible, and it immediately after coming back begins building the gamelist cache. The thing i am concerned with isnot the time to build the list, but the time during which you see the WiiFlow "loading" screen. Note that I'm using Rhapsodii Shima 5.4.9 if that changes anything
For both the N64 and Amiga, the "wiiflow loading screen" time seems ABNORMALLY long compared to other consoles. I could try to do some time comparisons, but just for example, it takes at least a minute or few for the N64 list, at 235 games. And for the Amiga, it takes like MANY minutes, like at least 5, on the Wiiflow Loading Screen, even with without me having any boxcovers setup for it (besids the Amiga "Blank Cover"). The Amiga has like 900 or more games?
By comparison, the Wiiflow Loading Screen for the SNES gams, which is like 1000+, is like... less than 10 seconds or so. or maybe 30 seconds. Same for the Amstrad CPC, at 1361 games.
Is there something the Amiga and N64 coverflows have in common that would make loading them take an abnormally long amount of time? Maybe something to do with the "box model" or something? I'm curious what wiiflow is actually doing during that waiting time before it displays the UI and starts building the gamelist out of your cached boxcovers and ROMs.
@RunningSnakes and
@fledge68 lemme know if you have a similar experience.