Search Issue Tracker
Won't Fix
Won't Fix in 3.2.X
Votes
0
Found in [Package]
3.2.2
Issue ID
PPB-7
Regression
No
PostProcessingVolume Effect List Not Repainting When Editing Values Via Script
Reproduction steps:
1. Open the user’s attached project
2. Open ”SampleScene” Scene
3. Open Inspector Windows for “Script” and “PostProcess Volume”
4. Enter Play Mode
5. Press the A and D keys to change the values of the Depth of Field.
Expected result: the Effect values are serialized and their changes are reflected in the Inspector
Actual result: the Inspector is not refreshing its values until Inspector Window is focused
Reproducible with: 2.2.2 (2019.4.39f1), 3.2.2 (2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.4f1, 2022.2.0a16)
Reproducible on: Windows 10 (21H2)
Note: Depth of Field values are not updated in the PostProcess Volume GameObject Inspector unless the mouse is focused on the Inspector window
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. 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 future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. 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 (3.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. 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 future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. 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.