Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0a1
2018.2.0a1
2018.3.0a1
2019.1.0a1
2019.1.0a10
Issue ID
1104464
Regression
No
[GLCore] Tessellation doesn't work on OpenGL while it works on Direct3D11
1. Download "OpenGLTessellationIssue.7z (12.7 MB)" project
2. Open a scene called "ddd" (In which you will find 2 cubes, Red and Blue)
3. Make sure that the Draw Mode used to display the scene is set to "Shaded Wireframe"
4. In PlayerSettings switch "Graphics APIs for Windows" from OpenGLCore to Direct3D11 and back to see the difference
Expected result: Switching "Graphics APIs for Windows" amongst OpenGLCore and Direct3D11, both Direct3D11 and OpenGLCore has Tessellation
Actual result: When switching "Graphics APIs for Windows" in-between OpenGLCore and Direct3D11 you will see that Direct3D11 has Tessellation where OpenGLCore does not.
Reproducible with: 2017.4.16f1, 2018.1.9f2, 2018.2.18f1, 2018.3.0b12, 2019.1.0a11
Note: In the project the "Red cube" has a Tessellation shader created by Unity and the "Blue cube" has a shader created by a customer.
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Resolution Note:
The wireframe mode for tessellation only works on DX11.
The rendering of tessellation object actually works.