Having trouble importing a very primitive map without tileset

[mydumpfire]

I'm trying to import an extremely simple LDtk map. There's just one integer grid layer with one grid value and an entity layer with two entities. No tilesets or anything, just plain colors. But it's just not importing correctly:

Here's the repo: https://github.com/mydumpfire/ldtk_topdown

It's just a ~50-line main.rs. The map is in assets/topdown.ldtk. Any help will be appreciated.

[Trouv]

Thanks for sharing the source code, I ran it and got expected results.

What happens if you run the examples in this repo? What about the examples in bevy_ecs_tilemap?

[mydumpfire]

I've managed to fixed it by using a proper tileset/atlas, instead of IntGrid colors.
I'll also try running the examples, but since they all use atlases, I expect them to fully work.
Btw, by "expected results", did you mean that you got something working or did you get a result similar to my screenshot?

[Trouv]

By expected results, I mean that it looked correct on my machine. IntGrid color rendering is implemented very differently to normal tile layers so it's not too surprising that there'd be some issues on some machines. A single white image is generated and treated as a single-tile tileset, and the colors are adjusted from there using bevy_ecs_tilemap components.

I wonder what part of that solution is breaking for you here. Maybe a plain tilemap rendered with bevy_ecs_tilemap using a single-tile tileset would have similar issues..

[Trouv]

What are your specs, OS, and have you updated your graphics drivers recently?

[mydumpfire]

I'm on Linux, with:

{ 
    name: "NVIDIA GeForce GT 635", 
    vendor: 4318,
    device: 4736, 
    device_type: DiscreteGpu,
    driver: "NVIDIA",
    driver_info: "470.199.02",
    backend: Vulkan
 }

It's an old card with a legacy driver. It's still weird that this happens though. I've played a few games in this machine and I have yet to see any problems with it.

I'm also having problem with my character sprite sometimes looking weirdly corrupted, but it's usually gone the next time I launch the binary (without rebuilding). I still have yet to test the release build though, I wonder if it would yield different results.

[mydumpfire]

EDIT: I think this is an upstream issue: bevyengine/bevy#4053

Getting the corruption again, this time it's not going away:

Zoomed in:

The original asset: