Search Issue Tracker
By Design
Votes
0
Found in
2022.3.58f1
6000.0.39f1
6000.1.0b7
6000.2.0a4
Issue ID
UUM-97848
Regression
No
Visual artifacts when the normal map is using mipmap and Bilinear filtering or Point filtering in URP Lit shader
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/DemonstrateBug.unity” Scene
3. Enter the Play Mode
Expected result: No artifacts exist
Actual result: Artifacts are present
Reproducible with: 2022.3.58f1, 6000.0.39f1, 6000.1.0b7, 6000.2.0a4
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Reproducible when shadows are disabled
- The sample demonstrates this issue with Bilinear and Point options for the same normal map.
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note:
This isn't an issue with URP's Lit shader; it's just an unfortunate side effect of computing mipmaps for the provided normal map.
This normal map has a very high-frequency/noisy texture (in-between the rocks) which unfortunately averages to the normal default direction, causing a dramatic transition between mip-levels 0 and 1. You can easily observe this by using the mip-slider in the preview at the bottom of the texture Inspector.
We recommend you either:
- Use a different normal map that doesn't present this issue.
- Use trilinear filtering for this texture.
- Unchecking the 'Generate Mipmap' toggle in the Texture Import Settings.