Ah in that way Tilengine is the same as old game hardware, as far as drawing the tiles per line by fetching the tiles as it refers to the level map, and not from a giant bitmap. That's really awesome.
I bet other 2D retro games just use giant bitmaps - unless they use the modern 3D acellerated technique of making the level out of a mesh where each tile is a quad, referring to a texture atlas. Much more efficient than a giant bitmap. I would say it's still not as efficient as the way Tilengine does it, at least if you try to push it to stupidly huge levels. If a float is typically 4 bytes (which is already the memory size of your tile), there are 3 of those for each vert, and 4 verts for each quad. Faaaar less efficient. Of course how much that really matters is dependent on the game and the target platform. On desktops, I'd guess that you'd be hard pressed to reach any sort of limitation for 2D levels on even the oldest accelerated video card you're likely to encounter. But if you were to keep scaling up the level size, that vert count would be what slows down the card first... whereas I assume it probably doesn't matter as much how big the level is in Tilengine?
Yes, I am looking forward to using Tilengine for something
I have a 2D retro game coming up but I want it released on mobile so I might be better off sticking to Godot with its touchscreen support and deploy to iOS built in. When I do have a 2D retro game come up that doesn't require mobile, the main thing I'll have to address is setting up a Hackintosh, or a VM like you have. Got to support those Mac users.
I bet other 2D retro games just use giant bitmaps - unless they use the modern 3D acellerated technique of making the level out of a mesh where each tile is a quad, referring to a texture atlas. Much more efficient than a giant bitmap. I would say it's still not as efficient as the way Tilengine does it, at least if you try to push it to stupidly huge levels. If a float is typically 4 bytes (which is already the memory size of your tile), there are 3 of those for each vert, and 4 verts for each quad. Faaaar less efficient. Of course how much that really matters is dependent on the game and the target platform. On desktops, I'd guess that you'd be hard pressed to reach any sort of limitation for 2D levels on even the oldest accelerated video card you're likely to encounter. But if you were to keep scaling up the level size, that vert count would be what slows down the card first... whereas I assume it probably doesn't matter as much how big the level is in Tilengine?
Quote:If you use tilengine for your next project, you'll have super easy scroll and low memory footprint with graphically rich huge maps
Yes, I am looking forward to using Tilengine for something
I have a 2D retro game coming up but I want it released on mobile so I might be better off sticking to Godot with its touchscreen support and deploy to iOS built in. When I do have a 2D retro game come up that doesn't require mobile, the main thing I'll have to address is setting up a Hackintosh, or a VM like you have. Got to support those Mac users.