Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X
Won't Fix in 5.5.X
Votes
0
Found in
5.5.0b5
Issue ID
841236
Regression
No
[Projector] Setting projector's render queue in runtime doesn't change actual render queue
Steps to reproduce:
1. Open attached project
2. Open scene "Bug" and run it
3. Notice 4 spheres in the scene. Top-left one is purple while top-right is black. Both bottom ones are black. The problem here is that bottom-left one has same render queue value as top one so they should look the same
Actual result: projector material's render queue doesn't change unless projector is disabled and re-enabled
Expected: projector material's render queue changes without need to re-enable it
Workaround: Disable and enable projector
Reproduced with: 5.3.6p7, 5.4.2f1, 5.5.0b7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Add comment