Asset File Manager
Manages the resource files.
It minimizes loading time in as much as possible by caching download files in the device, pooling loaded files into the system memory, etc.
File load diagram:
|File IO Manager||Management object for reading in and writing out files. Generally configured automatically.|
|Time Out Download||Time out time when downloading (seconds).|
|Auto Retry Count On Download||Number of automatic retries when there is a download error.|
|Load File Max||Maximum number of files to load simultaneously.|
|Max Mem Size MB||Maximum memory size used for management. If this amount of memory is exceeded, it unloads the files not currently in use.|
|Optimized Mem Size MB||Target memory size when unloading files. Does its best to unload files until it reaches that memory size.|
|Cache Dictionary Name||Directory name where the cache files are stored.|
|Cache Tbl File Name||Name of cache management file.|
|Is Out Put Debug Log||If set to ON, it outputs a debug log.|
|Is Debug Cache File Name||If set to ON, it outputs the cache filename to the debug log.|
|Is Debug Boot Delete Cache Text And Binary||If set to ON, it deletes text and binary files at startup time.|
|Is Debug Boot Delete Cache All||If set to ON, it deletes all cache files at startup time.|
|LoadSetting||For each file type, it configures whether or not to load files.
Utage files can be handled in a number of ways, such as by loading them locally or downloading them from the server, so this setting can be configured here.
This is generally configured automatically from AdvEngineStarter.
Please note that our memory size calculations are inaccurate. They are only used as targets for file unload timings and are by no means reliable.