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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment