Search Issue Tracker
By Design
Votes
1
Found in
2017.3.1f1
Issue ID
1006201
Regression
No
Frame debugger can't be attached to player with graphics jobs enabled
To reproduce:
1. Create new project
2. Enable Graphics Jobs in player settings
4. Build and run development build
5. Open Frame Debugger
6. Try connecting Frame Debugger to standalone build
Expected: Frame Debugger connects
Actual: Frame Debugger fails to connect and following error is thrown in console: Failed to enable Frame Debugger: Requires multithreaded rendering to be enabled.
Reproduced: 2018.3.0a1, 2018.2.0b13, 2018.1.0f2, 2017.4.3f1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
By-design for now that frame debugger does not support graphics jobs.