Patch Instructions

I. Downloads
SF3Patch.exe (this package) – Self-extracting install includes everything you need to create a patched disc image/CD from the original disc.

SF3Patch.zip (by request) – 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.

Other downloads needed for using an emulator:
(this info is a bit outdated, but SSF is still a valid option)
Saturn Emulator – both work, neither are perfect.
There are also some newer, more involved options available.

SSF – emulator of choice for those who have the computer hardware to run it.
            012 beta R2.zip          –           Newest recommended version
            009 alpha R4.exe        –           If you have any issues try this version
Cassini – works better for those with slower computers
            Cassini.exe
Virtual Clone Drive (or Daemon Tools if you prefer) – Virtual drive software used with all emulators
            SetupVirtualCloneDrive5500.exe
            daemon4123-lite.exe

These files are available from the SF3 Translation project FTP courtesy of Moogie and Shining Force Central.
Right click and “Save Target As…” to download files. Single left click on a txt file to view.

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
Options for patching are listed in order of recommendation. Older options will continue to be provided for users who have a need for them. The patch wizard detects your exact game version which the other options do not. This can result in issues when using the other options. Please use the patch wizard to avoid issues and if you do have issues, please report them, so we can get it working perfectly for everyone.

Option 1 – SF3Translation.exe (New patch wizard located in the SF3PatchWizard directory)

The SF3Translation.exe will work with a physical CD drive or a virtual drive and uses the bin/cue format exclusively. Windows 10 is supported. (Mac coming soon!)

1. Place the game CD in an available CD drive or mount the image in a virtual drive. Supports multiple images mounted at once. The Scenario 1 patch requires the NA or PAL version. It will not work correctly with the Japanese version.

2. Launch SF3Translation.exe.
The first time you launch the exe you will be prompted to download and install Windows Core.net library which is a one-time install that future proofs the patch wizard app. Select the version that is right for your system x64 (52mb) or x86 and download. Once it has finished downloading, go to the file and install. Once the Core.net library has been installed, re-launch SF3Translation.exe.

3. Gabriel is your personal patching wizard. He will auto-detect which scenario is in the drive and ask you to verify. You can use the arrow keys to change the selection or click on your selection with the mouse. Click or enter to select Yes or No.

4. You will have an opportunity to enable the view increase mod.
Click or enter to select Yes or No.

  • paul_met’s view increase mod provides a slightly higher resolution that increases the screen size by a few pixels. Recommended, but may not be ideal for all set-ups.

Other bug fixes and enhancements will be applied automatically depending on the scenario and version you are patching. The fixes are as follows:

  • Overlapping class and level text on the record loading screen fixed (all scenarios)
  • The Titan’s barrier can be broken with the Elbesem Orb, so it can be defeated as in the Japanese version (Sc1 NA and PAL)
  • The mixed-up lines after the Catacombs (Sc1 battle 27) fixed. Basanda had an extra line in the PAL version that was removed. (Sc1 PAL)
  • Garosh bug fixed. This caused Garosh to lose stats instead of gaining when reaching levels 20-29 after his final promotion to Bow Master. (Sc3 and PD)
  • 60 Character bug fixed for the Premium Disc, previously if the gameshark was used to add Rogan, another character had to be removed. This fix allows all 60 characters without crashing. (PD)

5. Browse to the location you want to place the cue/bin files and provide 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 patching process.

6. Wait for the Now Loading… to finish. It’s recommended to allow the patch to finish before launching any other computer activities.

7. Gabriel welcomes you back and reports patching success or failure. He then asks if you would like to patch another disc. If Yes is selected, he will invite you to ready the next disc. Once you press any key to continue the patch wizard will start again. If multiple disc images are currently mounted, you need only press any key to continue.

8. Use Virtual Clone Drive (or other virtual drive software if you prefer) to mount the .BIN (or .CUE) file and run with an emulator or burn the cue/bin to a disc to use in a modded Saturn.

Possible Issues:
The SF3Patch Wizard is enjoying its initial release, so issues are possible. The patching process should wrap up a few seconds after the disc stops reading, but may fail or the wizard may hang indefinitely at some point. If you run into any issues, please reach out to us to report them. The best place will be the SFC forum thread noted in the release announcement on the official site or direct email link on the Credits and Contact page of the official site.

http://sf3trans.shiningforcecentral.com/
http://sf3trans.shiningforcecentral.com/


Option 2 – SF3TranslationPatcher.exe (Located in the SF3Patch directory)
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 game CD in an available CD drive.
The Scenario 1 patch requires the NA or PAL version. It will not work correctly with the Japanese version. If you are patching a Scenario 1 PAL version, you will need to rename a couple of folders to get the PAL exclusive fix. Rename ‘SF3Patch\files\s1’ to ‘SF3Patch\files\s1 NA’ and then rename ‘SF3Patch\files\s1 PAL’ to ‘SF3Patch\files\s1’.

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 by a few pixels. Recommended, but may not be ideal for all set-ups.

Other bug fixes and enhancements will be applied automatically depending on the scenario and version you are patching (note the PAL folder renaming above). The fixes are as follows:

  • Overlapping class and level text on the loading screen fixed (all scenarios)
  • The Titan’s barrier can be broken with the Elbesem Orb, so it can be defeated as in the Japanese version (Sc1 NA and PAL)
  • The mixed-up lines after the Catacombs (Sc1 battle 27) fixed. Basanda had an extra line in the PAL version that was removed. (Sc1 PAL)
  • Garosh bug fixed. This caused Garosh to lose stats instead of gaining when reaching levels 20-29 after his final promotion to Bow Master. (Sc3 and PD)
  • 60 Character bug fixed for the Premium Disc, previously if the gameshark was used to add Rogan, another character had to be removed. This fix allows all 60 characters without crashing. (PD)

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 patching 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 other virtual drive software if you prefer) to mount the .BIN (or .CUE) file and run with an emulator or burn the cue/bin to a disc to use in a modded Saturn.


Option 3 – Isomaker (Located in the SF3Patch directory)
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 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 NA or PAL version. It will not work correctly with the Japanese version. If you are patching a Scenario 1 PAL version, you will need to rename a couple of folders to get the PAL exclusive fix. Rename ‘SF3Patch\files\s1’ to ‘SF3Patch\files\s1 NA’ and then rename ‘SF3Patch\files\s1 PAL’ to ‘SF3Patch\files\s1’.

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 other virtual drive software if you prefer) to mount the .ISO (or .CUE) file and run with an emulator or burn the ISO/CUE to a disc to use in a modded Saturn.


Troubleshooting
If any 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 Option 2 or Option 3 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 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.