Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X
Votes
0
Found in
2021.2
2022.1
Issue ID
1364139
Regression
No
SHADER_AVAILABLE_XXX defines are not set in compute shaders
SHADER_AVAILABLE_XXX does not seem to be set for compute shaders
Our specific use case is with VFX Graph where we have a shared include that uses SHADER_AVAILABLE_CUBEMAPARRAY. It works fine with regular shaders but fails to compile with compute as soon as we're using some cube map arrays because SHADER_AVAILABLE_CUBEMAPARRAY is never set.
I made a workaround for the moment (by always defining SHADER_AVAILABLE_CUBEMAPARRAY in our generated compute) but would be nice if this was handled correctly at some point.
PR of the workaround: https://github.com/Unity-Technologies/Graphics/pull/5582
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2022.1):
The SHADER_AVAILABLE_XXX defines should now exist in compute shaders.