Search Issue Tracker
Fixed in 2017.2.0f3
Votes
2
Found in
5.6.0f2
Issue ID
898615
Regression
No
Rendering doesn't execute on multiple cores when Graphics Jobs are enabled
To reproduce:
1. Open attached project
2. Build standalone project with Graphics Jobs enabled and graphics API set to Direct3D12
3. Open Task Manager
4. Run the build and observe CPU in Task Manager
5. Build standalone project with Graphics Jobs disabled and graphics API set to Direct3D11
6. Run the build and observe CPU in Task Manager
Expected: multiple cores of the CPU should be utilized when project was built with Graphics Jobs enabled
Actual: multiple cores of the CPU are not utilized when project was built with Graphics Jobs enabled
Reproduced in 5.5.2p4, 5.5.3f1, 5.6.0f2, 5.6.0f3, 2017.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on MeshRenderer::DispatchUpdate when disabling the second Mesh Renderer on a GameObject
- Inaccurate collisions when resizing Game view
- Animator Controller Layer name stays unchanged in Layers tab when renamed from Inspector
- [RenderingDebugger]Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
Add comment