Incidentally, good job on the DEOT continuation. I never flashed the original version, so I don’t have anything to compare it to, but it seemed to look and work well in the bit of poking around I did last night after I flashed it.
I put this DEOT on my 400GB card, which I had mostly given up on using in the Gameshell at all (but hadn’t gotten around to using for anything else), since I could never properly flash and use the official 5.0 on it. It always gave verification errors after the flash, and didn’t work in the device either. (The same 0.5 file flashed fine to my 256GB card, which is the one still currently in an uncertain state with Buster, but hopefully I can revive.) Your DEOT variant not only flashed, but the script you included to expand it to the full card also worked fine. Though it’s certainly overkill (even 256GB was kind of ridiculous, even for keeping lots of code around and building lots of things!), I’m thinking what I may do is pretty much archive the entire contents of my old card from within the system as tar.gz, and then extract it out to a temporary directory on the new card. It will still take a lot of digging and tinkering, but at least having all the contents on the card will make it easier to move stuff around and piece things together.
I think you’re already aware of the other minor bugs I’ve found: the volume and brightness controls are still partly using the background from the original firmware.
Also, is it redundant to have “Retro Games” -> “id” -> [various games] AND “ChocoDM” at the top level? I haven’t set up any of them or tried them, but I’m assuming they are essentially the same thing, with ChocoDM providing the old style list when games are available and the other menu area providing icons for each game?
There’s also an awful lot of stuff on the top level of the launcher menu. It was fun to see the old DEOT toys (since I’ve never seen them before), but it might be worth considering organizing things a bit differently. Maybe create an “Extras” entry at the top where these things, and perhaps other less used and unessential stuff could live?
Since I haven’t been following along very closely with the updates of DEOT, does the option to “update launcher” work? Or does it wreck everything? Since it probably just does a git pull in the launcher directory, I’m assuming whatever is true for one is true for both. I’m not going to try it because I’ve had my fill of wrecking systems for now, but I thought it was worth asking. If it does indeed wreck things, then it might be a good idea to remove it from the launcher code entirely. It’s less likely someone would run a git pull under launcher, but I could see folks trying to update this way and then getting into trouble. Or is this something that has issues when you change skins back to the old launcher? Or does it work everywhere now? Like I say, I haven’t really followed along closely. But if there is a way to wreck the system conveniently provided in a menu, that’s probably a bad idea.
One more question, though not really a Gameshell specific one… It seems like everyone else is already familiar with the Retroarch XMB interface. I haven’t used it or the other Retroarch menu that much. It seems like the XMB could be pretty powerful, but I confess to not really knowing how to set it up properly, in terms of adding ROMs. For the other version, I always selected a core and then selected a ROM, to launch a game. That felt clunky, and I get the feeling that it could automatically load appropriate cores for ROMs if I set it up properly, possibly even including extra information about the games, etc. Does anyone know of a good tutorial for how to setup and use Retroarch and the XMB interface? Preferably not a video, if possible, as I’d rather read and follow a guide than sit through a long video of someone fumbling through an explanation. I’m not actually looking to do a specific thing here (“OMG run whatever game on Retroarch!”), but instead looking for an overview with enough details to let me explore further if I want. I saw the Retroarch website has a decent high level overview of the interface, but I haven’t really found a sort of “suggested use” walkthrough. And I can’t imagine it’s just going to magically work if it detects ROMs in the correct places. How does it identify them and get the appropriate metadata, etc? What other things need to be set up? I followed along with the development of MAME over the years and am familiar with the ins and outs of it, but I largely ignored Retroarch, and I guess I missed out on seeing it evolve and learning where to look for how to use it and tweak it.