Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2020.2
2021.1
2021.2
Issue ID
1306556
Regression
No
Using a SamplerState associated with a Texture, without using the Texture itself results in an error
Reproduction steps:
1. Open attached project "ShaderTest"
2. In Project window, select Assets/TestSamplerState.shader
3. In Inspector window, observe error
4. If there is no error, in Inspector window, press "Compile and show code" button
Expected result: No errors
Actual result: " Fragment program 'frag': Unrecognized sampler 'samplertexture1'" error
Reproducible with: 2018.4.31f1, 2019.4.18f1, 2020.2.2f1, 2021.1.0b3, 2021.2.0a2
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (2021.2.X):
When a texture is stripped from the shader (which happens to unused textures), it's not present in the reflection data, and we have no way of knowing how to configure things.