Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-52926
Regression
No
[Win] Depth difference when two passes in one shader have the same vertex shader and different pixel shaders
Reproduction steps:
1. Open the attached "repro_IN-55414.zip" project
2. Open the "SampleScene" Scene
3. Enter the Play Mode
4. Observe the Game view
Expected result: "Fishing_water" GameObject is solid black when it moves
Actual result: There are visible holes in the "Fishing_water" GameObject when it moves
Reproduced with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproduced on: Windows 10 (22H2)
Not reproduced on: macOS Monterey 12.6.1 (M1)
Note:
- On Windows 10, the issue was not reproducible on a machine with AMD Radeon RX 6800XT GPU but was reproducible on a machine with Nvidia GeForce RTX 3080 GPU
- Reproducible 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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
NVidia windows opengl drivers issue, depending on vertex stage output usage in fragment shader, the vertex shader output can have slight differences in depth values, most likely due to driver optimizations omitting unused variables and calculations.