Search Issue Tracker
By Design
Votes
0
Found in
2022.3.31f1
6000.0.4f1
6000.1.0a7
Issue ID
UUM-73171
Regression
No
Rendering a transparent material takes over 200ms when it is close to the Camera while using D3D12 or Vulkan in HDRP
Reproduction steps:
1. Open the attached “TestProject.zip” project
2. Click File > Build and Run
3. Observe the Player
Expected results: The Camera view moves without any major lag
Actual results: The Camera view lags just before rendering a transparent sphere
Reproducible with: 2022.3.31f1, 6000.0.4f1
Couldn’t test with: 2021.3.39f1 (Compiler errors)
Reproducible on: Windows 10 (by reporter), Windows 11
Not reproducible on: Windows 10 pro (2H22), macOS 13.5.2 (Intel)
Notes:
- Not reproducible with Direct3D11
- Couldn’t test with OpenGLCore, OpenGLES3 (Not supported with HDRP)
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Resolution Note:
The performance spike is due to pipeline state object compilation which happen when a combination of shader and state configuration are first encountered during runtime on modern graphics APIs such as DX12 and Vulkan. Note that this spike can be lower on subsequent runs of a player build depending on GPU vendors as a disk cache is sometimes handled at the driver level. Unity 6 introduced a solution to mitigate the issue, with the introduction of the GraphicsStateCollection API. On older versions of Unity, there is unfortunately no easy solution and we recommend using DX11 on Windows if this is an issue.
Resolution Note:
The performance spike is due to pipeline state object compilation which happen when a combination of shader and state configuration are first encountered during runtime on modern graphics APIs such as DX12 and Vulkan. Note that this spike can be lower on subsequent runs of a player build depending on GPU vendors as a disk cache is sometimes handled at the driver level. Unity 6 introduced a solution to mitigate the issue, with the introduction of the GraphicsStateCollection API. On older versions of Unity, there is unfortunately no easy solution and we recommend using DX11 on Windows if this is an issue.