Search Issue Tracker
Won't Fix
Votes
5
Found in
2021.3.37f1
2022.3.26f1
2023.2.19f1
6000.0.0b16
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-71678
Regression
No
Tessellation has poor performance in URP when rendered using Metal
How to reproduce:
1. Open the attached “IN-72831“ project
2. Open the “bug_primitiveid” scene and enter Play mode
3. Press the “Stats” button in the top-right corner of the Game view
4. Take note of the frame rate displayed in the Statistics window
5. In the Project tab, navigate to “Assets/ExampleCode/” and select the “Unlit_NewUnlitShader” Material
6. In the Inspector, select the “Shader” drop-down and choose “Tesselation/BUG_SV_PrimitiveID”
7. Repeat step 4
Expected result: The frame rate does not change when the shader is changed
Actual result: There is a significant drop in frame rate when the tessellation shader is applied (160FPS to 100FPS)
Reproducible in: 2021.3.37f1, 2022.3.26f1, 2023.2.19f1, 6000.0.0b16
Reproducible on: macOS 10.15 (Intel), macOS 11.7.2 (Intel), macOS 12 (Silicon)
Not reproducible on: Windows 10, Windows 11
Notes:
- Also reproducible in Player
- Not reproducible with OpenGLES3, OpenGLCore, and Vulkan graphics APIs
- The shaders failed to render using Direct3D11 and Direct3D12
Comments (1)
-
flyer19
Sep 09, 2024 06:09
how about this now?
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.