Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2020.3.44f1
2021.3.16f1
2022.2.2f1
2023.1.0a25
Issue ID
UUM-22521
Regression
No
Compute shaders fail to compile when keywords are declared in a separate include-file
How to reproduce:
1. Open any project or create a new one
2. Import the attached “Compute Shader Keywords“
3. Select the “ComputeShader2” Compute Shader
Expected result: The “ComputeShader2” Compute Shader is compiled
Actual result: “Program 'CSMain', error X3084: 'numthreads(X,Y,Z)' attribute expected, where 'X,Y,Z' are the dimensions of the thread group at kernel CSMain“ error in the Inspector of “ComputeShader2” Compute Shader
Reproducible with: 2020.3.44f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
Reproduced on: macOS 13.0.1 (Intel)
Note: The error goes away when reopening the project
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
`#pragma` directives are only taken from files included using `#include_with_pragmas`, not regular `#include` directives.
Resolution Note (2023.1.X):
`#pragma` directives are only taken from files included using `#include_with_pragmas`, not regular `#include` directives.