Search Issue Tracker
Fixed
Fixed in 2023.1.0a23
Votes
0
Found in
2023.1.0a13
Issue ID
UUM-16057
Regression
Yes
commandBuffer.SetRenderTarget will only bind the first slice when sliceID is set to -1
How to reproduce:
1. Open the user-attached project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. Select the "Quad" GameObject in the Hierarchy
5. Change the Clear Color into anything in the "Test Blit" Script Component
6. Change the Slice field to any amount
7. Expand the Material Component and raise or lower the Slices count
Expected result: Only 1 color is on the Quad or switches between multiple colors
Actual result: When the Slices count in the Material goes above 1 the Color disappears/resets
Reproducible with: 2020.2.0a19, 2020.3.40f1, 2021.3.11f1, 2022.1.18f1, 2022.2.0b9, 2023.1.0a13
Not reproducible with: 2019.4.40f1, 2020.2.0a18
Reproduced on: macOS Monterey 12.6 (Intel)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment