fix(mister): arcadepatches MRAs fail to find RBF when launched from Zaparoo UI #1663

Activity

1. zaparoo-automation-bot

   added

   bugSomething isn't workingSomething isn't working

   on Oct 16, 2026
2. wizzomafizzo

   changed the title [-]Street Fighter Alpha 3 USA Restoration.mra attachment was reported with no text content.[/-] [+]fix(mister): arcadepatches MRAs fail to find RBF when launched from Zaparoo UI[/+] on Oct 16, 2026
3. wizzomafizzo commented on Oct 16, 2026

   

   wizzomafizzo

   on Oct 16, 2026

   Member

   More actions

   Investigation results:

   • The attached MRA is valid: <rbf>jtcps2</rbf>, setname sfa3r, and 3048 <patch> blocks (1.6 MB).
   • Not reproduced. On a MiSTer test device with _Arcade/cores/jtcps2.rbf, I launched the MRA through Core from _Arcade/_Arcade Patches/_Restorations/. Main resolved RBF: /media/fat/_Arcade/cores/jtcps2.rbf and loaded the core. A copy under _Arcade/_Arcade Patches/_Arrangements/_CPS+/ resolved the same way. Launching from the Zaparoo UI itself was not tested.
   • Core sends the path to Main unchanged as load_core <path>, the same call the MiSTer menu makes, so the code gives no reason for the two to differ.
   • Found and fixed a separate bug: the setname reader for MiSTer docs artwork skipped any MRA over 256 KB, which drops every large patch MRA. Fix in fix(misterdocs): read setname from MRAs larger than 256 KB #1665. Unit tests in pkg/database/scraper/misterdocs pass and task lint is clean.

   To find the cause of the RBF failure, a /media/fat/zaparoo/main.log and /tmp/zaparoo/core.log from a failing launch would show the exact path Main received and the folder it searched.
4. Firehawke commented on Oct 16, 2026

   

   Firehawke

   on Oct 16, 2026

   More actions

   https://logs.zaparoo.org/Ucc6zCCZ.log is what the system provided.
5. Firehawke commented on Oct 16, 2026

   

   Firehawke

   on Oct 16, 2026

   More actions

   core.log
6. wizzomafizzo

   closed this as completedin #1667on Oct 16, 2026