Incorrect Texture Dimension behaviour on shadows on Intel Iris Xe under Vulkan
Validation
- [x] I have checked the Issues page to see if my problem has already been reported
- [x] I have confirmed that this bug does not occur in the original game running on original Xbox 360 hardware
If you have DLC installed, please specify which ones you have.
- [x] Apotos & Shamar Adventure Pack
- [x] Chun-nan Adventure Pack
- [x] Empire City & Adabat Adventure Pack
- [x] Holoska Adventure Pack
- [x] Mazuri Adventure Pack
- [x] Spagonia Adventure Pack
If you have mods enabled, please specify which ones you have.
No response
If you have codes enabled, please specify which ones you have.
No response
Describe the Bug
Shadows look really weird after the update 1.0.3. I've turned off all the mods and codes, checked the files, checked the game in original hardware and emulation.
Steps to Reproduce
- Just open the game with an Intel Integrated GPU
- Look at the shadows, whatever you try to fix it by changing the settings, it just stays like that.
Expected Behavior
Normal Shadows, each setting to it's specific resolution, for me, it's just stuck to that resolution.
Footage
System Specifications
CPU: Intel i5-1135g7 GPU: Intel Iris Xe G7 80EUs GPU Driver: Intel Graphics Driver 32.0.101.6651 (Latest) OS: Windows 10 Home Version: 1.0.3
Additional Context
This only happened when i updated from 1.0.2 to 1.0.3. I've checked all my drivers, updates and everything is fine. When i go to 1.0.3 it does just that. My current preset is: 1280x720p Original Shadows No Anti-Aliasing
Apparently texture dimension instructions are just broken on Iris GPUs and it'll need a workaround to embed texture dimensions instead in uniform data rather than relying on the HLSL method.
You were probably defaulted to D3D12 in 1.0.2 and just got switched to the new default, Vulkan, in 1.0.3. You can try checking with F1 in both versions and see if that's the case. It may be the bug only shows up in one backend or the other, but D3D12 was phased out for Intel due to the multiple other issues these GPUs seem to have with it.
You can also just try force-enabling this through the config.toml file.
Okay, i'll check on it, thanks!
Both versions show the issue on Vulkan backend. I've just checked it. The past version, 1.0.2, like i said, the shadows were normal because of the D3D12 backend.
UPDATE! I'm on another laptop, with the same GPU and CPU, using Vulkan, and the problem seems to be nowhere found, it's a driver issue or the transition between versions, i've made a fresh install in the other laptop i'm currently using, and the shadow is normal.