Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.2.0b3
Issue ID
716053
Regression
No
Shader Render Queue Changes doesn't properly reflect in Material m_CustomRenderQueue property
To reproduce:
1.Create new project, import attached "CustomShader.shader" file.
2.Change project settings in Project Settings > Editor > Asset Serialization > Force Text.
3.Create new material from imported shader.
4.In text editor open "CustomShader.shader" and change line 9 to:
Tags { "Queue"="Transparent" "RenderType"="Transparent" }
5.Open created material in text editor, notice m_CustomRenderQueue value is set to 2000, which is wrong render queue.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Add comment