yuzu
yuzu copied to clipboard
Xenoblade Chronicles DE Extra Story: Complete emulator crash after certain point
During the Extra Story, around the end of it, any time I try to watch the cutscene in question or even skip past it, the emulator will freeze, seemingly dying during trying to compile a shader. Afterwards, all proceeding launches of the game will fail trying to compile the end of the shader cache, presumingly due to a corrupted entry in the cache
Save file is attached, repro is:
- Launch game with saves in correct location
- Go to Extra Story at bottom of main menu
- Load the save the cursor should default to, if not I believe its the top one, its in Alcamoth standing near a teleporter
- Go into teleporter and accept path of no return prompt
- Try to watch cutscene or skip past it, emulator crashes instead of proceeding and last log entry is a half-written shader compile log entry and shader cache is 9/10 times corrupted so that launches without first deleting the cache fail
Log: yuzu_log.txt
Save: 0100FF500E34A000.zip
WinDbg Output:
Try gpu accuracy normal and high
Tried Normal, High, and Extreme, all have the same result unfortunately
Issue caused by Vulkan, use OpenGL to get past cutscene until it's fixed.
Will try later today after I get back from work and let you know if that fixes it, thanks
~~I don't know what changes were made, but now the game crashes on OpenGL as well, so is no longer possible to play through this part (tested with yuzu 1110).~~
Nevermind, is caused by the new AMD drivers.
So has anyone an idea of how to fix this?
Just gonna have to wait until AMD gets their shiz together and fixes the driver, or wait until someone gets around to implementing a workaround if possible unfortunately
So has anyone an idea of how to fix this?
Play it on Switch until yuzu optimizes their code for AMD, is currently not possible to finish this game on AMD, it crashes with both OpenGL and Vulkan.
Seems the issue on this page has migrated hard to Xenoblade 3 (Vulkan is pretty much crashing on all cutscenes). If you supply logs will help the team pinpointing the issue.