Official Adaptive Performance Package

We released Adaptive Performance and Samsung Android 2.0.0 Preview 11 today which comes with many fixes and updates to the Indexer and Scalers. Please read the changelog below for details. The installation in Adaptive Performance 2.0 is different to 1.0 due to the new provider system. Please see the quick installation guide below. Changes in Adaptive Performance 2.0:

• Samples to show off different Adaptive Performance features.
• Settings for Scalers
• A number of sample Scalers
  • Adaptive Sorting
  • Adaptive Batching
  • Adaptive Shadowmap Resolution
  • Adaptive Shadow Distance
  • Adaptive Shadow Quality
  • Adaptive Shadow Cascades
  • Adaptive LOD
  • Adaptive MSAA
• Fixes to VRR support.

Quick Installation Guide:

• Install Android Support for Unity. Unity needs Android Support to build to your Samsung device.
• Switch Platform to Android in the Build Settings window.
• Use the Unity Package Manager and install the Adaptive Performance
• Install and activate the Adaptive Performance Samsung Android provider in Adaptive Performance Settings.
• If you want to use the Device Simulator Extension, you also have to activate the Adaptive Performance Simulator provider in the Adaptive Performance Settings.

Please also read the Installation Guide in the manual, which has additional details.

 

Not at this moment with the shipped providers.

 

We released Adaptive Performance and Samsung Android 1.1.9 and 1.2.0 today which comes with bug fixes, dependency changes and updates. Please read the changelog for details. 1.1.9 and 1.2.0 have the following fixes:

• Automatic Performance Mode: lower CPU and GPU levels at the same time instead of one at a time to increase efficiency and higher power savings.
• Fixed Automatic Performance Control flag to respect the function and not be read only anymore.
• Thermal Mitigation Logic changes in GameSDK 3.2 and it was updated in SetFreqLevels() to react to the correct return values.
• Automatic Performance Mode: gpuUtilizationThreshold increased from 0.7 to 0.9 to increase effeciency.
• Automatic Performance Mode: gpuFactor increased from 0.72 to 0.92 to increase effeciency.
• Automatic Performance Mode: Increase GPU Active time Ratio.
• Changed Documentation to make clear that changing CPU and GPU levels is risky and the Automatic Performance Mode should be used instead.
• Exchanged GameSDK wrapper with updated version removing GameSDK 3.1 support.
• Automatic Performance Control does not lower CPU lower than 1 on GameSDK 3.2 workaround.
• Add workaround to send temperature warning when the device starts as warm already as currently no events are sent.

1.2.0 has the same changes as 1.1.9 but it also updates a dependency: The Subsystem Registration was updated from 1.0.6 to 1.1.0. This updates the minimum supported version to Unity 2019.4. It fixes an issue where you get compilation errors if you disable the built-in module Subsystems in your project and you install Adaptive Performance afterwards. This is an issue in Unity 2019.4+. A workaround is to enable the the Subsystem module again before installing Adaptive Performance. This means, the Support Matrix looks like:

Unity 2018 LTS : Adaptive Performance and Samsung Android 1.1.9
Unity 2019 LTS+: Adaptive Performance and Samsung Android 1.2.0

 

We are happy to announce that Adaptive Performance 2.0.0 and Samsung Android 2.0.0 are now available. This verified release comes with many new features to improve your device performance. It comes with samples which can be use on the Samsung device but also in the Unity Editor in combination with the Device Simulator:

• Samples to show off all Adaptive Performance features.
• Editor settings for all features.
• All features of Adaptive Performance 1.0. including Automatic Performance mode, Bottleneck and Thermal state detection.
• Device Simulator Extension
• A number of Scalers utilizing the Indexer
  • Adaptive Framerate
  • Adaptive VRR
  • Adaptive Resolution
  • Adaptive Sorting
  • Adaptive Batching
  • Adaptive Shadowmap Resolution
  • Adaptive Shadow Distance
  • Adaptive Shadow Quality
  • Adaptive Shadow Cascades
  • Adaptive LOD
  • Adaptive MSAA

• Variable Refresh Rate Support.

Quick Installation Guide:

• Use the Unity Package Manager and install the Adaptive Performance.
• Install and activate the Adaptive Performance Samsung Android provider in the Adaptive Performance Settings.
• If you want to use the Device Simulator Extension, you also have to activate the Adaptive Performance Simulator provider in the Adaptive Performance Settings and install the Device Simulator Package.
• Install Android Support for Unity. Unity needs Android Support to build to your Samsung device.
• Switch Platform to Android in the Build Settings window.

