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
- "Customize handled extensions" part in the External Tools settings tab is not aligned with other properties
- Editor Diagnostics foldouts do not open when clicked on the foldout title
- [UI Builder] Visual Elements are not placed at the mouse cursor position when Absolute Position Placement is enabled
- "Width" and "Height" text is misaligned with slider ends in Screen Match Mode Parameters section of Panel Settings Asset
- Editor does not quit when Editor is not in focus and any floating window is opened
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.