Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.2.0a4
Issue ID
707844
Regression
No
[GLCore] Tessellation only works with glcore43 or newer
Tessellation only works with glcore43 or newer version, but with modified glcore it should work with every version, because untiy should include Tessellation as extension.
1. Open project with -force-glcore43 (Be sure your GPU supports Tessellation).
2. Open scene "Test".
3. Notice that cube has tessalation shading.
4. Open project with -force-glcore32 (Be sure your GPU supports Tessellation).
5. Open scene "Test".
6. Notice that shader fallbacks.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- OnPointerExit and OnPointerEnter is mistakenly called when an overlapping child Image is destroyed
Add comment