This may sound obvious but if you uncheck Use Caching - it no longer will use the currently cached textures.
This is an issue because caching is amazing at reducing loading speed, but at the cost of disk space. If you like to reuse a high res texture, it's great to cache it, but if you just leave caching on, it will balloon to hundreds of gigabytes.
Ideal use would be, turn caching on, load the textures you are interested in caching, then disabled caching. This way you limit the massive file size of the cache, by preventing it from caching new textures, but still have the benefit of using the faster speed of the cached textures.
I thought this would be the case, but in testing there was a massive difference in load times between having caching enabled and disabled after having already cached a texture and loading between it and another texture.
This is an issue because caching is amazing at reducing loading speed, but at the cost of disk space. If you like to reuse a high res texture, it's great to cache it, but if you just leave caching on, it will balloon to hundreds of gigabytes.
Ideal use would be, turn caching on, load the textures you are interested in caching, then disabled caching. This way you limit the massive file size of the cache, by preventing it from caching new textures, but still have the benefit of using the faster speed of the cached textures.
I thought this would be the case, but in testing there was a massive difference in load times between having caching enabled and disabled after having already cached a texture and loading between it and another texture.
