Search Issue Tracker
Fixed in 2022.3.8f1
Fixed in 2022.3.X, 2023.2.X, 2023.2.0b4
Votes
19
Found in
2022.3.5f1
2023.1.4f1
2023.2.0a23
Issue ID
UUM-42795
Regression
Yes
Severe performance degradation in Play Mode when using multiple Cameras with “Direct3D12”, “OpenGLCore”, and “OpenGLES3” Graphics APIs in URP & HDRP
How to reproduce:
1. Open the “URP_Multi_Camera_Graphics_API_Performance“ project
2. Open the “SampleScene”
3. Open the Game view window and add an additional Game view (right-click on Game view tab > Add Tab > Game)
4. Make sure both Game view windows are visible
5. Make sure one Game view is using “Display 2”
6. Make sure the Game view with “Display 1” has the Rendering Statistics window open (“Stats” button)
7. Enter Play Mode and make sure that the Game view with “Display 1” is focused
8. Observe the Rendering Statistics window
Expected result: moderate performance impact - FPS is reduced by about 15-35%
Actual result: severe performance impact - FPS is reduced by about 50-70%
URP reproduced with: 2022.2.0a11, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
URP not reproduced with: 2021.3.28f1, 2022.2.0a10
HDRP reproduced with: 2021.3.28f1, 2022.2.0a11, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproduced on: macOS 12 (M1)
Notes:
1. Could not test in Player → could not find a way to render different cameras in different windows in one Player
2. Reproducible in a new project
3. Reproducible with “Direct3D12”, “OpenGLCore”, and “OpenGLES3” Graphics APIs in Universal and HD Render Pipelines
4. Not reproducible with “Direct3D11”, “Vulkan”, and “Metal” Graphics APIs
5. Performance degradation for the HD Render Pipeline is about 40-50% → created a new project with a “3D (HD RP)” template
6. Could not test “OpenGLCore”, and “OpenGLES3” Graphics APIs in the HD Render Pipeline → these Graphics APIs are not supported by the HD RP package
7. Could not test “Metal” Graphics API with 2023.2.0a23 in the HD Render Pipeline → “Compute shader” errors are thrown
8. It seems that before the regression point using the “Direct3D12” Graphics API in the Universal Render Pipeline, the FPS remains stable and in some versions was even slightly better (about 5%) when the second Game view was using “Display 2”
9. Did not reproduce with “OpenGLCore”, and “OpenGLES3” Graphics APIs in the Universal Render Pipeline in the regression point
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment