#5, by afrlmeFriday, 15. December 2017, 14:44 7 years ago
Instead of preloading, try to optimize your images & animations as best as you can. Use XnConvert to batch convert your images & animations to webp. Lossy webp has the largest compression, but sometimes the images have artifacts on them in VS, so I recommend using Lossless webp instead as those are always displayed correctly & still have about 1/3 to just under 1/2 file size difference of the png file(s). Smaller file sizes for the images/animations means the images will load in faster which is great for people running potato rigs & laptops.
Try to crop your animations & images too. Images with transparent backgrounds the size of the scene/game default resolution might not be much larger in file size than a cropped version, but they will load in slower. Also never use duplicated image frames for animations to display the same frame for x time, instead use the built in system for manually adding a custom pause/delay value for specific frames.
For animations that should play forwards & then backwards, you could either use Lua script to do that or alternatively just manually insert the forward playing frames one at a time or play the animation forward, then use the play animation action part to play it in reverse immediately afterwards.
There's no need for preloading if you optimize efficiently.