Closed Dynamitos closed 2 months ago
Everything inside a type that implements an interface and used to specialize a shader in a way that affects shader parameter layout must be ordinary data types, i.e. they must not contain opaque resource types. This is a limitation of the language and we don't have plans to support it due to the complexity it introduces to binding models and reflection API. You need to implement some sort of bindless mechanism and stick to pure data types with different material implementations.
I am trying to compile the following example using the C++ API:
The C++ code used to reproduce the error is as follows:
This error occured with the latest tagged release version v2024.1.10. What I could gather from the debugger, the problem is that the texture and sampler are passed to the function via a BitCast to Uint64, which it is unable to properly generate into code.