LÖVE

Ah! I've fixed it so it uses the 0.9.2 feature set.

Added an image cache so that loading multiple maps with shared tilesets doesn't cause huge memory usage.

m'man! i bring news of crashes and bugs.

Loading super duper mega maps via your library causes it to crash. worse, it kills the main love thread and the console doesnt registers any logs.

attaching the super duper mega map here so you can looksy it.


PS. the map is created procedurally by a program called worldengine.
More discussion and the actual map is here;
http://forum.mapeditor.org/t/worldengin ... led/896/11

So there are a few things I can say right off the bat.

1) Your chunks are WAY too big! STI just recently supports loading multiple maps so I highly recommend making significantly smaller maps and placing them in a grid using pixel offsets.

2) Your textures are outside the size range for many graphics cards. You should try to make the textures more compact and square if possible, such as 2048x2048 and trim off any unneeded spacing and other junk data.

I believe that your system is simply running out of memory trying to load such an unreasonable map.

> unreasonable

okie.

Thanks anyway.
I tried other tmx files and it does works with smaller files.

Would be nice to get some exact exception though so I can send it to the map maker. He would have liked the feedback on it.
Any idea how i can achieve that?

It's hard to say what a reasonable chunk size limit should be. For instance, Minecraft chunks are 16x16x256. 16x16 is pretty small for a 2D tilemap, though. I would recommend maybe 128x128 tile chunks, or maybe up to 512x512. Anything bigger than that would just be a pain.

Do you think it could be possible to add in a feature that takes in a layer with a custom property eg. table = true then we can grab all tile locations from that layer and add it to a table with x,y coords, something like tabled = map.cTable. It would be for the sake of being able to draw things like Objectives, collectables etc onto the tiled map, load the map into sti, grab the coord data and remove that layer from view, run a for loop to loop through the table of coords for collisions, drawing items individually etc? Just a thought..

Why not just use an object layer?

Had no idea you could use object layers. ;o

HumanRegret wrote:Had no idea you could use object layers. ;o

Yep, you can indeed use an object layer for that.



I keep a palette map of all the object tiles, and then:



boom.