Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2019.4.X, 2020.1.X



Found in




Issue ID




[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

1. Tested on Ubuntu 18.04 and Windows 10 (Doesn't reproduce)
2. GPU used - Nvidia GTX 1060

  1. Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0a21

  2. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.8f1

  3. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.13f1

Comments (2)

  1. 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

  2. TheKraken64

    Jan 28, 2021 16:55

    I believe "-forceVulkan" is a typo. It should be "-force-vulkan".

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.