• Rise from your gwave!

Looking to make a Madou Monogatari Saturn translation patch.

Discussion in 'General' started by raybon256, May 15, 2018 at 5:58 PM.

  1. raybon256

    raybon256 New Member

    I'm not sure if this is where I am supposed to post about this, but, my friends and I run a discord featuring Madou Monogatari stuff (and run a site called Puyo Puyo Universe). I want to learn a translation patch for Madou Monogatari (Saturn), and later Waku Puyo Dungon, 1-2-3. A-R-S. Rulue's Spring Break, and Seriri's Happy Birthday.

    As far as the Saturn games go, how exactly do I go about creating a translation patch?
     
  2. klarth

    klarth New Member

    It varies game by game, heres a general (not comprehensive) guide:

    0.) Have someone familiar with computer architecture and ASM on the team. They should read through all the saturn hardware docs and familiarize with the renasis sh2 docs. Knowledge of lz** style compression cant hurt.

    1.) See if Yabause or mednafen can play the game. Yabause has a nicer debug interface, so thats going to be preferred. If neither support you may as well stop here.

    2.) Figure out where the font is stored: System.dat sometimes is a good place to start and just look at it in a tile viewer. Id recommend randomly corrupting the font to verify it is indeed the one in use, there could be several fonts... If you cant find it, it could be compressed in which case you will need to trace it backwards from VDP1 or VDP2 using your debugger.

    3.) Locate the text drawing routine and menu routines. Probably use the debugger again to trace backwards from writes to the video display processors.

    4.) Determine location of the text in files (if compressed youll need to work that backwards again from the debugger and do a file search on the predecompressed text to determine the original file).

    5.) When the original file is located and text format has been determined you should have enough info to decide how you are going to modify both the font, text storage, and text routines. You may need to hack in a vfw font for things to look nice. Expanding a file will require rebuilding the disc image, otherwise cdmage can update.

    6.) Next step is images. Need to determine the formats, and if nonstandard, again use the debugger to figure out a format. Maybe make a custom tool if necessary.

    7.) Audio/Video - Again, need to figure out the format either by staring at the files in a hex editor or tracing the debugger. Then a custom tool needs to get written to update/replace if the formats cant be read with existing tools.

    So... its a lot of work. You can stare at files and pray theres some common tool out there for some things, but inevitably you will need to use a debugger if you want to make real progress.
     

Share This Page