Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.3f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1170548
Regression
No
Shader RenderQueue changes are not reflected on Projectors when RenderQueue is edited in the inspector
How to reproduce:
1. Open the attached project ("case_1170548-projector-render-queue")
2. Open the repro scene ("SampleScene")
3. Select "sky" material in the Project tab
4. Change the "Render Queue" value to be greater than 3000
5. Save the change and see that scene view hasn't changed
6. Select the "sky" game object
7. Disable and then re-enable the "Projector" component
8. Inspect that the scene view has updated
Expected results: RenderQueue changes are reflected on Projectors when RenderQueue
Actual results: RenderQueue changes are not reflected on Projectors when RenderQueue until the scene is updated
Reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0b10, 2019.3.0a10
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Projector is a system not supported in SRP and as there is a valid workaround (enable / disable the projector component) we will not be investing in a real fix.