![]() ![]() This section defines general information about the skin. Such common sections are and sections, the next chapter will discuss them in details. The list of sections is specific to the skin, but there are two common sections for all skins. The header format is derived from standard INI file format, so it is composed of multiple sections containing different fields. The header must have “ HDR” signature in the very beginning, otherwise the skin won’t work. skin name and author information, positions and styles of all controls in the skin and so on). The header is ASCII text file defining all information related to the skin (e.g. Storing images in different format will result in skin compilation error. The next chapters will discuss skin source files format in details.Īll source images representing different skin parts and controls must be stored as uncompressed 24-bit BMP images. After doing so you may edit the header to specify new skin name, author, password and redefine control positions in the header if needed then modify bitmaps for the controls you are about to change. \Skins\default folder contents to your new skin folder (e.g.\Skins\MySkin). Similar approach can be used to create new skins, just use decompiled default skin as a template and copy. For example, to compile edited default MSI Afterburner or EVGA Precision skin use: \Skins\.usf file from the source files stored into. Where is the name of application with integrated skin compiler and is the name of skin to be compiled. You can modify them and compile modified skin using the following command line switch: Similar to that, default EVGA Precision skin (.\Skins\f file in EVGA Precision folder) is compiled with jsRfsgTd password, so it can be decompiled using the following command line switch:Īfter decompiling the skin decompiled source files will be stored in. The following passwords are used for the following RivaTuner skinning technology based products:įor example, default MSI Afterburner skin (.\Skins\f file in MSI Afterburner folder) is compiled with te6Xfjz3 password, so it can be decompiled using the following command line switch: ![]() Where is the name of application with integrated skin decompiler, is the name of skin file to be decompiled and is a password, which can be optionally defined by skin author to protect it from decompilation. The skins can be decompiled using the following command line switch: It is recommended to use default skins as tutorials before trying to create your own skins. So you can always decompile and modify default skins or add your own skins to each of these products. RTSS.exe, D3DOverrider.exe, EVGAPrecision.exe or MSIAfterburner.exe) contains built-in command line based USF skin file compiler and decompiler. normal, focused (hot) and pressed button appearance) and special text header file, mapping these separate bitmap images to each control, defining positions of each control in the skin and so on. USF skin files are compiled from separate bitmap images defining appearance of skin base, appearance of each skin control in all possible states (e.g. \Skins subfolder in the application folder. The skins in all skinned RivaTuner technology based products (RivaTunerStatisticsServer, D3DOverrider, EVGA Precision or MSI Afterburner) are represented by *.USF files stored in the. Here is early draft version of Afterburner skin creation manual: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |