Replies: 1 comment
-
|
Sorry for not responding in time.
What was the platform? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
EDIT: Resolved
The issue was that I did not put the slang.dll from v2025.19 in the binary folder, and I guess the application instead used the older slang.dll from the Vulkan SDK. A reminder for me to uninstall the VulkanSDK.
Original Question:
Hi,
I'm trying to compile shaders with the spvBindlessTextureNV capability, and this actually works using slangc:
slangc shader.slang -target spirv -capability spvBindlessTextureNV -emit-spirv-directly -fvk-use-entrypoint-name -source-embed-style u32 -source-embed-name shader_spv -o shaders.hHowever, I cannot get it to work with the compiler API, which always throws:
In both cases I'm using v2025.19.
I guess I have to use a command-line equivalent of
-capability spvBindlessTextureNVwhen using the compiler API, but I am a little lost on how to achieve this.Things I tried:
With the deprecated API
This gives me the unknown capability name error. cap0 to cap3 were attempts of finding the capability ID, but all of them return SLANG_CAPABILITY_UNKNOWN. For comparison, cap4 returns a valid number for a different capability.
With new API
Same error. id1 and id4 were again attempts to obtain the capability ID, but all of them return "unkown capability". Some of the docs seem to suggest that I should provide CompilerOptionName::Capability with an Int value of the CapabilityName enum, but I do not know how to obtain that integer value.
Thanks for any help!
Beta Was this translation helpful? Give feedback.
All reactions