This extension allows an apllication to voluntarily register itself with the driver, providing a more robust app detection solution and avoid the issue of the driver relying on exe names to match the app to a driver profile. This feature is supported in Radeon Software Version 17.9.2 onwards. Rules: More...

This extension allows an apllication to voluntarily register itself with the driver, providing a more robust app detection solution and avoid the issue of the driver relying on exe names to match the app to a driver profile. This feature is supported in Radeon Software Version 17.9.2 onwards. Rules:

AppName or EngineName must be set, but both are not required. Engine profiles will be used only if app specific profiles do not exist.
In an engine, the EngineName should be set, so a default profile can be built. If an app modifies the engine, the AppName should be set, to allow a profile for the specific app.
Version number is not mandatory, but heavily suggested. The use of which can prevent the use of profiles for incompatible versions (for instance engine versions that introduce or change features), and can help prevent older profiles from being used (and introducing new bugs) before the profile is tested with new app builds.
If Version numbers are used and a new version is introduced, a new profile will not be enabled until an AMD engineer has been able to update a previous profile, or make a new one.

The cases for profile selection are as follows:

Case	Profile Applied
App or Engine Version has profile	The profile is used.
App or Engine Version num < profile version num	The closest profile > the version number is used.
App or Engine Version num > profile version num	No profile selected/The previous method is used.
App and Engine Version have profile	The App's profile is used.
App and Engine Version num < profile version	The closest App profile > the version number is used.
App and Engine Version, no App profile found	The Engine profile will be used.
App/Engine name but no Version, has profile	The latest profile is used.
No name or version, or no profile	The previous app detection method is used.

As shown above, if an App name is given, and a profile is found for that app, that will be prioritized. The Engine name and profile will be used only if no app name is given, or no viable profile is found for the app name. In the case that App nor Engine have a profile, the previous app detection methods will be used. If given a version number that is larger than any profile version number, no profile will be selected. This is specifically to prevent cases where an update to an engine or app will cause catastrophic breaks in the profile, allowing an engineer to test the profile before clearing it for public use with the new engine/app update.