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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment