Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X
Votes
0
Found in
2017.3.0a7
2018.1.0b9
Issue ID
1010840
Regression
Yes
Command Line Argument "-force-gfx-jobs off" doesn't disable "Graphics Jobs(experimental)" in the Player Settings
Reproduction steps:
1. Create a New Project
2. Go to the "Player Settings" -> "Other Settings" -> Enable "Graphics Jobs (Experimental)"
3. Exit Unity
4. Launch Unity with this cmd argument "-force-gfx-jobs off"
5. Go to the "Player Settings" -> "Other Settings"
6. Look if "Graphics Jobs (Experimental)" is disabled or enabled
Expected Result: Using cmd argument "-force-gfx-jobs off" disables "Graphics Jobs (Experimental)"
Actual Result: Using cmd argument "-force-gfx-jobs off" doesn't disable "Graphics Jobs (Experimental)"
Fixed in: 2018.3.0a10
Reproduced with: 2018.3.0a7, 2018.2.2f1, 2018.1.9f1, 2017.4.8f1, 2017.3.2f1, 2017.3.0a7
Did not reproduce on: 2017.3.0a6, 2017.3.0a1, 2017.2.3p3, 2017.1.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Profiler disconnects from WebGL Player when it gets clicked on in URP
- Crash on -[NSApplication _crashOnException:] when opening a specific custom Editor window
- Sprite editor does not allow creating new sprite tiles in a sprite sheet with a specific name
- Crash on block_locate_free when rendering a specific scene
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
Add comment