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