Nighterlev
commented
3 years ago Tested on xenia-project/xenia@9a74df49
Issues:
Goes in-game, most likely went in-game as soon as Gibbed added in KeSetCurrentStackPointers into Xenia which allowed Halo Wars 1 to finally go in-game as well (just like how it stopped Halo 4 crashing in cut scenes, or certain Halo 3/Reach loading segments causing hard crashes with Xenia itself).
Screenshots:
More Screenshots
    Issues:
state-gameplay
Etokapa
Marketplace
Tested on https://github.com/xenia-project/xenia/commit/fd18a97f3a13d1394872b83f4fce285cf1c5133e
Issues:
Exactly the same as the main game, but provides a different intro screen. Both of them seem to have issues with either guest crashing, host crashing Xenia upon booting, or completely hanging. Errors: !> F8000204 XMA: Read from unhandled register (0600, CONTEXT_ARRAY_ADDRESS) !> F800023C XMA: Write to unknown register (0601): 00000002 !> F800023C XMA: Write to unknown register (0601): 00000003
Warnings: w> F8000004 GPU: Write to unknown register (0081 = 80010000) w> F8000004 GPU: Write to unknown register (0082 = 00000000) w> F8000004 GPU: Write to unknown register (1E4E = 00000000)
Log:
log level set to 3, cache mounted, scratch mounted. xenia.log
Screenshot(s):
Labels:
cpu-unimplemented-instruction state-crash-guest or state-intro tech-engine-Halo Wars particle engine (not sure if this is worth it to create another label for as it only apples to HW, managed to get a name for it from here https://richg42.blogspot.com/2016/11/another-little-note-about-halo-wars.html )