Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant add a cell on the same position as an erased scene tile #82597

Closed
TheKassaK opened this issue Sep 30, 2023 · 2 comments
Closed

Cant add a cell on the same position as an erased scene tile #82597

TheKassaK opened this issue Sep 30, 2023 · 2 comments
Assignees
Milestone

Comments

@TheKassaK
Copy link

TheKassaK commented Sep 30, 2023

Godot version

4.2 dev 4

System information

Godot v4.2.dev4.mono - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 Super (NVIDIA; 31.0.15.3713) - Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (16 Threads)

Issue description

It is the continuation of #80658

Now we when use EraseCell() on a scene tile, the instance is removed and the tile disappears BUT after that, if we add a "classic tile" on the same position, we erase this tile and we try to set the scene tile again on the same position, nothing happens.

If I modify the tileset, like TileSet.TileShape = TileSet.TileShapeEnum.Square, it works, the tile I add is displayed well, but it is not a solution because it refresh everything and all my scene tiles instances are recreated

Steps to reproduce

  • use SetCell() to put a scene tile on runtime
  • use EraseCell() to delete that scene tile on runtime
  • use SetCell() to put a classic tile at the same position
  • use EraseCell() to delete that classic tile on runtime
  • use SetCell() to put a scene tile on runtime at the same position => nothing happens

So if you open the linked project, its :

  • Left Click
  • Right Click
  • Space
  • Right click
  • Left Click => nothing happens

Minimal reproduction project

Scene.Collection.issue.zip

@KoBeWi
Copy link
Member

KoBeWi commented Oct 1, 2023

4.2 dev 4

Tested in dev5 and it's fixed. Try updating the engine.

@groud groud self-assigned this Oct 2, 2023
@groud
Copy link
Member

groud commented Oct 10, 2023

I'll close this one as it's likely already fixed. Please comment here if you can reproduce the issue on latest versions.

@groud groud closed this as completed Oct 10, 2023
@akien-mga akien-mga added this to the 4.2 milestone Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants