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
- “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
Add comment