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
Hello, first of all thanks for the plugin, I've been using it for my project and it's been really useful!
Now I've recently updated it to v5 and got an issue when instantiating a scene containing a TileMapDual, here's the description:
Tested Version
Godot 4.3
Issue description
When instantiating a PackedScene containing a TileMapDual node with pre-existing tile data, the instance doesn't automatically update the tiles which are set to their initial state. This might be a visual-only bug, and doesn't happen when the scene is directly run from the editor with Run Current Scene. Any update to the tileset afterwards seems to fix the issue.
From the example scenes, MultipleAtlases.tscn when run directly from the editor
MultipleAtlases.tscn when instantiated from a PackedScene
Steps to reproduce
Open the default TileMapDual-main project
Add some code to instantiate another scene containing pre-existing tile data at runtime from any scene
Run the project
Instantiate the other scene, you will see that the pre-existing tile data isn't properly displayed
I've reproduced the issue by adding some quick code in CursorDual.gd to instantiate MultipleAtlases.tscn (which is the clearest example) from a PackedScene and got 100% repro. Unfortunately I'm not able to upload my MRP for some reason but here's the code I added:
var multiple_atlases = preload("res://examples/MultipleAtlases.tscn")
# Inside _process
if (Input.is_action_pressed("ui_focus_next")):
var instance = multiple_atlases.instantiate()
get_parent().queue_free()
get_tree().root.add_child(instance)
Pressing Tab would instantiate MultipleAtlases.tscn without any tile displayed. Further updates to the tileset by adding a tile (while still running) with the cursor correctly updates the entire tileset
Hope you can help me with this issue, thanks!
The text was updated successfully, but these errors were encountered:
Hey there!
Thanks for sharing. This seems related to #10. I thought it should be fixed by updating the tilemapdual at _ready(), but for whatever reason this does not work. I'm not sure what could be the problem, any suggestion is really welcome.
Cheers!
Thanks for the reply, I'll try to delve deeper in the plugin code when I find the time. Maybe a delayed update could do the trick temporarily but it's definitely not viable long-term.
Hello, first of all thanks for the plugin, I've been using it for my project and it's been really useful!
Now I've recently updated it to v5 and got an issue when instantiating a scene containing a TileMapDual, here's the description:
Tested Version
Godot 4.3
Issue description
When instantiating a PackedScene containing a TileMapDual node with pre-existing tile data, the instance doesn't automatically update the tiles which are set to their initial state. This might be a visual-only bug, and doesn't happen when the scene is directly run from the editor with
Run Current Scene
. Any update to the tileset afterwards seems to fix the issue.From the example scenes,
MultipleAtlases.tscn
when run directly from the editorMultipleAtlases.tscn
when instantiated from a PackedSceneSteps to reproduce
I've reproduced the issue by adding some quick code in
CursorDual.gd
to instantiateMultipleAtlases.tscn
(which is the clearest example) from a PackedScene and got 100% repro. Unfortunately I'm not able to upload my MRP for some reason but here's the code I added:Pressing Tab would instantiate
MultipleAtlases.tscn
without any tile displayed. Further updates to the tileset by adding a tile (while still running) with the cursor correctly updates the entire tilesetHope you can help me with this issue, thanks!
The text was updated successfully, but these errors were encountered: