A `TilemapChunk` should accept a grid arranged tileset

[hxYuki]

What problem does this solve or what need does it fill?

It is natural that you would draw together the tiles in tileset that appear adjacent to one another on the map. That helps you to create seamless tiles.

What solution would you like?

Process the tileset by grid instead.

What alternative(s) have you considered?

The bevy_ecs_tilemap exports a Material trait for customized rendering.

Additional context

One tileset asset from Monogame's tutorial:

Here's my local solution for reference. Disclaimer: I am not familiar with WGSL. It is authored by copilot.

[greym0uth]

I haven't really touched much of the new tilemap stuff that has landed in bevy yet, but at first glance this seems like something that should live in the ImageLoaderSettings rather than modifying the internals. The ImageArrayLayout enum seems a little rigid in that it only allows for a vertically-stacked image. Modifying this to instead convert a grid to an array so that the underlying texture2DArray can still be used without having to pass additional uniforms to the shader.

What I'm imagining here is replacing ImageArrayLayout with ImageGridLayout. A vertically-stacked image is just a grid with one column so it would fit in pretty well.

bevy/crates/bevy_image/src/image.rs

Line 1369 in 3cf98a6

pub fn reinterpret_stacked_2d_as_array(

could then be refactored to convert the grid to an array to handle this new type. This method would be breaking and require people to migrate, so there is some potential in adding new property to the ImageLoaderSettings but seems like managing two different properties that do such similar things would be redundant.

I'm curious to what others, or maybe a SME on this topic's, approach would be. I'll maybe drop a comment in the discord and recollect here.

[alice-i-cecile]

I agree with @greym0uth's analysis: this is the sort of solution I would prefer to see.