Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2018.4
2019.4
2020.2.0f1
2020.3
2021.1
2021.2
Issue ID
1323892
Regression
No
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
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Resolution Note (fix version 2021.2):
Vulkan and desktop OpenGL support (via extension) for fine/coarse derivatives is incoming
Fixed in - Unity 2021.2.0a20