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

ResourceLoader can't find uid of packed scenes in exported builds #79009

Closed
bodonkerhoderos opened this issue Jul 4, 2023 · 3 comments
Closed

Comments

@bodonkerhoderos
Copy link

Godot version

v4.0.2.stable.arch_linux

System information

Manjaro Linux

Issue description

ResourceLoader.get_resource_uid returns -1 (not found) when provided a res:// path to a packed scene during runtime in exported builds that are not run in the original project directory. i expect it to return the uid of packed scenes at runtime.

it returns a uid for icon.svg even on exports. it returns a uid for packed scenes when run in the original project directory. it fails to find a uid when exported to linux, android, and web platforms (likely all platforms). it also fails to find it when the pck is embedded.

Steps to reproduce

  1. call ResourceLoader.get_resource_uid with the res:// path of a packed scene.
  2. export to any platform
  3. run exported project anywhere else

Minimal reproduction project

resource_uid_not_found.zip

@AThousandShips
Copy link
Member

AThousandShips commented Jul 4, 2023

While supporting UIDs is a good idea probably they're normally intended for the editor, and not for export, their main purpose is to handle renaming of files in the editor

Also there might be issues related to conversion to binary, might be that the scene paths converted work but not the original paths

@AThousandShips
Copy link
Member

AThousandShips commented Jul 4, 2023

@AThousandShips
Copy link
Member

AThousandShips commented Jul 4, 2023

Thank you for reporting

@AThousandShips AThousandShips closed this as not planned Won't fix, can't repro, duplicate, stale Jul 4, 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

2 participants