![halo 3 xenia halo 3 xenia](https://user-images.githubusercontent.com/39768033/40741214-dc654466-6442-11e8-8d31-db9051ed229f.png)
#Halo 3 xenia code
(title ID is the same so I posted it here, maybe should have its own issue though since this build is from months before the retail one, even earlier than the Halo 3 beta.)įor it to start loading some XBDM exports needed their return values changed:ĭmRegisterCommandProcessorEx: right now it's defined via MAKE_DUMMY_STUB_STATUS which makes it return an error code, unfortunately H3 debug requires this to return success for it to continue loading.ĭmWalkLoadedModules: returns X_STATUS_INVALID_PARAMETER atm, but H3 has a while(DmWalkLoadedModules() != 0x82DA0104) loop which will keep looping forever since we don't return the code it's looking for, changing it to return that code lets it break out of that and continue loading. The Halo 3 08172 'delta' build that was recently released works fine after a few small changes. So this leads me to believe that a new profile is being generated each start, and therefore maybe why the last profile isn't shown when starting the game again. I'm also noticing that each time I start the game, start a mission, then save & exit a new profile is created in the content\4D5307E6\00000001 directory. Either way Xenia is creating a file instead of a directory in cache1 I do not know what this file really is for. temp ext was created inside that autosave folder (as I hit a checkpoint I guess) I analyzed it with HxD to find BLF mentioned in the header and strings about what map I've progressed through. (FWIW I don't expect this to work) Now, Halo tries to check if an autosave folder exists in cache1, this fails and creates a file for some reason, when I deleted the file and created a folder, a new file with the.
![halo 3 xenia halo 3 xenia](https://i.ytimg.com/vi/Obx4HFawrhc/maxresdefault.jpg)
first I enabled the cache0 and cache1, also I created an entry for /Device/Harddisk0 the same way that scratch, cache0, and cache1 are done.