Scrappy is an art scraper for muOS, with the standout feature of incorporating a fully-fledged Skyscraper app under the hood. This integration enables near-complete support for artwork XML layouts, allowing Scrappy to scrape, cache assets, and generate artwork using XML mixes with ease.
I have a few systems that Scrappy says its finding art for (using the built in scraping) but the art isnt showing in the system folders after doing so.
The scraper is showing me the boxart in the preview window, but when I go to my games folders for those systems, no boxart shows up. I have around 20 different systems/folders and its only an issue with three of them. The NEC SuperGrafx, Nintendo FDS (famicom disk system) and the SuFami Turbo (a SNES addon made by Bandai).
I thought maybe the issue at least with the SuperGrafx was the omission of the .sgx filetype from the peas.json file, but even after adding it, still getting blank box art in the folders.
However, still I only get the image previews and not showing up in the games folders.
Also, unrelated - after importing custom images, can the source picture files (.png, .jpg, etc) be deleted from the import directory or do they need to remain?
I figured out the issue for Famicom Disk System and SuFami Turbo was because I didn’t have default cores selected which I realized was needed after reviewing Artwork | muOS so this was a muOS issue (and a user issue-me lol) ultimately.
The issue for SuperGrafx, however, as best as I can tell, is maybe because Scrappy’s peas.json file lists SuperGrafx as an alias for PC Engine and PC Engine CD. I realized the art was getting scraped into my PC Engine in MUOS/info/catalog meanwhile muOS has a dedicated catalog folder for SuperGrafx so after just moving those png files into the SuperGrafx folder they showed up.
Anywho, thanks for the great app! Maybe update peas.json so SuperGrafx is treated as its own system would save that last remaining non user related issue I had
SG-1000 art is being saved in the master system folder. I don’t know if it has to do with Scrappy or how Skyscraper interprets those games. For the moment you can move their art from the /catalogue/master system folder to the sg-1000 folder or just set the genesis plus gx core, the default for sg-1000, but using master system as the system, then the art will show. You guys can check the logs in the scrappy folder to see where art is being saved and what is happening. Probably other games where scrapping is happening but no art is showing are just being saved to a different location than expected too. The logs are really helpful, check and share them when issues are found.
And about art not appearing to a folder without a set system/core, I don’t see how it is a muOS issue. muOS binds artwork by system, so without one set, no art will be shown. If you think the naming convention you use for those systems should be auto assigned by muOS, you can post in Ideas for them to be considered and most probably included in the auto assign list.
I’ve opened up an issue on Github so you can track the progress and gather evidence.
For now, can you check which platform your SG-1000 folder is mapped to in config.ini?
I have another question. I downloaded the Dolphin core, and I got scrappy to actually scrape gamecube box art, and it the cache data will make its way to the scrappy_cache folder - but from there it doesnt covert to an image file over to the muOS nintendo gamecube catalogue folder (or any system catalog folder). Not sure if there is something I can tweak to make it work. Not sure if its even possible given this is an added core and not a part of a stock muos install?
I also wanted to add something I have been able to replicate with every single custom import I have done. If you do a custom import and do “scrape single rom” for those games, it will ignore your import and just scrape from screenscraper. In order for it to detect your custom import you have to do the full scrape scan.
Currently Gamecube is not oficially supported on Scrappy, so there is no catalogue mapping. If you feel comfortable doing so, you could manually edit the code, by adding the platform and its corresponding catalogue folder in helpers/muos.lua. Add an entry in the platforms table with the format ["<platform>"] = "<catalogue folder>"
This will be addressed in a future update. Overwriting existing resources when using single scrape was a requested feature, but I’ll add the option on-screen as that makes a lot of sense.