Search Issue Tracker
Not Reproducible
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
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
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
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
- "Curve" window workspace doesn't update the scale to match the selected curve preset unless reopened
- StackOverflowException occurs and tests fail to load when the Test Runner window is opened while System.Windows.Forms.dll and System.Deployment.dll are present in the project
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
Resolution Note:
I was unable to retrieve the initial test project, but when testing the URPSample scene from Hub, the project worked normally with -job-worker-count 0 in both DX11 and DX12. If the initial project is still showing issues, please re-report the issue.