(new to this forum, i've read the rules and FAQ, i think this is the right spot to post this on, if this is the wrong spot, please move this thread to where it belongs)
I tried launching Xenoblade Chronicles earlier today, with the build 5.0-3973, using Vulcan backend, SSAA 2x, 3x Resolution and HD textures. I've been playing this game for a while with this build(about 40-50 hours)
There were a quite a few framedrops during battles, so i stopped the game, lowered the resolution to 2x and it just wouldn't load. Sooner or later, it did load. But all I saw was a really zoomed in version of the title screen.
I thought that it might've been a bug with the build i used, so I updated to the build 5.0-4889, with the same settings, and it just crashed the emulator by instant.
I tried to disable the textures, and then the game worked again. I also tried to enable custom textures again, but this time with Direct3D and OpenGL, and both worked.
I thought that it might've something to do with the ram, but i couldn't prove it like this, I thought, so I went all the way back to the stable release of dolphin 5.0, trying Direct3D 12, and I checked the ram usage from the task manager, and it went up to 6 GB on dolphin alone before the emu noticed me that it failed to load the textures(The textures are ~1.35GB btw). I tried to load the game once more on the build 5.0-4889 again with the same settings as I originally had, except for that i used 2x resolution intstead. The ram went up to ~1.7GB before it crashed or "stopped working" as windows likes to call it.
My conclusion is that Vulcan seems to eat RAM while using custom textures, which is obvious, but not just the ammount it needs, but way more than it should, therefor it crashes due to not having enough ram, which is funny, because on the stable release(with D3D12) it doesn't crash, just ignore the textures and clear them from the RAM(I saw the ram usage shrink to mere 300-400 MB)
TL;DR: Xenoblade + Vulcan + Custom textures + Prefetch Textures = crash on load using the latest build, for me.
Btw using prefetch textures all the time except for those times i told that i disabled custom textures.
I tried launching Xenoblade Chronicles earlier today, with the build 5.0-3973, using Vulcan backend, SSAA 2x, 3x Resolution and HD textures. I've been playing this game for a while with this build(about 40-50 hours)
There were a quite a few framedrops during battles, so i stopped the game, lowered the resolution to 2x and it just wouldn't load. Sooner or later, it did load. But all I saw was a really zoomed in version of the title screen.
I thought that it might've been a bug with the build i used, so I updated to the build 5.0-4889, with the same settings, and it just crashed the emulator by instant.
I tried to disable the textures, and then the game worked again. I also tried to enable custom textures again, but this time with Direct3D and OpenGL, and both worked.
I thought that it might've something to do with the ram, but i couldn't prove it like this, I thought, so I went all the way back to the stable release of dolphin 5.0, trying Direct3D 12, and I checked the ram usage from the task manager, and it went up to 6 GB on dolphin alone before the emu noticed me that it failed to load the textures(The textures are ~1.35GB btw). I tried to load the game once more on the build 5.0-4889 again with the same settings as I originally had, except for that i used 2x resolution intstead. The ram went up to ~1.7GB before it crashed or "stopped working" as windows likes to call it.
My conclusion is that Vulcan seems to eat RAM while using custom textures, which is obvious, but not just the ammount it needs, but way more than it should, therefor it crashes due to not having enough ram, which is funny, because on the stable release(with D3D12) it doesn't crash, just ignore the textures and clear them from the RAM(I saw the ram usage shrink to mere 300-400 MB)
TL;DR: Xenoblade + Vulcan + Custom textures + Prefetch Textures = crash on load using the latest build, for me.
Btw using prefetch textures all the time except for those times i told that i disabled custom textures.