Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.17f1
2023.2.0b14
2023.3.0a10
Issue ID
UUM-53923
Regression
No
Compute Shader doesn't seam terrains together when running Editor with Nvidia and Intel GPUs
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Simple.unity“ scene
3. In the Scene View, fly around and observe the terrain
Expected result: Terrain GameObjects are seamed together
Actual result: Terrain GameObjects are not seamed together and have gaps between them
Reproducible with: 2021.3.31f1, 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a10
Reproducible on: Ubuntu 23.10 (Nvidia, Intel), Ubuntu 22.04 (Nvidia), Windows(Nvidia, glCore)
Not reproducible on: Ubuntu 22.04 (AMD), Windows 10 Pro 22H2
Notes:
- With OpenGL set as Graphics API, this issue is reproduced with Nvidia and Intel GPUs
- With Vulkan set as Graphics API, this issue is reproduced only with Intel GPU
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
GPU drivers bug mixed with faulty user's compute shader:
On NVidia running OpenGL, compute shader fails to load+store R16_UNorm texture. User's compute shader uses RWTexture2D<float4>format which is not compatible with R16.
Workaround: R16_SFloat seems to work. Or avoid reading and writing the same texture in compute shader.