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
- "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
Resolution Note:
By-design for now that frame debugger does not support graphics jobs.