Tilemap Palette, needs better ways to populate

When you drag a whole tiles that are generated by say a sprite sheet, you would generally want to keep the formation in which the original sprites were drawn as. So for example, if you had 32x32 tile in 512x512 map, then you would want to keep 16x16 tiles formations just as if it was drawn originally in palette. But when you drag them into the palette, it creates like 17x16 sets making the tiles to be put in offset to what was originally drawn for. This is very awkward and not very friendly to work with, as you have tried to organize the original sprite so that it is easier to work with.

My question is,

1. Why does it do this?
2. Can this some how be improved so that it tries to keep the original formation?

Putting the tile one by one in palette is just not an option.

 

Try setting a custom size when slicing the tileset in the sprite editor. Perhaps its set to automatic which isn't correcting selecting the tile sizes.



Good luck!

 

Unfortunately, this is not the case, I am slicing the sprite correctly. I can even see all the tiles in the palette, it is just that their formation is just not good. I cant understand the logic behind how and why Unity place them like this way.

 

Right, so dragging texture asset does indeed work as expected. This is some what not very clear that you need to do this, because when you drag the texture for the first time, you will need to split them, and after splitting them, I thought dragging individual sprites split into the palette in order to create the tile assets. After creating tile assets I thought dragging them into the palette is going to work. Never thought about dragging the texture asset, because well, it is texture... not sprite. (because I thought in order to create tile assets I need to drag the sprite , not texture)

I think many of us are confused at this. If this information is not documented, then it should be. I don't know if it has already and I didn't know about it...

thanks.

 

Also even if tile assets were dragged in, if it seems like it can do exactly 16x16 or so, then it should try default to fit that instead of doing weird 17x16. Defaulting to 17x16 when it can do 16x16 exact is just beyond anyone's understanding....