Search Issue Tracker
Fixed in 1.1.7
Votes
0
Found in [Package]
1.1.6
Issue ID
1246170
Regression
No
[Adaptive Performance] Auto Control Mode does not get enabled when changed during runtime
Steps to reproduce:
1. Open attached project
2. Make sure that:
- AdaptivePerformanceSettings.cs Line 22 should say "StartupSettings.Enable = false;"
- Inside AutomaticPerformanceControl scene -> AutoPerfControl GameObject -> Auto Perf Control script -> Auto Control Mode should be set to TRUE
This basically sets up a scenario where Auto control mode was set to FALSE during startup, but then it was set as TRUE during runtime
3. Build and run Automatic Performance Control scene on device
4. Observe CPU and GPU levels stay at 0, despite the device being taxed and requiring more processing power
5. Click the "Recent apps" button on the device
6. Go back to the Unity App (focusing it again)
7. Observe CPU and GPU levels being managed right away.
Expected: Setting the Automatic Performance Control mode to TRUE during runtime should begin effects immediately - CPU and GPU levels should start fluctuate based on current performance
Actual: Setting the APC mode to TRUE during runtime does nothing. It only gets updated during startup and during app refocus.
Devices Reproduced on:
Samsung Galaxy Fold (SM-F900F) Adreno (TM) 640 Snapdragon 855 SM8150 Android 9
VLNQA00264 Samsung Galaxy S10+ (SM-G975F)Mali-G76 Android 10
Unity version:
Version 2019.3.11f1 (ceef2d848e70)
Tue, 21 Apr 2020 03:45:09 GMT
Branch: 2019.3/staging
Adaptive Performance and Samsung Provider Package Versions:
Up to 1.1.6 (including)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Add comment