Emulator Issues #9348
closed
DX12 (8947) - Texture corruption and crashes with custom texture loading enabled
0%
Description
Xenoblade Chronicles | SX4E01 | MD5: f6110ec667a19c22c0163902f7474e54 (GCZ compressed image) | Dolphin 64-bit, build 8947
DX12 renderer enabled: with custom textures enabled (latest version of HD texture pack) there's texture corruption on the title screen. Dolphin crashes upon attempting to load a savegame, when the title screen's background scene changes, and upon starting the game if "dump textures" enabled. Textures appear to load blurry, then sharpen and move up+left slightly as if the standard textures are loaded then replaced by the HD versions. I've attached a screenshot showing the texture corruption. I can't take a video since ShadowPlay doesn't seem to like DX12.
Reproduce by running Xenoblade Chronicles in DX12 mode with the HD texture pack enabled. OGL and normal D3D both work fine. I extensively tested other settings being enabled/disabled and none have any effect on the bug, including running in Interpreter and JITIL mode with all of the "safest" settings selected.
Windows 10 Professional, 64-bit
Asus Z97-A/USB3.1
GTX 970, driver version 361.82 (an official but optional hotfix that resolves the "unmount your GPU" tray icon bug in W10)
Intel i5-4690K
16GB RAM
Samsung 840 Evo 500GB SSD
[Anything else here]
-
On the title screen with custom textures preloaded, Dolphin's RAM usage is ~7475 MB in OGL and ~7425 MB in D3D, but ~7725 MB in DX12.
-
The glitchy texture moves in sync the fog/cloud textures.
-
In OGL mode with custom textures disabled and texture dumping enabled, only a few dozen textures are dumped from the title screen. One of the textures is an image of the monado, which has coloring consistent with the texture corruption.
-
As I mentioned earlier, a blurry version of textures appears to load at first and is then replaced with a sharper version. This does not happen in OGL or D3D mode.
I'm not a programmer so this is just wild speculation, but based on all this I wonder if the standard textures and the custom textures are both being loaded, with the standard textures (partially?) overwriting the custom textures in RAM. This would explain the issues I'm experiencing and sounds similar to a bug I remember reading about in the monthly progress reports a while ago, where textures would overwrite each other in RAM.
Files
Updated by 
Updated by 
Updated by 
