CoreValidation-Shader-InconsistentSpirv error

steamclosed overlay

ValveSoftware/steam-for-linux#6626 · opened 2019-10-29 by baryluk · updated 2022-04-22 · 6 comments · github

Bbaryluk 2019-10-29 github

When I run steam itself with Vulkan validation layer on I got these two validation errors:

Fossilize INFO: Overriding serialization path: "/home/user/.local/share/Steam/shader_cache_temp_dir_vk_64/fozpipelinesv4/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/home/user/.local/share/Steam/shader_cache_temp_dir_vk_64/fozpipelinesv4/steamapprun_pipeline_cache".
UNASSIGNED-CoreValidation-Shader-InconsistentSpirv(ERROR / SPEC):
msgNum: 0 - SPIR-V module not valid:
Vulkan spec doesn't allow BuiltIn VertexId/InstanceId to be used.
  %gl_VertexID = OpVariable %_ptr_Input_int Input

    Objects: 1
        [0] 0, type: 0, name: NULL
UNASSIGNED-CoreValidation-Shader-InconsistentSpirv(ERROR / SPEC):
msgNum: 0 - SPIR-V module not valid:
In the Vulkan environment, the OriginLowerLeft execution mode must not be used.
  OpExecutionMode %main OriginLowerLeft

    Objects: 1
        [0] 0, type: 0, name: NULL

~~I am not sure which version of the fossilize layer I have as it is bundled with steam. I am using Steam Beta at the moment.~~ EDIT: This is not related to fossilize.

$ file /home/user/.local/share/Steam/ubuntu12_64/libVkLayer_steam_fossilize.so
/home/user/.local/share/Steam/ubuntu12_64/libVkLayer_steam_fossilize.so:
ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, 
BuildID[sha1]=eca99a8c74a4aed651a44d812fb67c0f770765a9, not stripped

Linux Debian testing amd64

HHansKristian-Work 2019-10-30 github

I don't think this is a Fossilize issue, but a Steam issue. The "Fossilize INFO" there means the Fossilize layer has been initialized, but it's not issuing any Vulkan calls, so I don't see how it could cause validation errors.

Ddanginsburg 2019-10-30 github

Does this happen when launching a game or the Steam client itself? I wonder if this could be the shaders in the Steam Overlay needing to be regenerated with a new glslang. @Plagman

Bbaryluk 2019-10-30 github

I think you are right, it might be the issue with the Steam not fossilize. Let me retry with fossilize completely disabled / removed.

Bbaryluk 2019-10-30 github

Indeed I am getting same error message with: VK_LOADER_DEBUG=all VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation DISABLE_VK_LAYER_VALVE_steam_fossilize_1=1 steam

Not a fossilize layer issue. Sorry about that.

Kkisak-valve maintainer 2022-04-01 github

Hello @baryluk, are you still experiencing this issue on an up to date system?

Bbaryluk 2022-04-22 github

Cannot reproduce the issue anymore. Closing.

Nothing extracted yet.