**System Information**
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71
**Blender Version**
Broken: version: 2.93.0, branch: master, commit date: 2021-06-02 11:21, hash: `rB84da05a8b806`
Also broken in 3.0 alpha
**Short description of error**
If a normal map has it's image texture set to Closest or Cubic, the result in Eevee looks incorrect. I'm not sure if this is a fundamental limitation of the method or if it's something that could be fixed in the implementation, but I've found the Closest interpolation to be really useful when heavily messing with an image's vector coordinates.
**Exact steps for others to reproduce the error**
1. Load up a normal map and apply it to a smooth shaded object
2. Set the image texture's interpolation to Closest or Cubic
{F11582031}
Linear filtering:
{F11581983}
Closest filtering:
{F11581974}