Please also read the Installation Guide in the manual, which has additional details.

For additional information and upgrade guides, please see the first post.

 

We released Adaptive Performance and Samsung Android 2.0.1 today which comes with bug fixes, and updates. Please read the change log linked above for details.

 

We released Adaptive Performance and Samsung Android 2.0.2 today which comes with bug fixes when you use Unity < 2020.2. Please read the change log linked above for details.

We also release Samsung Android 1.2.1 today which replaces a broken 1.2.0 - please upgrade to Samsung Android 1.2.1 if you use 1.2.0. In case you use Unity 2018, please stay/downgrade to 1.1.9.

 

There is additional APIs in Android 11 which we evaluate at the moment. Most Thermal APIs, required for Adaptive Performance, are still missing on Android and iOS. We monitor the APIs closely and hopefully will be able to support more platforms in future. For now, if you use Adaptive Performance, it should be easy to adapt it for other platforms once they are available.

 

We released Adaptive Performance and Samsung Android 1.1.10 and 1.2.2 last week which comes with bug fixes. Please read the change log linked for details.

https://docs.unity3d.com/Packages/com.unity.adaptiveperformance@1.1/changelog/CHANGELOG.html
https://docs.unity3d.com/Packages/com.unity.adaptiveperformance.samsung.android@1.1/changelog/CHANGELOG.
htmlhttps://docs.unity3d.com/Packages/com.unity.adaptiveperformance@1.2/changelog/CHANGELOG.html
https://docs.unity3d.com/Packages/c....samsung.android@1.2/changelog/CHANGELOG.html

 

We are researching possible extensions, but for now it's not available. However, you always can create a custom provider easily if you find yourself on platforms which have similar APIs available already.

 

We are bound by API availability with the extension to other systems unfortunately. The good thing is that with Samsung you have million devices covered, as it's a pretty big part of the Android ecosystem and, once you implement it successfully, it will work out of the box for any other platform once it is available.

 

We released Adaptive Performance and Samsung Android 2.1.1 last week which comes with several bug fixes. Please read the change log linked for details.

 

We released a new blog post with some info about AP 2.0 which features a video about the functionality!

https://blogs.unity3d.com/2021/03/3...-that-run-smoothly-with-adaptive-performance/

 

Thermal Info is a great API, and we'd love to support it on more platforms and using the Provider.Feature is exactly what will be used for it. (Alternatively you can already use it if you implement the provider yourself) We gonna add some more Provider.Feature helper function to make it more useful during runtime in the next release.

The current APIs for thermal are less precise then what we use on Android/Samsung devices. The good news is that with Android 11 the thermal headroom API provides us with more details we can use to generate a thermal trend picture to service the basic functionality of AP.

Thanks for your feedback, really appreciate it. Stay tuned for more updates soon!

 

We released Adaptive Performance and Samsung Android 3.0.0-prev.2 which comes with several new features. It comes as verified package release candidates in 2021.2.0a19 but minimum requires version is 2021.2.0a18.

New in 3.0 (3.0+ only)

• Minimum Support Unity 2021.2
• Startup Boost mode - Enables boost mode during engine startup.
• Profiler Integration - Profile Adaptive Performance easily from the Unity Profiler.

New in 3.0 (also coming to 2.2)

• Scaler profiles - Easily define and change Adaptive Performance Scalers with predefined profiles.
• Boost mode - Boost CPU and GPU for short periods of time.
• Cluster info - Request cluster info to have details which and how many cores are available on the device.
• Feature API - Check which Adaptive Performance feature is available on the current platform.
• Adaptive view distance scaler - A new scaler to change the Camer.main view distance automatically.
• Additional samples

Boost mode, Startup Boost mode and Cluster info API require GameSDK 3.5 which is not released at this point, but you can use the Device Simulator Extension to simulate the features. We will keep you posted when GameSDK 3.5 is going to be publicly available on Samsung Phones. This is a release which comes with many new feature and we would love to hear feedback. Some features require a breaking upgrade, so please ensure your project is backed up properly!

 

Hi Guillogika,

Can you verify that both checkmarks (Samsung Android Provider as well as Initialize Adaptive Performance on Startup) are ticked in the Android Provider Settings?

 

Can you try the following test.apk and see if you get the output below in logcat?

