Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.12f1
2019.1.0a1
2019.2.0a1
Issue ID
1143474
Regression
No
Attaching build to "Frame Debug" throws inaccurate error when "Graphics Jobs" in Player settings is enabled
How to reproduce:
1. Open attached project "MultihreadedRenderingError.zip"
2. Make sure that "Edit" -> "Project Settings" -> "Player" -> "Other Settings" -> "Graphics Jobs (Experimental)*" is enabled
3. In "Build Settings" enable "Development Build"
4. Build and Run the application
5. In the Editor, open "Window" -> "Analysis" -> "Frame Debugger"
6. Select your build (in my case "WindowsPlayer")
7. Enable "Frame Debugger"
Expected result: the following error is thrown "Failed to enable Frame Debugger on Remote Device: Requires Graphics Jobs to be disabled."
Actual result: the following error is thrown "Failed to enable Frame Debugger on Remote Device: Requires multithreaded rendering to be enabled."
Reproducible with: 2017.4.25f1, 2018.3.12f1, 2019.1.0f1, 2019.2.0a11
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
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Memory leak warnings are constantly thrown when Generating Font Atlas in Font Asset Creator with 4096x8192 Atlas Resolution
- “Glyph rendering has been aborted due to sampling point size” Log is printed and Font Atlas is not generated when Atlas Resolution is 8192x8192, and the Render Mode is SDF
Resolution Note:
Cosmetic, because enabling Graphics Jobs will disable multithreading rednering. They are 2 different modes.