Author Topic: Upgrading woes  (Read 2029 times)

procyon

  • Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Upgrading woes
« on: January 20, 2020, 02:38:22 AM »
I've been using RetroFE for the better part of three years now, and I love it.  But I'm starting to build a new rig, modding an Arcade1up, and I wanted to bring my 3 year old load out up to date.  It has not been easy.

When I did my initial install, I started with the base package from the EmuMovies FTP, and used it as a guide and a template on how to set up the rest of the systems.  I went about downloading all of the art assets and movies, and migrated directories to where the base package taught me to place them so that nothing needed to be specified in the settings.cfg files, RetroFE would just find everything in the default locations (collections/SYSTEM NAME/medium artwork and collections/SYSTEM NAME/system artwork).

Fast forward three years later, and I want to bring all of the artwork and movies up to date.  The tool that seems best for the job is the EmuMovies Sync. Not only will it update my art files, but it will match the asset names to the current file names I have, according to the latest No-Intro dats.  The problem is, it wants the directories in an entirely different structure.  And I'm not going to try to move the RetroFE directories back to the way EmuMovies Sync wants, there's just too many systems.  So the path of least resistance, it would seem, is to start over again, using EmuMovies Sync, and modify the settings.cfg to match the way EmuMovies wants to download the files.  This way, I get the new files (and the old files over), and then whenever I'm ready to update again in 3 years, I just run Sync again and let it pull the missing assets.

But that only gets me part of the way because now I need to generate new include.txt files.  What I've been doing is going into each rom directory and running dir /b > include.txt, and then opening that file in a text editor to strip all of the .zip extensions from every line, and adding that back into my collections folder.

I don't really know if I'm doing things the best way.  Does anyone have other suggestions to try?  I'm willing to keep going like this until I have every system I need done, but it's going to take a few nights to do it right.  It's going to be even tougher for the few systems where I split out Japanese games from the rest, like my NES collection vs. Famicom collection, SNES vs Super Famicom, Turbo Grafx-16 vs PC Engine, etc.  Also, does anyone know how to easily generate include.txt files for the various arcade collections that Hyperspin supports?  Like Namco Classics, Konami Classics, etc.?

Thanks.

Pieter Hulshoff

  • Administrator
  • Hero Member
  • *****
  • Posts: 1534
  • Karma: +46/-14
    • View Profile
    • Towel 42
Re: Upgrading woes
« Reply #1 on: January 20, 2020, 06:53:51 AM »
The include.txt files on the EmuMovies FTP are only there so people could see the artwork without having the roms. If you delete it (or rename it), RetroFE will simply read your roms directory.

procyon

  • Newbie
  • *
  • Posts: 23
  • Karma: +0/-0
    • View Profile
Re: Upgrading woes
« Reply #2 on: January 21, 2020, 04:14:27 AM »
The include.txt files on the EmuMovies FTP are only there so people could see the artwork without having the roms. If you delete it (or rename it), RetroFE will simply read your roms directory.

Ah, OK, that makes sense.  What, then, is the distinction between include.txt and menu.txt?  Also, does exclude.txt support wildcards?  Could I, for example, exclude any game in my directory that matches *(Beta)*?

Agent47

  • Global Moderator
  • Full Member
  • *****
  • Posts: 160
  • Karma: +7/-41
    • View Profile
Re: Upgrading woes
« Reply #3 on: January 21, 2020, 04:20:06 AM »
What, then, is the distinction between include.txt and menu.txt?  Also, does exclude.txt support wildcards?  Could I, for example, exclude any game in my directory that matches *(Beta)*?

include/exclude.txt are for items in a collection. menu.txt is for submenus. None of them support wildcards, what you enter there is used verbatim.