It happens with every image, not just larger ones. I used a large one because it was easier to see the loading time.
After rereading and thinking about it Iâll admit that reloading my âMain Screenâ with its 1.89 MB background feels a bit long.
Considering that image is one of the first image to be loaded at the start, it should remain in cache since every image after its screen is unloaded is procedural or part of one of Niftyâs screen.
ponders
Looking at the issue of phroot in another thread⌠Maybe nifty changes the settings of the image (e.g. disables mipmaps) which would then invalidate that file for the cache?