Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
2
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1252387
Regression
No
[Linux] Frame Debugger can not be enabled and asks for multi-threaded renderer to be enabled even when it's forced on
How to reproduce:
1. Create a new project and launch it using the "-forceVulkan" and "-force-gfx-mt" arguments
2. In the Editor open the "Frame Debug" window by going to the menu bar: Window > Analysis > Frame Debugger
3. Notice the "Enable" button near the top left corner of the "Frame Debug" window
Expected result: The button is interactible and when pressed enables the Frame Debugger
Actual result: The button is greyed-out and not interactible
Reproducible with: 2018.4.24f1, 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
Notes:
1. Tested on Ubuntu 18.04 and Windows 10 (Doesn't reproduce)
2. GPU used - Nvidia GTX 1060
-
iminsert
May 09, 2022 20:49
just doubling down here, using manjaro with unity hub from flatpak, and vsCode from the aur's, on unity 2021.3.1f1,
"-force-vulkan" then "-force-gfx-mt" on a new line does fix the issue for me aswell -
TheKraken64
Jan 28, 2021 16:55
I believe "-forceVulkan" is a typo. It should be "-force-vulkan".
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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21
Resolution Note (fix version 2020.1):
Fixed in 2020.1.8f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.13f1