Search Issue Tracker
Fixed
Won't Fix in 2021.3.X, 2022.3.X
Fixed in 6000.0.59f1, 6000.2.0a7
Votes
0
Found in
2021.3.43f1
2022.3.44f1
6000.0.17f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-79015
Regression
No
Scene Color Sampling fails when using a custom pass in 'After Post Process'
How to reproduce:
1. Open the “IN-82937_repro“ project
2. Open the “OutdoorsScene“
3. Observe the Scene view
Expected result: The scene is colored
Actual result: The scene is black
Reproducible with: 2021.3.43f1, 2022.3.44f1, 6000.0.17f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
This issue will be fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production.
Today we will be closing this port. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2021.3.X):
Thank you for reporting a bug to Unity.
This issue will be fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production.
Today we will be closing this port. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.