Patch Instructions

 

I. Requirements

1. Original Shining Force III game discs. For every scenario you wish to patch, the original disc of that scenario is required. Scenario 1 requires the english version.

 2. SF3Patch.exe– Self extracting install includes everything you need to create a patched ISO/CD from the original disc.

SF3Patch.zip – If there are issues with virus software flagging the self-extracting install and you are not comfortable disabling your virus software for the download and install, this is the patch in zip form. Simply unpack where you would normally install.

The patch is available from the SF3 Translation project FTP courtesy of Moogie and Shining Force Central.

 http://sf3transftp.shiningforcecentral.com

II. Patching Process
Information- Once the patched bin or iso has been created it can be played using an emulator or burned to a CD to be played in a mod-chipped Saturn. This method will work with all of the Shining Force III discs.

Instructions
Option 1 – SF3TranslationPatcher.exe
The SF3TranslationPatcher.exe only works with a CD drive (no virtual drive support) and uses the bin/cue format exclusively. Windows 10 is supported.

  1. Place the original game CD in an available CD drive.
    The Scenario 1 patch requires the US or UK version. It will not work correctly with the Japanese version.
  2. Launch SF3TranslationPatcher.exe
  3. The program will auto-detect which scenario is in the drive and ask you to verify. Once you click OK, a dialog will appear with the scenario name at the top in bold.
  4. Here you can enable paul_met’s view increase mod, Rescan Drives or Patch.
    a. paul_met’s view increase mod provides a slightly higher resolution that increases the screen size slightly. Recommended, but may not be ideal for all set-ups.
  5. Click the Patch button and browse to the location you want to place the cue/bin files. The SF3Patch directory is recommended. Type a name for the files. If you are overwriting, be sure the cue/bin isn’t currently mounted and select the bin file to overwrite. Click Save to start the patch process.
  6. Wait for all the command windows to finish. Do not attempt any other activities while the patch is running. This can cause errors.
  7. Use Virtual Clone Drive (or Daemon Tools if you prefer) to mount the .CUE file and run with an emulator or burn the cue/bin to a disc for use in a modded Saturn.

Option 2 – Isomaker

The Isomaker patch works with either a CD drive or a virtual drive and uses the ISO format, but issues with Windows 10 have been reported.

  1. Place the original game CD in an available CD drive or mount an image. If using an image, be sure to place it in a location other than the SF3Patch directory.
    The Scenario 1 patch requires the US or UK version. It will not work correctly with the Japanese version.
  2. Launch ISOMAKER 2.exe
  3. Select the scenario you are patching and click the Make CD button.
  4. Double click the drive of the CD or image.
  5. Wait for all the command windows to finish. Do not attempt any other activities while the Isomaker is running. This can cause errors.
  6. The SF3.ISO and SF3.CUE files will appear in the folder with the ISOMAKER 2.exe.
    These can be renamed so long as both file names and the ISO name on the first line of the .CUE file match. (open, edit and save .CUE file with Notepad)
  7. Use Virtual Clone Drive (or Daemon Tools if you prefer) to mount the .ISO (or .CUE) file and run with an emulator or burn the ISO/CUE to a disc for use in a modded Saturn.

Troubleshooting

If either patch program crashes, try these solutions in order:

  1. Make sure you have enough free disk space. 1 gb is a safe amount.
  2. Move the “SF3Patch” directory closer to the root. It may not work correctly if it is located within many folders.
  3. If you have had either patch program crash or you have stopped it before it finished, you will need to delete the temp folder in the SF3Patch directory. This can be caused from having a cue file mounted in Daemon Tools while trying to run the patch. The SF3Track2.bin file is then locked for editing and can’t be written at the end of the process. Unmount all drives, delete the temp directory and try again.