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
- 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
Add comment