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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
Cosmetic, because enabling Graphics Jobs will disable multithreading rednering. They are 2 different modes.