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

Empty scenetree with unsaved scene #92214

Closed
ultsi opened this issue May 21, 2024 · 7 comments · Fixed by #92253
Closed

Empty scenetree with unsaved scene #92214

ultsi opened this issue May 21, 2024 · 7 comments · Fixed by #92253

Comments

@ultsi
Copy link

ultsi commented May 21, 2024

Tested versions

  • master with custom commits
  • Godot v4.3.dev6

System information

Godot v4.3.dev6 - Ubuntu 20.04.6 LTS (Focal Fossa) - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) () - AMD Ryzen 7 5800X 8-Core Processor (16 Threads)

Issue description

Empty scenetree on unsaved scene, when switching from non-initialized unsaved scene.

Steps to reproduce

  1. Create new scene A
  2. Add a 3D root node
  3. Create new scene B, don't create a root node
  4. Switch back to scene A [unsaved]

Scenetree should now be empty.

The empty scenetree can be fixed by switching to a saved scene and then back, then the unsaved scenetree appears again.

Minimal reproduction project (MRP)

N/A

@AThousandShips
Copy link
Member

Can you replicate this on an unchanged branch? The commit you reference isn't part of the repo

@ultsi
Copy link
Author

ultsi commented May 21, 2024

@AThousandShips yes was able to repro on Godot v4.3.dev6

@AThousandShips
Copy link
Member

And on latest master as well? If you're able to test

@ultsi
Copy link
Author

ultsi commented May 21, 2024

Yeah sure, let me recompile

@ultsi
Copy link
Author

ultsi commented May 21, 2024

empty-scenetree-bug.mp4

Here's a simple repro video

@AThousandShips
Copy link
Member

I can confirm on latest master

@ultsi ultsi changed the title Empty scenetree Empty scenetree with unsaved scene May 21, 2024
@matheusmdx
Copy link
Contributor

This is a regression caused by #86605:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants