Multitude Fantasy - Final Comparison

Compare the pair (and more)

So many versions/ports/translations of Final Fantasy VI, which leads to the inevitable question: which is the version to spend 60 hours playing through?

It's a question that's been asked all over the net with as many opinions as there are interested gamers. It can actually be quite fascinating, there are comparisons based on translation, looks, censorship (or the lack thereof), nostalgia, system of choice, and more.

As an aside, The Legends of Localization site has a wonderful breakdown and comparison of the different translations (complete with video), and is well worth having a look through.

It's certainly not a choice I've been able to make 100%, but I have ended up settling on a SNES play-through using the (admittedly flawed) RPGOne re-translation. I've also sunk a lot of hours into (but not completed) the GBA and PSX ports. The GBA is (IMHO) the best of the official ports, but it does require some patching to restore the original music and to lower the brightness (raised for the GBA screen).

 First up, the SNES version - or, more accurately, the Super Famicom version patched with the RPGOne translation (v1.2) plus other fixes. Screenshots below from mednafen, with hq4x scaler and smoothing applied:







Next up, the patched GBA port:


 




 Finally, the PSX version:





So, for the moment at least, I'll probably persevere with the SNES/RPGOne version for this play-though but I'm also very tempted to keep up with the GBA version of switch over completely.  

Comments

Post a Comment

Popular posts from this blog

Change the ComputerName value in Unattend.xml using PowerShell

A quick and dirty PowerShell script to update the value of ComputerName in Unattend.xml before imaging. This particular value is located at: <unattend>  <settings pass="generalize">   <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">     <computername> Which is a bit of a mouthful, but we can be lazy and just pull the value from the nth component node (in my case it's 3, or the 4th component node). PowerShell uses dots to describe the hierarchical path, which looks a lot neater than the above: $xml.unattend.settings.component[3].computername To repeat, the value of .component[n] will change depending on the structure of the file. The value of the...
Read more

Testing out Link Aggregation

Image
I picked up a TP-Link managed switch last week as something of a compromise between affordability and features - as it turns out though, it does just about everything I could ask for, just without the extra expense from buying something that has HP or Cisco written on the side. I grabbed the TL-SG3216, a fanless L2 managed switch with 16x1Gigabit ports as it ticked all the boxes: Silent (fanless) Managed Link Aggregation/802.3ad (LACP) 802.1Q (VLAN) STP As a bonus, the CLI interface (via console cable or ssh) is very similar to Cisco's IOS, so I don't have to learn an entirely new syntax to configure it. Before I replace my existing switch, I spent a bit of time testing out its features. First up, I setup a spare Raspberry Pi with a second ethernet interface (via a USB dongle) to test out link aggregation. First up, the configuration on the Pi (Raspbian): Install ifenslave to allow for the creation of bonded network interfaces # apt-get install ifenslav...
Read more

Adding 802.1Q Trunking to Debian GNU/Linux

Here's a quick guide to setting up 802.1Q trunking for VLANs on a Debian GNU/Linux box connected to one or more Cisco Catalyst switches, which could then be used as a cheap router replacement. Configuration on the Debian box: Add 8021q to /etc/modules so 802.1Q support is enabled at startup. To install it immediately: # modprobe 8021q Use vconfig to add the VLANs to the interface you'll be using (if vconfig is missing, run apt-get install vlan ): # vconfig add eth0 2 (In the above, eth0 is the physical interface and 2 is the ID of the VLAN) Give the interface an IP. Choose an address in the range you've set aside for that particular VLAN. In this example, VLAN 2 is using 192.168.2.0/24. # ifconfig eth0.2 192.168.2.201 netmask 255.255.255.0
Read more