Code (CSharp):

1. [Adaptive Performance] Subsystem version=3.3

3.3 or higher, otherwise it is a possibility that game SDK installed on the device is not supported. If there is a device update available I'd recommend to install that.

 

This looks like the phone does not have Samsung GameSDK 3.3+ installed which is required for AP 2.x. Is this the same message with the up to date S21?

 

We released Adaptive Performance and Samsung Android 2.2.1 which comes with several new features (backported from 3.0.0 where possible). It comes as verified package in 2020.x+ but also works with 2019.

New in 2.2

• Scaler profiles - Easily define and change Adaptive Performance Scalers with predefined profiles.
• Boost mode - Boost CPU and GPU for short periods of time.
• Cluster info - Request cluster info to have details which and how many cores are available on the device.
• Feature API - Check which Adaptive Performance feature is available on the current platform.
• Adaptive view distance scaler - A new scaler to change the Camera.main view distance automatically.
• Additional samples

Boost mode, Startup Boost mode and Cluster info API require GameSDK 3.5 which is not released at this point, but you can use the Device Simulator Extension to simulate the features. We will keep you posted when GameSDK 3.5 is going to be publicly available on Samsung Phones. This is a release which comes with many new feature and we would love to hear feedback. Some features require a breaking upgrade, so please ensure your project is backed up properly!

 

I'm sorry that this is happening. I do not have a good explanation at this point.
This forum is fine, once we found a solution it hopefully will help anyone running into similar issues.

The log indicates that it's running GameSDK 3.4 on the device and it would be available to use.
As we ruled out the GameSDK version, the other way for the message to appear is if GameSDK can not be initialized correctly.
Can you provide the full logcat log from application start?
Also, the apk was made with 2.2.1 - which has a newer GameSDK wrapper. Can you upgrade to 2.2.1?

 

That looks normal - except it should initialize properly if the test apk worked. Could you include the full logcat (not limited to Unity logs only) as there should be some additional info. You can also send a private message with the log if needed - or email to db@unity.com and I can have a closer look at the init process. Also please restart the device to ensure the startup process is clear.

 

The issue above is not easy to debug and we will add additional logging to Adaptive Performance in future. If you are stuck on a older version and wonder what's wrong, you can add some more logs into the SamsungGameSDKAdaptivePerformanceSubsystem.cs found in Adaptive Performance Samsung Android package under Runtime/Provider.

Instead of the current RegisterDescriptor() you can add following:

Code (CSharp):

1.         static void RegisterDescriptor()
2.         {
3.             if (!SystemInfo.deviceModel.StartsWith("samsung", StringComparison.OrdinalIgnoreCase))
4.             {
5.                 GameSDKLog.Debug($"The device {SystemInfo.deviceModel} is not a supported Samsung phone. This provider will not run. Aborting registering the Adaptive Performance provider descriptor.");
6.                 return;
7.             }
8.  
9.             if (!NativeApi.IsAvailable())
10.             {
11.                 GameSDKLog.Debug($"The native API for this provider is not available. Aborting registering the Adaptive Performance provider descriptor.");
12.                 return;
13.             }
14.  
15.             AdaptivePerformanceSubsystemDescriptor.RegisterDescriptor(new AdaptivePerformanceSubsystemDescriptor.Cinfo
16.             {
17.                 id = "SamsungGameSDK",
18.                 subsystemImplementationType = typeof(SamsungGameSDKAdaptivePerformanceSubsystem)
19.             });
20.         }

and instead of StaticInit() please add:

Code (CSharp):

1.             static private void StaticInit()
2.             {
3.                 if (s_GameSDK == null)
4.                 {
5.                     try
6.                     {
7.                         s_GameSDK = new AndroidJavaObject("com.samsung.android.gamesdk.GameSDKManager");
8.                         if (s_GameSDK != null)
9.                             s_isAvailable = s_GameSDK.CallStatic<bool>("isAvailable");
10.                     }
11.                     catch (Exception ex)
12.                     {
13.                         GameSDKLog.Debug($"GameSDK is not available due to {ex} Aborting Adaptive Performance initialization.");
14.                         s_isAvailable = false;
15.                         s_GameSDK = null;
16.                     }
17.  
18.                     if (s_isAvailable)
19.                     {
20.                         s_GameSDKRawObjectID = s_GameSDK.GetRawObject();
21.                         var classID = s_GameSDK.GetRawClass();
22.  
23.                         s_GetGpuFrameTimeID = GetJavaMethodID(classID, "getGpuFrameTime", "()D");
24.                         s_GetHighPrecisionSkinTempLevelID = GetJavaMethodID(classID, "getHighPrecisionSkinTempLevel", "()D");
25.  
26.                         if (s_GetGpuFrameTimeID == (IntPtr)0 || s_GetHighPrecisionSkinTempLevelID == (IntPtr)0)
27.                             s_isAvailable = false;
28.                     }
29.                 }
30.             }

