I’m afraid I can’t help, this sounds like something off with either your code outside of what you’ve shared, or the library you’re using to load or draw the tilemaps. You should ask in the community for the library or engine. Or, keep at it with the debugging - trying things to try to figure out in what way exactly it’s wrong, which may help you find where the problem is.
You mentioned that a video you watched didn’t have this issue, perhaps they might not have used any oversized tiles, maybe the library/engine doesn’t handle those the same way Tiled does. A possible workaround is to load your background tileset with a tile size equal to your map’s tile size, and place each background section as a bunch of small tiles instead of as a single large tile? Or, if it’s just a repeating image, perhaps you can make it an Image Layer like the other background layers.
1 Like
Thanks for your feedback, I will try to find the cause and will tell you what the real problem here is (or no :v).
Thank you very much
1 Like
You are right, if I put the components into a tile layer but it is sparse, it will lead to the wrong render. This made me turn into photos and put them myself.
Are you sure it’s the sparseness that’s the issue, rather than the oversized tiles? The Ground layer is also mostly empty, but seems fine, presumably because all its tiles are small. If the size is the issue, then the method I wrote above of using the large backgrounds as small tiles should work. Or is that what you meant into “turn into photos”? I have no idea what that means.
I mean, my tiles are oversized. I typed wrong and got you stuck. You can see that I have a Grass layer and I want to fill it with tile (grass), but their width is over than the map’s width, so I had the error render.