Crash observed on Ubuntu 22.04 with AMD Vulkan driver

[lukelmy]

This crash happened after I clicked on new game and loading.

I have dumped API and related spirv shaders.
After investigation, I think the root cause is that the problematic fragment shader uses "layout(set = 1, binding = 168) uniform samplerBuffer ********ProvinceDataBuffer" which is not set in the corresponding pipeline layout (the largest binding count is 167 in the pipeline layout), thus the driver could not identify this descriptor during shader compiling.

The vertex shader and problematic fragment shader and corresponding pipeline layout are attached.
If you would like to confirm it with API dump, I suggest you could dump API with RADV (since it crashes with AMDVLK and the dump info is incomplete) and find the specific pipeline layout with the size of shader module. (size of shader module -> graphics pipeline -> pipeline layout)

Please let me know if you have any questions.

Thanks!

System info:
Operating System : Ubuntu 22.04
CPU : Ryzen7 5800X3D
RAM : 64 GB
ASIC : Radeon 7900XTX
Base : AMD Pro driver

 

[AndrewT]

I think you are saying this is a game bug in the Linux edition, is that right?
If so you are best off posting in the Bug Reports forum here.

If however you are saying this is a problem with that AMD driver, please report it to them. Hopefully reverting to an older driver helps that?

 

[lukelmy]

I think it's a game bug which uses a descriptor in the fragment shader while the descriptor is not set in the pipeline layout.
And it's a bug in Vulkan edition. (both Windows and Linux)

I understand that maybe this issue is not observed with other graphics drivers. But it still should be fixed on the game side.

Report files are attached.

 

[AndrewT]

I think it's a game bug which uses a descriptor in the fragment shader while the descriptor is not set in the pipeline layout.

Thanks, then please make a new post in Bug Reports here, and attach the files QA will need to look into this.

Did reverting the AMD driver help?

And it's a bug in Vulkan edition. (both Windows and Linux)

FYI Vulkan is not supported under Windows, it is just there for diagnostic purposes. And only Vulkan is supported in Linux (and MacOS)! So there is no separate "Vulkan edition" for either game.

 

[lukelmy]

Thanks, then please make a new post in Bug Reports here, and attach the files QA will need to look into this.

Thanks, I will do it.

Did reverting the AMD driver help?

We have tried with older driver and it still crashes.
IMO, it seems like a game regression since it could work earlier this year.

FYI Vulkan is not supported under Windows, it is just there for diagnostic purposes. And only Vulkan is supported in Linux (and MacOS)! So there is no separate "Vulkan edition" for either game.

We have tried to launch with "-vulkan" under Windows and observed same issue. And no issue with default launch option (maybe using DirectX).
Thus I guess it‘s launched with Vulkan...
And I am probably wrong