Search Issue Tracker
Fixed
Fixed in 2020.3.X, 2020.3.38f1
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-2198
Regression
No
[Backport] Fwidth behavior is inconsistent between DX11/DX12 and OpenGL/Vulkan
How to reproduce:
1. Open the user attached project
2. Open the SampleScene
3. Observe the Sphere in the Game view. Notice that the applied texture does not have a seam
4. Switch the Graphics API to OpenGLCore or Vulkan
5. Observe the Sphere in the Game view again
Expected result: The applied texture does not have a seam
Actual result: The applied texture has a seam
Reproducible with: 2018.4.33f1, 2019.4.24f1, 2020.3.4f1, 2021.1.3f1, 2021.2.0a13
Notes:
1. The seam does not occur when D3D11 or D3D12 APIs are used
2. The issue occurs in Editor and in Player
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