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
- 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
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
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