Do I reuse pipeline layout for shader objects in Vulkan?

Question

I noticed that in the new Vulkan spec, Render Pass objects are obsoleted in favor of the newer Render Pass instance. And there's a newer mechanism to compile and use shaders: Shader objects - which can be used directly; while the older Shader modules aren't obsoleted yet - which is used with pipeline objects.

But I find no mention of newer mechanism of using descriptors (and its sets and pools) with shader objects. I did a Ctrl-F over the Resource Descriptor page, there's no exact full-match for VkPipeline - Suggesting the same set of interfaces are directly applicable to shader objects?

So what's the real story here?

Nicol Bolas · Accepted Answer · 2025-05-09 17:06:10Z

1

VK_EXT_shader_objects is an extension, not core functionality.

If you look at what it takes to create a shader object, you'll find that VkShaderCreateInfoEXT has parameters that are suspiciously similar to those of VkPipelineLayoutCreateInfo. An array of VkDescriptorSetLayouts, and an array of VkPushConstantRanges.

Shader objects use the same descriptor (and push-constant) functionality for accessing resources as pipelines. The only difference is that shader objects aren't bound to pipeline state the way shaders in pipeline objects are.

answered May 9 at 17:06

Nicol Bolas

482k66 gold badges862 silver badges1.1k bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

DannyNiu May 16 at 4:37

I'm aware that it's an extension. I'm also aware that many extension are promoted to cores of future revisions or KHRs over time; also that vender drivers can implement new extensions should their (old) hardware has the capability to support that. Therefore I'm willing to try this.

Collectives™ on Stack Overflow

Do I reuse pipeline layout for shader objects in Vulkan?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related