Search Issue Tracker
Fixed in 6000.0.23f1
Fixed in 6000.0.X, 7000.0.0a10, future release
Votes
0
Found in
6000.0.0b16
6000.1.0a7
Issue ID
UUM-70187
Regression
No
[Player Settings] [Common] [Rendering] - Graphics Jobs should be changed per build profile and not globally
Steps to reproduce:
1. Open File > Build Profiles
2. Create a build profile and add a player settings to it (press Customize Player Settings)
3. Change Graphics Jobs under Other Settings > Rendering
Actual results: When the graphics jobs value is changed, it's also changing the Project Settings' player settings values.
Expected results: When the graphics jobs value is changed, it shouldn't change the value globally.
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Resolution Note (fix version 6000.0):
Graphics Jobs now correctly changes per build profile and not globally.