Note: You will have to make a local copy of the package in the Project/Package folder to be able to save changes. To see the logs you will need to enable the Samsung Provider Logging in the AP Settings and run the app in development mode to get the logs.

 

If you face a situation and get errors like: Unable to start the Samsung Android subsystem. The log above might give you a better insight what's wrong.

If you receive a log like [Samsung GameSDK] GameSDK is not available due to UnityEngine.AndroidJavaException: java.lang.ClassNotFoundException: com.samsung.android.gamesdk.GameSDKManager it might mean the GameSDKManager was removed from your final binary. This can happen due to minify or ProGuard. You can check the Player Settings if they are activated for the project. Note: Those settings can be overridden if you use a custom Gradle Project.



In some cases it helps to add a custom proguard-user.txt file in Assets/Plugins/Android with the following content:

-keep class com.samsung.android.gamesdk.** { *; }
-keepclassmembers class com.samsung.android.gamesdk.** { *; }

This tell Proguard to keep the files and not minify or optimize them. You can verify your settings if you export your project and open it in Android Studio. This should also help if a 3rd party plugin overrides your settings and still strips the classes.



While unfortunately it did not solve Guillogikas issues I hope this helps others to narrow down the problem.

 

TLDR; Yes, Samsung only at this moment.
- You can use the Samsung Provider to run it on a variety of Samsung phones.
- By default the package default provider is for the Editor/Device Simulator.
- Custom providers can be used for other platforms.
- I agree, the mobile flag in the release notes is not great, unfortunately, there is no Samsung section atm.

 

We released Adaptive Performance and Samsung Android 4.0.0-pre.1 today, which comes with several new features. This is a release candidate and not a verified package. It will come as verified package in 2022.1+ but also works with 2021.2+.

New in 4.0

• Adaptive Layer Culling
• Custom Scaler
• Adaptive Decals (requires URP 13 which will be released soon)
• Adaptive Physics
• Visual Scripting support
• Additional samples

Installation:
To install the RC package, please add it manually to the package manifest.

Code (CSharp):

1. "com.unity.adaptiveperformance": "4.0.0-pre.1",

In the Adaptive Performance Settings, enable and download the Samsung provider and it will download the package for you.

This is a release which comes with many new feature and we would love to hear feedback!

 

Yes, @freso those are all things we are investigating for a cross-platform solution and it currently is not supported if you don't add a custom provider for desktop which would support the APIs by yourself.

Adaptive Performance modes is a feature we are looking into which describes how automatic scaling would work with a general provider.

 

@freso this is the best thread to follow for updates.
@abushaheen You can disable it in the Adaptive Performance Settings. Alternatively, please verify by removing Adaptive Performance Package form the Package Manager if this crash is related to Adaptive Performance.

 

Great news for everyone, who develops their own provider or derivation of Adaptive Performance.

The frame timing manager got an upgrade and supports more detailed information and more platforms, check it out here: https://forum.unity.com/threads/update-for-frame-timing-manager.1191877/#post-7623058

Why is this relevant?
Adaptive Performance uses the frame timing manager and subsidizes platform specific timing information where needed and the new release will make it more precise and easier to run on more platforms.

 

We gave a talk about Adaptive Performance recently at the ARM Devsummit. Please tune in to hear some update to Adaptive Performance.

 

The easiest way is to look at SamsungGameSDKAdaptivePerformanceSubsystem.cs in com.unity.adaptiveperformance.samsung.android\Runtime\Provider and make your own provider. There's additional documentation here.

The best way is to modify the Capabilities and supply the Feature.TemperatureLevel | Feature.WarningLevel | Feature.GpuFrameTime | Feature.CpuFrameTime and then modify m_Data.ChangeFlags |= Feature.WarningLevel; (and the m_Data content) to deliver the temp level, warning level, gpu and cpu time coming from the FrameTimingManager.