I guess i just understood your post as löve supports loading TGA files, not that it supports saving them. Edit: According to the wiki, saving tga might have been added, wasn't aware of that. :v Yeah that's what I meant - and primarily because the original poster also wondered about the long time sa...

... That's nice and all but i'm pretty sure the question was about saving images with specific formats, not what types does löve support loading. :3 That's why I wrote TGA and in addition some other info why it may be at least a easy usable additional format wrt to the time required to save the ima...

TGA works too ... I just noticed this a very few months ago and now use it during development as both, writing (from within my asset handling tools) and loading (when running the game) is much much faster on my system. It turned probably around >= 5 seconds of startup time into a blink which doesn't...

It seems as if I somehow got the 5th key. Not sure if it's an issue on my side but I can't download/install using itch. I guessed the key was taken/something went wrong and didn't try anything else but it seems that it's still somehow linked to my account and I can download it manually using a brows...

During development I recently moved over to tga as those load a lot faster on my pc. Originally I used tga because I worked/debugged my asset pipeline/tools and, obviously writing pngs is a lot slower than just dumping to uncompressed tgas. Out of curiosity I tried those in the game and the startup ...

I got the 8RKFX-P0Z8A-0Q00K one ... thanks a lot.

Love the animation of the character, triggers very old memories (Loderunner on the C64)

Will give it a try asap.

It would help if you give us some numbers and more details about your canvas sizes and the nature of your game. Is it a single screen or a scrolling game (because you created your batches on load and did not change them anymore)? How many tiles per layer, size of the tiles, size of the tileset (i.e....

The devil is in the detail. To call into constructors of parent classes you need to call them like so ClassB.super.new( self, x ) This is, because ClassB etc. are class instances and when you use super:new and not use the explicit self of the current scope, you call those upper constructors with the...

Never mind ... life's to short for these nosense.

I'd love to hear an actual reason with, maybe an explanation why and how something else works the same way, instead of just a phrase of opinion