4D5308C5 - Mass Effect 2 Importer

[emoose]

Marketplace ("Unreap.xex" included with ME2)

Tested on xenia-project/xenia@ea9625f

Issues:

XEX is named "Unreap.xex", normally gets launched by ME2's default.xex, but Xenia can't restart into another XEX atm.

Running it directly results in a "gamer profile changed, exiting to menu" message, but despite that message it actually seems to be caused by launch-data from default.xex not being set when the XEX is ran directly.
Seems to expect launch data of the form " -expectuser0.177.62.186.190.186.190.186.190" (with a leading space character), and the launch-data buffer needs exactly 1000 bytes allocated.

With that launch data set it'll now load up "properly", shows a save-game list but doesn't actually seem able to detect any ME1 saves right now.

Strangely, it doesn't seem to use XamContentAggregate or any XamContent*Internal functions anywhere in the XEX (like Banjo-Kazooie uses for loading Banjo-Tooie saves), instead it seems to use XamContentCreateEnumerator, with content-type 0x3 / XContentType::Publisher.
Maybe this is a special content-type that allows enumerating savegames from other titles with the same publisher? Maybe based on title id, with ME1 being 4D5307E8, this could explain why the importer is 4D5308C5 while ME2 itself is 454108CE.

(I don't really get how XamContentCreateEnumerator would be able to return things from other titles though, since XCONTENT_DATA enumerated by it doesn't include any title ID...)

Unfortunately haven't had any success getting it to detect any ME1 saves, could be something to do with STFS headers being missing (I've only tested with master's STFS code), or maybe the ME1 save I'm testing with isn't complete enough to be imported by ME2.

Log:

xenia.zip (with launch data set)

Screenshot(s):

Labels:

kernel-save-file-errors
kernel-unimplemented-feature
kernel-xex-switching
state-load

[Sowa95]

No changes since last report.
Importer works on Canary through launch_data feature. xenia-canary#264

Outdated

Tested on: xenia-canary/xenia-canary@0c9ba87
Forgive me for Canary, it's easier to get it going thanks to launch_data feature. And it probably needs correct ME1 save, fixed in 74b5271.

After completing ME1, new save will be created in 4D5307E8/00000003, along with its header. With expected launch_data set for unreap.xex it still won't detect any saves. However, it's possible to trick this thing. ME1 save has to be placed inside unreap.xex content folder (4D5308C5), like so:

After launching unreap.xex again, ME1 save is detected with correct stats, but when selected, nothing really happens. "Normal" game is resumed through default.xex, and it continues to run like importing never happened. That being said, new launch_data for unreap.xex will be generated (also with 1000 bytes buffer). Parameters are correct, but they have to be used on default.xex instead:
BioP_ProNor -importstartupmovies -legacydataready -autodevice1 -expectuser0

So now with ME1 save located in unreap.xex content folder and correct launch_data for unreap.xex and default.xex in place, Xenia will have no issues importing.

If anyone wants to try it out:
ME1_save.zip
launch_data_for_unreap.xex_and_default.xex.zip