This was done on Batocera V38 beta, I can test again when I have some cycles to ensure things are still working as they should
I've had so many issues bouncing back-and-forth with Batocera 37 & 38 Beta, I suspect the problem is something on my end. I did notice in the video you referenced, that the newline character is also showing in your log output (at about 9:11 into the video). However, the way my output is formatted in the original post, you'll see it is different, which I think is what caused the images to be 'detected' as text. Again, probably some corruption on my end when I switched back to V38. I'm out of town at the moment, otherwise I'd offer to test again.
Appreciate that insight, the issue you had with text vs. images though was caused by this specifically:
V38 works differently with Pixelcade than V37. We collaborated with the Batocera devs and with V38, Pixelcade is now built into native with V38 so when the user plugs in Pixelcade, Batocera will autodetect Pixelcade and run a built in version of Pixelcade. This build in version however does not have any artwork and when Pixelcade does not find artwork, it shows scrolling text instead (ie, what you experienced).
So to fix this for existing Pixelcade installs which is what you had with V37, we just need to remove Pixelcade from Batocera's startup script , specifically /userdata/system/custom.sh. Once Pixelcade is removed from custom.sh , then Batocera will use the logic to use the built in Pixelcade if the user installed Pixelcade (/userdata/system/pixelcade) does not exist. We want it to use the user installed Pixelcade as that has all the artwork. So when you re-run the install, it'll get you the latest artwork and also automatically remove pixelcade from custom.sh if V38 is detected. So when you upgrade to V38, just do that and you should be fine.
I appreciate your explanation. Still waiting for Batocera V38 'Stable' to be released. When I'm back in town, if I wanted to test & confirm that re-running the Pixelcade script fixes the issues I was having with V38 Beta/Butterfly, and then I wanted to revert Batocera back to V37 again (so I can play games that aren't working with V38 at the moment), would Pixelcade still run OK? Or, would I have to tweak the custom.sh script?
BTW - If the above would cause more hassle than it's worth, then I'm totally fine continuing to wait for V38 Stable (+ a little extra time to assure stability), then biting the bullet and updating both Batocera and Pixelcade, and then just opening issues to the Batocera team if the (suspected) bugs continue to be an issue with V38 Stable.
you'd need to run the script when you do V38 and then re-run it again when you go back to V37. It's up to you but I'd recommend just to wait for V38 GA to come out.
Thx - Noticed that ("Blue Moon" premier trailer) in my subscription feed. There is one bug that looks like it just got fixed and might make V38 Stable, so my plan is to wait. I recently found / fixed some issues (batocera-boot.conf file got clobbered, Flatpak app corruption) that I'm pretty sure were caused by going back-and-forth between Stable and Beta, so I plan to avoid doing that moving forward (setting up a virtual machine for testing may be a better approach...).