-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separable samplers #693
Separable samplers #693
Conversation
Its necessary for us to ignore the sampler as well, because otherwise we write it into the lifetime tracking of the pool. |
I'll see when it gets lifetime tracked then and have it be ignored at that point |
version increase behaviour, corrected some logger messages
creation for the former has some new validation
btw your dxc submodule is not inline with the one on |
processing passes
…mortized_lookups. Also cleanup + AoS changes for amortized lookups
…ge_sampler_amortized_lookups Separable image sampler amortized lookups
Description
Writing the necessary stuff so that we can have decoupled image/samplers in bindings
Testing
I changed example 07 a little bit and it runs normally. If you remove the sampler from the equation it doesn't forward any to the vk write
TODO list:
If you still provide a sampler in the DescWrite, it will be forwarded to Vulkan (the current way stuff works is that if the type's category is image and you provide samplers, they will be sent). I think this is not an issue because if the
VkDescriptorType
of the write isVK_SAMPLED_IMAGE
the samplers of the image info are ignored. However it makes no sense to give samplers to an image info for a sampled image descriptor. If necessary I can make it generate a warning or fail