Search Issue Tracker
Fixed in 2.1.1
Votes
0
Found in [Package]
Up to 2.1.0 (including)
Issue ID
1304020
Regression
No
[Adaptive Performance][UX] Adaptive Framerate or Adaptive Resolution Min and Max values are not saved after it is typed
How to reproduce:
1. Create a new project
2. Open Package Manager
3. Install Adaptive Performance package
4. Open Project Settings -> Adaptive Performance -> Simulator (or Samsung (Android) if you install Adaptive Performance Samsung Android package)
5. Navigate to Runtime Settings -> Scaler Settings -> Adaptive Framerate or Adaptive Resolution
6. Enable it and go to Rage Scaler
7. Type value, which is in the range, to the input field of Minimum and hit Enter
Actual result: value is not saved
Expected result: value is changed to what user typed and Maximum value should change accordingly, if all values are in the range
Unity Version:
Version: 2021.1.0b2.1745
Revision: 2021.1/staging 1e651ea6a5c1
Built: Tue, 05 Jan 2021 11:35:12 GMT
Adaptive performance package version:
2.1.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment