Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
2
Found in
2019.4
2019.4.14f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1358042
Regression
No
Shader compilation error is thrown when #pragma target is set to 3.0 or higher
How to reproduce:
1. Open the attached project "1358042.zip"
2. Select the "TestShader" Shader in the Assets folder
3. In the Inspector press on the Open in Shader Editor button
4. In Rendering Options, turn off LOD Group Cross Fade Option
5. Turn the LOD Group Cross Fade Option on again
6. Save the settings
7. Open the Console
Expected reesult: Warning is not thrown when #pragma target 3.0 is already set in code
Actual result: Even though the target is set to 3.0 or higher the warning is thrown
Reproducible with: 2019.4.29f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a5
Note:
* 2021.2 and 2022.1 streams show the error in the Inspector when selecting the shader
* Warning thrown: "Automatically setting target of LOD_FADE_CROSSFADE to 3.0"
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b1
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.9f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.27f1