Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.21f1
Issue ID
UUM-36453
Regression
No
Full Screen Pass Renderer Feature oversaturates colors in inverse mode when "Linear" Color Mode and "FullscreenInvertColors" Pass Material is used
How to reproduce:
1. Open the “Color_Space_Render_Feature_Bug“ project
2. Open the “SampleScene”
3. Open and observe the Game view
4. Change Color Space to “Gamma“ (Edit > Project Settings > Player > Other Settings)
5. Open and observe the Game view again
Expected result: “Linear” and “Gamma” Color Modes are identical
Actual result: “Linear” Color Mode is more saturated than “Gamma”
Reproduced with: 2022.2.21f1
Could not reproduce with: 2020.3.48f1, 2021.3.26f1 (Failed to fix RenderFeature errors), 2023.1.0b18, 2023.2.0a16 (“ScriptableRenderer” API is no longer supported from URP 15 and upwards)
Reproduced on: Windows 11
Note: Reproducible in Player
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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 isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
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 (2022.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 isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
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.