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
I was having difficulty utilizing the relativePath property exporting a TileMap when, upon testing, realized it would properly set the ext_resource in the final .tscn if I specified the exact path to the tileset (e.g. /Assets/Maps/Town/town_map.tres).|
This did not happen with Tilesets, as the exported .tres properly linked to their source image without projectRoot or relativePath needing to be specified.
I dug around the source code only to find that tileset.asset.fileName in setTilesetsString() returned null when tileset.asset returned a proper object reference, resulting in relativePath only working if it included the tileset file name as well.
The text was updated successfully, but these errors were encountered:
I was having difficulty utilizing the
relativePath
property exporting a TileMap when, upon testing, realized it would properly set theext_resource
in the final .tscn if I specified the exact path to the tileset (e.g./Assets/Maps/Town/town_map.tres
).|This did not happen with Tilesets, as the exported .tres properly linked to their source image without
projectRoot
orrelativePath
needing to be specified.I dug around the source code only to find that
tileset.asset.fileName
insetTilesetsString()
returned null whentileset.asset
returned a proper object reference, resulting inrelativePath
only working if it included the tileset file name as well.The text was updated successfully, but these errors were encountered: