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

Main scene fails to load for exported projects #100084

Closed
levidavidmurray opened this issue Dec 6, 2024 · 5 comments
Closed

Main scene fails to load for exported projects #100084

levidavidmurray opened this issue Dec 6, 2024 · 5 comments

Comments

@levidavidmurray
Copy link

levidavidmurray commented Dec 6, 2024

Tested versions

  • Reproducible on master

System information

Godot v4.4.dev.mono (eb51030) - Windows 10.0.22631 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; 32.0.15.6094) - AMD Ryzen 7 2700X Eight-Core Processor (16 threads)

Issue description

I was getting the following error when launching an exported project in 4.4dev5, which instantly crashes the application:

ERROR: No loader found for resource: res://uid:/cu2wmlv7867bo (expected type: )
   at: ResourceLoader::_load (core\io\resource_loader.cpp:327)
ERROR: Failed loading scene: res://uid:/cu2wmlv7867bo.
   at: Main::start (main\main.cpp:4214)
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
   at: ObjectDB::cleanup (core\object\object.cpp:2342)

Issue 1

Changing resource values such as application/run/main_scene or application/boot_splash/image in Project Settings results in an automatic conversion from their res:// paths to their uid:// paths (this is the value that's stored in project.godot)

Issue 2

The bit of code that determines the main scene path doesn't appear to be expecting a uid:// path. I've tracked down the code that results in res://uid:/cu2wmlv7867bo to main.cpp:4161.


I'm not exactly sure if this code should handle the uid:// path, or if these resource paths saved under project.godot should be reverted back to their res:// paths.

In any case, manually hardcoding the paths to their res:// paths in project.godot has temporarily fixed the issue for me.

Note

I actually don't remember if this was the exact issue I was facing when building on 4.4dev5. This is an issue on latest master that I ran into after having similar issues on 4.4dev5. I built latest master because I thought this very similar issue (#99151) might've been fixed.

Steps to reproduce

  1. Create a project in 4.4dev5
  2. Export that project
  3. Run the project

Minimal reproduction project (MRP)

N/A

@levidavidmurray levidavidmurray changed the title Main scene fails to load for exported projects in 4.4dev5 Main scene fails to load for exported projects Dec 6, 2024
@IsaacMarovitz
Copy link

I also started experiencing this issue in dev5, which persists in dev6. Seen reports from several others in the Godot Discord also.

@IsaacMarovitz
Copy link

I managed to work around this by manually editing project.godot to use a res:// path.

@IsaacMarovitz
Copy link

FWIW, this should absolutely be included in the release blockers list

@CSLRDoesntGameDev
Copy link

i've come across the same issue, and the project.godot did fix it.

@akien-mga
Copy link
Member

Fixed by #100408.

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

5 participants