Open thesymbol opened 9 years ago
xenia-project/xenia#1382
Hi! I'm having a trouble with the game, the game crash and generate a folder called "scratch"... I'll give you the file you're finding in the subfolder "gpu", I think you can examine it and find a solution.
Specs 2700x GTX 970 8x2 GB Ram 2400Mhz Windows 10 Last Version (1903)
Currently testing Halo 3 and constantly having crashing after a certain amount of play. I find levels which have more going on cause the crash to happen more times than none. I do have a 1.53GB crash report which I can quite happy to share. Not to sure how I can send this massive file though?
I don't have a folder called "scratch" though. Specs: i7-6700k, 64GB RAM, GTX 980M, Win 10 - 1903
@CloudFR No. Stop spamming.
Requires GPU>CPU resolve readback for eye adaptation to brightness (but even without it, the screen is not overly bright/dark).
Tested on https://github.com/xenia-project/xenia/commit/06AB8589
You can finally complete the 1st mission of Halo 3 without crashing. Originally it would crash once you met Johnson on older Xenia builds, but after the changes Rick implemented involving KeSetCurrentStackPointers, now it no longer crashes. The 2nd mission is also fully completable. Given you have all the shaders cached 1st of course.
To be honest any log that I'd show here with me completing the entire mission would be way to huge in size. So here's one of me loading in-game on the mission Tsavo Highway, but exiting it after 3 seconds in-game. Actual size is 516MB's xenia.zip
Ryzen 3600 2x8GB 3600MHz GTX 1070
The Halo 3 08172 'delta' build that was recently released works fine after a few small changes. (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...)
For it to start loading some XBDM exports needed their return values changed:
DmRegisterCommandProcessorEx: 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.
DmWalkLoadedModules: 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.
(I've made a branch with the XBDM changes needed here: https://github.com/emoose/xenia/commit/78b459a8db83100ca7edd26dc441a154868e2aaf, unsure about PRing though since there might be reasons these had the values they did...)
Besides those there's also missing NtReadFileScatter & XeCryptBnQwNeRsaPubCrypt exports that the game needs to start loading, (EDIT: these have now been added to xenia-master!)
In addition cache:\ needs to be mounted for the game to load, currently xenia only mounts cache0/cache1 though, so another small change is needed: https://github.com/xenia-project/xenia/pull/1664
With all the linked branches merged together, and mount_cache = true
inside xenia.config.toml, hopefully the halo3_cache_debug/release.xex should run fine for you!
This can be marked as playable. I've completed the game without any major issues. There were some minor graphical issues like light effects shining through objects and footsteps not rendering correctly but it didn't distract from the gameplay. Performance wise it rarely went below 26FPS, most of the time at 28 to 30. When new level sections load during gameplay the emulator freezed for a second or two but then went on as normal when the load was complete. No crashes and all cutscenes played perfectly as well.
System: i7 7700K GTX 970 16GB DDR4 3000MHz
Tested on master@c4eae232f (Apr 2 2022) build from a blank save. While the DX12 renderer works fine, on Vulkan (or at least Vulkan combined with Win 7) the opening videos and main menu are inivisible and the opening cutscene soon crashes after the dialog commenting on how far Master Chief fell. The cutscene is also filled with numerous graphical rainbow artefacts.
PC Specs: Windows 7 SP1 Professional Intel Core i3-6100 AMD Radeon Pro WX3100 8GB DDR3
Retested on master@7ab5ccbbd (May 3 2022) with the same results (not unexpected as virtually no changes to the Vulkan code in this time) but this time with a RenderDoc capture on the (invisible) main menu. The capture from the arrival cutscene is 281MB and too large to upload even compressed.
is the game's fps tied to the physics or not? I was just wondering because I want to play the campaign at 60 fps
Yes, otherwise it wouldn't have the vsync-off-speedup
tag.
Xenia Canary issue: https://github.com/xenia-canary/game-compatibility/issues/214
i am have a problem with it i getting the bad io files error on this game and on halo reach and i cant find a way to fix it
Marketplace
Tested on https://github.com/xenia-project/xenia/commit/068b2056ca02a707b164693fefc9e0dd9637e6f2
Log:
https://gist.github.com/thesymbol/aa2e7305fde89c4a57be
Issues:
Screenshots: