Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.1
Issue ID
1215632
Regression
No
[Rider Editor] Compiled shader code is marked for errors when opened in "Rider" editor
The compiled code of a shader is marked red in Rider editor when it has no issues at all
Steps To Reproduce:
1. Create a new Project
2. Project > Create > Shader > Unlit
3. Inspector > Compile and Show code
Expected Result: Compiled code looks error-free
Observed Result: Whole code is marked red and "}" expected message appears
Reproducible On: 2020.1.0a21, 2019.3.0f6, 2019.2.019f1
Checked with Rider package version: 1.2.1
Note: Rider editor wasn't available with 2019.1
Environment: Mac and Windows
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note:
Please report this bug with JetBrains then they will make sure this is handled, here is the link to their bug tracker: https://youtrack.jetbrains.com/issues/RIDER?q=Shaders