Search Issue Tracker
Fixed in 7000.0.0a1
Fixed in 2023.3.X, 2023.3.0a1, future release
Votes
0
Found in
2023.3.0a1
Issue ID
UUM-26106
Regression
No
Gaussian filtering uses aggressive settings when Filtering enum is set to Advanced
Jira twin of: https://fogbugz.unity3d.com/f/cases/1362188/
Steps to reproduce
- Open an existing Unity project, or create a new one
- Navigate to Window > Rendering > Lighting
- Click on the New Lighting Settings button
- Navigate to Filtering, and set that enum to Advanced
- Notice, that Gaussian filtering settings are overly aggressive
Notes
- Suggest changing each Gaussian kernel size to 1 texel. This will match the behavior in Auto filtering preset
Current settings
!AdvancedFilteringSettings-Current.png|thumbnail!
Suggested settings
!AdvancedFilteringSettings-Suggested.png|thumbnail!
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
Add comment