Xbox 360 Exclusive JRPGs on Xbox One

Given it wasn't a big player in Japan (or Asia in general), JRPGs that were only available on the Xbox 360 are quite a rare breed indeed. Even rarer, then, are those that are included in the list of backwards compatible titles for Xbox One.

Exclusives

The only 3 titles that I know tick both boxes (360 exclusive AND backwards compatible on the Xbox One) are:

Infinite Undiscovery

Infinite Undiscovery

Lost Odyssey and Blue Dragon enjoy reasonably high profiles, but I have a soft spot for Infinite Undiscovery. It seemed to mainly exist as a test game for the new Star Ocean engine but is an enjoyable fantasy JRPG with a solid cast and good battle system. It also features a New Game+ mode, which bumps up the difficulty.

Multi-platform Titles

Then there are a few more which are backwards compatible but are available on other platforms:

Star Ocean: The Last Hope

As an example, Star Ocean: The Last Hope (TLH) had a brief window of exclusivity (1 year, from memory) but then moved to PS3 and was updated as TLH "International". New features included Japanese or English audio and a choice of Anime-style or CG character portraits. TLH was later re-released on PS4 and Windows as a "4K & Full HD Remaster" edition.

Backwards compatible but also available on other platforms:




Not backwards compatible (but available on other platforms):

Eternal Sonata, known as Trusty Bell in Japan

There may well be a few I've missed - feel free to comment if that's the case.

 Here's the Wikipedia list of backwards compatible titles - as far as I can tell it's as up-to-date as the official list, but I find it easier to read-through.

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