I'm playing around with animated textures at the moment, so I'm paging up animated sequences on to texture pages.
The program I'm using to stitch the frames together seems to make them into one row, making one loooong bitmap (4096 x 64) rather than something a bit more sensible (512x512). The long file works perfectly fine in Blitz3D, but I'm curious as to whether this will be any less efficient or cause problems for low-spec machines.
How exactly does Blitz handle its animated textures? Does the LoadAnimTexture command do something clever with the texture?
The program I'm using to stitch the frames together seems to make them into one row, making one loooong bitmap (4096 x 64) rather than something a bit more sensible (512x512). The long file works perfectly fine in Blitz3D, but I'm curious as to whether this will be any less efficient or cause problems for low-spec machines.
How exactly does Blitz handle its animated textures? Does the LoadAnimTexture command do something clever with the texture?