Yes, that’ll suffice unless you’re scaling down a lot and using MIP mapping.
Yes, that’s the whole point of the border. It has to match the colors of the pixels at the edge so that you don’t see your edge pixels blend to another color. Because it’s tedious and error-prone to set up such a border, it is something that you should automate by code, or look for a tool that can already do this for you.
No. Only the size of the whole tileset image matters, depending on the hardware.
Based on what you described at 2, you’d specify a 1px margin (the space at the tileset border) and 2px spacing (the space between the tiles).
Finally, note that when you’re not actually scaling your map, you can also avoid the whole problem by making sure to render it aligned to pixels.
Oh I am sorry, I used the wrong picture, because I created a new folder.
Basically this fixed issue 1.
(I can see that whenever there was the background shining through, there is the border pixel as you said)
This leaves nme with a very small issue that sometimes the lines around my tiles are looking 1px bigger (but thats hard to tell on smaller devices)
My performance issue was not fixed. It is kind of choppy, but maybe thats a ghosting effect of the screen
Yes sry I edited my previous answer while you very answering too…
1 last question… If im running my app now on Android, sometimes a 1px black line is shown like this, sometimes it looks like the 1px thick line is 2px - it is the conversion from from 1px to 1 screen px…
It won’t, because as was visible in screenshots @captainflyaway posted before (but then deleted in an edit), you will have blending going on to transparent pixels, causing the background of your tile grid to show through.