ultimate_addon VS sauce_factory

To build or modify the UCE, you’ll need this outdated tool that no longer builds UCE files properly

For posterity, I checked the original UCE from the COX v5 pack. It ran. So then I rebuilt it with the latest core from here using both the original AddOn Tool and the much better tool created by /u/meepowl. Both of those ran as well.

I'm pretty certain the Windows Addon tool uses a pre-built save image as there is one bundled with it and it doesn't include Cygwin ports of truncate, debugfs or mkfs which I needed to generate the save images. Our tool makes these on the fly just as the Linux script in the ultimate_addon tool does.

Hi. I'm trying to build a cross-platform tool to make building UCE images easier. The build scripts for Linux in the sauce_factory and ultimate_addon repos use mksquashfs which can be compiled for Windows but also use mkfs and debugfs to create the ext4 partition (as well as truncate and dd for various things but I can probably find a way round these).

I successfully built a UCE based on FBA libretro last night, using https://github.com/FalkensMaze1983/ultimate_addon and it worked but it sounds like you're saying this is not suitable if I want to be able to save any data. Is that right?

Download the AddOn Tool from here: https://github.com/FalkensMaze1983/ultimate_addon/tree/master/AddOn_tool

heres the download link for the addon tool https://github.com/FalkensMaze1983/ultimate_addon/tree/master/AddOn_tool, also read the readme so you know how to do everything below

A. Find a sauce from the same type of system. Use 7zip to extract the emulator core (.so) and the rom. Use AddOnTool (https://github.com/FalkensMaze1983/ultimate_addon/tree/master/AddOn_tool) to use your own rom or emulator core . Only mame roms are zipped. All others should be uncompressed.

There can be multiple solutions: 1. Map it with RetroArch on PC, then put the generated .cfg file inside the UCE with the new UCE tool. 2. Directly edit the .cfg file inside the UCE to make it right. For mame2010 and later, the .cfg file is in XML format, so it's easier to figure out what to change there. For mame2003, however, the .cfg file is in a binary format with no documentation. I studied the code for a bit and wrote a (very user-unfriendly) script here, so you can dump the .cfg to json, then edit the json, then repack the json into .cfg. I've suggested to u/meepowl that maybe he can create a UI for that.

3. Download and unzip the premade save partition from https://github.com/wn2000/sauce_factory/raw/master/recipes/AddOn_BattleZone/save.zip , to get save.bin

Now you mention inclusion of a custom save partition (inc retroplayer.ini) I can't see where this is done in build_uce.sh. It creates a new ext4 image and inserts work and upper dirs (lines 105-107) then either replaces it with a custom ext4 image from a save.zip file (123-127) or keeps the fresh one.

There is also this: https://github.com/wn2000/sauce_factory/

Just want to share what can be done with MAME's artwork feature. For details please visit https://github.com/wn2000/sauce_factory and look for recipes Sky Diver and Asteroids Deluxe.

I just checked in a recipe for BurgerTime at https://github.com/wn2000/sauce_factory . Please read the instructions there to build the UCE.

# First clone the repo git clone https://github.com/wn2000/sauce_factory cd sauce_factory # define some env variables to point to your directory holding romsets and cores export COREDIR=/my/cores export ROMDIR=/my/roms # finally make make