The drawback is of low impact to the the current design since the significant pixel coverage data is stored in memory. The 2Q's intended implementation may not easily allow for extra values in the cache system to determine factors of pixel coverage. Only drawback noticed so far is that it appears to carry a specific implementation, but this drawback will need to be confirmed. Benefits include that the 2Q method has already been studied by other groups and that it is possible to fit this method into the current design. However, there is significant data to move to a new system for the method to determine the storage time. At this time, the format of the medium is still under discussion. Beyond the view of the texture cache, there is the method to which to determine how long a texture is stored in the cache and there is medium format of the textures being stored. In the discussion of the texture cache has, it is apparent that there are two separate issues involved. all of the texture minus the header Analysis U32 mTime // unused TODO: create separate structure without this entryīody of the texture, i.e. S32 mSize // size of texture body stored on disk Old entries are purged until 10% of the disk cache is available.Only the latest entry for each texture is retained.On startup and when the disk cache becomes full, textures.cache is parsed.This prevents the disk cache from having to explicitly keep track of which entries have bodies stored in the main cache.When a texture is written to the cache, a new EntriesInfo struct is appended to the file regardless of whether or not an entry already exists.This file consists of a an array of EntriesInfo, except mSize is the body size, not the total image size.cache/textures/texture.entries (Not used with cache version 1.2).j2c file) The main "body" cache consists of an entries file and 16 subdirectories S32 mBodySize // size of body file in body cacheĪrray of 600 byte entries (first 600 bytes of. S32 mImageSize // total size of image if known S32 mSize // total size of image if known (NOT size cached) Currently all textures in Second Life are stored in the JPEG2000 compressed format.The results are given through a Responder class when they are ready.Requests to read or write to the cache are processed in the priority given.The body (minus the header) for a limited (by the cache size) number of entries is stored in textures//textureid.The header for each image (enough to identify the size and load the first mip level) is stored in texture.cache.
A list of all files in the cache is stored in texture.entries.Stored in a 'textures' subdirectory in the cache directory, specified in the preferences.This is a read-only cache which contains common textures shipped with the Viewer.Located in the Second Life/skins/textures directory.There are two different disk caches used by the Second Life Viewer:.2.2 The main "body" cache consists of an entries file and 16 subdirectories.