Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b6
2023.1.0a8
2023.2.0a1
Issue ID
UUM-12420
Regression
No
Color doesn't appear in Realtime Global Illumination Albedo Draw Mode when it's passed using the SetPropertyBlock method with an index parameter
Reproduction steps:
- Open the attached project
- Open the “/Assets/Scene.unity” Scene
- Change the Draw Mode to Shaded under Shading Mode in the Scene View
- Observe the colors of the cubes in the Scene View
- Change the Draw Mode to Albedo under Realtime Global Illumination in the Scene View
- Observe the colors of the cubes in the Scene View
Expected result: the “Cube_Indexed” GameObject is red when the Scene View Draw Mode is Albedo
Actual result: the “Cube_Indexed” GameObject is black when the Scene View Draw Mode is Albedo
Reproducible with: 2020.3.39f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a8
Reproducible on: Windows 10 (21H2)
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
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
- Look Dev window flickers when resizing the window after docking it
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue is not legitimate, but instead that we are not able to prioritize the fix, at this time.
Please note that this decision is weighed against our other priorities, including delivering new features and ensuring that our core functionality is stable.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue is not legitimate, but instead that we are not able to prioritize the fix, at this time.
Please note that this decision is weighed against our other priorities, including delivering new features and ensuring that our core functionality is stable.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.