You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug in calling get_used_rect() after creating multiple layers in TileMap.
Draw area not covered (0, 0) coordinates, but using get_used_rect () to obtain data for [P: (0, 0), S: (3, 3)], expect is [P (1, 1), S: (2, 2)].
In minimal reproduction project, in the main scene, TileMap1 has only one layer and TileMap2 has two layers, They are in the same position and draw the same content, But calling get_used_rect() gets a different value.
Note: This bug still exists in dev4, but not in dev1.
Steps to reproduce
In minimal reproduction project, running the main scene, you can see the data from TileMap1 and TileMap2 calling get_used_rect() in the console.
xlljc
changed the title
[Godot4.2dev2] When tileMao has multiple layers, the data returned by calling get_used_rect() is problematic.
[Godot4.2dev2] When tileMap has multiple layers, the data returned by calling get_used_rect() is problematic.
Sep 7, 2023
Godot version
4.2 dev2
System information
windows10
Issue description
There is a bug in calling get_used_rect() after creating multiple layers in TileMap.
Draw area not covered (0, 0) coordinates, but using get_used_rect () to obtain data for [P: (0, 0), S: (3, 3)], expect is [P (1, 1), S: (2, 2)].
In minimal reproduction project, in the main scene, TileMap1 has only one layer and TileMap2 has two layers, They are in the same position and draw the same content, But calling get_used_rect() gets a different value.
Note: This bug still exists in dev4, but not in dev1.
Steps to reproduce
In minimal reproduction project, running the main scene, you can see the data from TileMap1 and TileMap2 calling get_used_rect() in the console.
Minimal reproduction project
TestTileMap.zip
The text was updated successfully, but these errors were encountered: