Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2
2019.3
2020.1
2020.1.0a8
Issue ID
1190247
Regression
No
Material's RGBA output values are too high
1. Open the attached 'PostProcessNaNs.zip'project
2. Open 'SampleScene' Scene
3. Select 'Main Camera' GameObject in the Inspector
4. Set Transform Position Y value to 90 and Transform Rotation X value to 90
5. Enter Play Mode
6. Move Camera along positive Z-axis
7. Observe Bloom's effect brightness in Game View
Expected result: Material outputs RGBA pixel values below 1, Bloom effect is not that intensive
Actual result: Material outputs high pixel values such as RGBA(14,11,2,1), Bloom effect is too intensive
Reproducible with: 2018.4.7f1 with smaller repro project, 2019.2.11f1, 2019.3.0b9, 2020.1.0a11
Couldn't test with: 2017.4.33f1, 2018.4.12f1 due to errors in original repro project
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.3.X):
Low priority based on product evaluation, extreme edge case