Search Issue Tracker
By Design
By Design in 2017.2.X
Votes
0
Found in
2017.2.1f1
Issue ID
982564
Regression
No
Shaders with Tessellation and Custom Lighting break
How to reproduce:
1. Open Unity
2. Load tester-submitted project(Link to OwnCloud archive in the edit section)
3. Open 'TessMaterialTest.unity'scene
4. In Scene view, fly around the sphere and observe tessellation artifacts
5. in Game view, notice tesselation artifacts to appear as black smears
Expected result: Unity renders the sphere without artifacts
Actual result: Unity renders the sphere with black smears
Notes:
- Could be related to depth buffer
- Changing 'Tessellation Edge Length' and 'Tessellation Phong Strength' properties, changes appearance of artifacts
Reproducible with - 5.6.5f1, 2017.1.3f1, 2017.2.1p2, 2017.3.0p2, 2018.1.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment