It sets useAffinity, chipset, GPU, processorCount, bigCoreMask, and littleCoreMask.
#QCOM SMART TOOL MODULE HYDRO CODE#
The following code uses Regex to extract the number in Adreno (TM) 630 and compares it to see if it is less than 510 to flag an error.:Ĭondition:((SourceType=SRC_GpuFamily,CompareType=CMP_Regex,MatchString="(?!Adreno \(TM\))(*)"),(SourceType=SRC_PreviousRegexMatch,CompareType=CMP_LessEqual,MatchString="510")), (error="CR_Info_UnsupportedGPU")Ĭhipset is a shortcut to set a group of variables if the hardware string is equal to either ro.hardware or hardware. The following code will set myvar to arm64 if isARM64 is true and clears notsupported:Ĭondition:((SourceType=isARM64,CompareType=CMP_EQUAL,MatchString="true")),(myvar="arm64"),(notsupported) The following code will set myvar to arm64 if isARM64 is true:Ĭondition:((SourceType=isARM64,CompareType=CMP_EQUAL,MatchString="true")),(myvar="arm64")
#QCOM SMART TOOL MODULE HYDRO ANDROID#
The following examples show how you might setup and use the Android Config Rules Commands in your UE4 projects: True if regex in MatchString found in SourceType (matching group is available in SRC_PreviousRegexMatch for additional condition checks) True if value of SourceType >= value of MatchString True if value of SourceType value of MatchString. True if SourceType does not equal Matchstring, ignoring case. True if SourceType equals MatchString, ignoring case. True if SourceType not equal to MatchString. True if variable name in MatchString is not set. True if variable name in MatchString is set. MatchString is any string value to use for the comparison or the variable name for the case. Used with MatchString to see if a variable exists or not. The group returned from the last regex expression condition. The following are the three special SourceType values that can be used: SourceType specifies the first argument for comparison and will usually be a variable name. (SourceType=isARM64,CompareType=CMP_EQUAL,MatchString="true") The three parts are SourceType, CompareType, and MatchString. The comparisons are made up of three parts in parentheses separated by commas. You can clear more than one variable at a time using a comma ( ,) to separate the values you want to clear.Ĭondition evaluates the list of conditions and if all are true it applies optional set and clear commands.Ĭondition:((comparison), Set:(myvar=false,myvar2="something",myvar3="else")Ĭlear allows you to clear the value assigned to variables. If you have more than one variable, you can use a comma ( ,) to separate them:
Set allows you to assign one or more variables and their specified values: These are defined below along with use case examples. Height of Android navigation bar in pixels.Ĭommands can be used with valid arguments in the forum of action:argument. Indicates GPU supports FP render targets.Ĭomma-separated list of supported texture formats by GPU. Indicates ARM emulated on Intel processor by Houdini. Indicates if Vulkan is supported by the device. OpenGL ES 3.2 I42f6fe38fb) (Date:07/13/18)Īndroid version from android.os.ĭevice manufacturer from android.os.Build.MANUFACTURER.ĭevice model from android.os.Build.MODEL.ĭevice build number from android.os.Build.DISPLAY.
GL version from GLES20.glGetString(GLES20.GL_VERSION). GPU family from GLES20.glGetString(GLES20.GL_RENDERER). Vendor from GLES20.glGetString(GLES20.GL_VENDOR). Indicates processor supports NEON features (SIMD).īitmask indicating which cores are little. Whether or not to set thread affinity to little cores for some threads. The chipset (either Hardware from /proc/cpuinfo or getprop ro.hardware). The following variables are defined automatically before configrules.txt is parsed:
Would be replaced with the values of SRC_DeviceMake and SRC_DeviceModel separated by a space. Variables may be used in values with the following syntax: UE_LOG(LogAndroid, Log, TEXT("Found variable %s = %s"), *VarKey, *VarValue)
TMap ConfigRules = FAndroidMisc::GetConfigRulesTMap() It is also possible to get access to a TMap with the key/value entries if you would like to iterate over them: UE_LOG(LogAndroid, Display, TEXT("myflag was set!")) If (FAndroidMisc::GetConfigRulesVariable(TEXT("myflag") = TEXT("true")) Any variables still defined after the Config Rules runs may be queried from C++ with the following function:įString* FAndroidMisc::GetConfigRulesVariable(const FString& Key) Any line that starts with a // or semicolon( ) is treated as a comment and ignored.Ĭommands are used to manipulate case-sensitive variables which either trigger an immediate action or are passed on to the engine.
0 kommentar(er)
