Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 2023.2.X
Votes
0
Found in
2020.3.39f1
2021.1.14f1
2021.3.9f1
2022.2.0b7
2023.1.0a8
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-14302
Regression
No
Unity doesn't fully open and gets stuck on a process when opened using "-job-worker-count 0" and "-force-d3d11" command line arguments
Steps to reproduce:
1. Open the attached project “Test.zip“ using the command line with the “-job-worker-count 0“ and “-force-d3d11“ arguments
2. Observe the partially open project
Expected result: Unity project fully opens
Actual result: Unity gets stuck on a process and doesn’t fully open
Reproducible with: 2020.3.39f1, 2021.3.9f1, 2022.1.14f1, 2022.2.0b7, 2023.1.0a8
Reproducible on: Windows 10
Notes:
1. 2020.3.39f1 - stuck on AppStatusBar.Repaint
2. 2021.3.9f1, 2021.1.14f1 - stuck on Open Scene
3. 2022.2.0b7, 2023.1.0a8 - stuck on Toolbar.Repaint
4. Project opens with “-force-d3d12“ argument
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory Leak when using InstantiateAsnyc to instantiate a large Prefab
- There are checkboxes to enable and disable Volume Profile effects in the Graphics Settings
- “ArgumentException: Trying to use an invalid resource (pass Motion Blur)” errors are infinitely thrown when Motion Blur is used
- Inspector is not using the result of the last CreatePropertyGUI call when calling it for several times for one property
- Crash when attempting to initialize XR SDK while entering Play Mode
Add comment