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

Entire scenes disappearing with MissingNode error #99863

Open
Athsmar opened this issue Nov 30, 2024 · 5 comments
Open

Entire scenes disappearing with MissingNode error #99863

Athsmar opened this issue Nov 30, 2024 · 5 comments

Comments

@Athsmar
Copy link

Athsmar commented Nov 30, 2024

Tested versions

Godot v4.3.stable

System information

Godot v4.3.stable (77dcf97) - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 32.0.15.6094) - AMD Ryzen 7 2700X Eight-Core Processor (16 Threads)

Issue description

What seems like for no reason at all, random scenes in my file will completely disappear and turn to MissingNode. If it weren't for git there would be no way to get scene back. This is very bad. It happened to me twice and very far apart. Just reporting because no one has an answer to it online.

Image

Steps to reproduce

I have no idea how to reproduce, it seems to be happening randomly. My project is connected to GitHub desktop and it is a larger project.

Minimal reproduction project (MRP)

N/A

@huwpascoe
Copy link
Contributor

Next time it happens, would you be able to share the .tscn file?

@Mickeon
Copy link
Contributor

Mickeon commented Nov 30, 2024

I do feel bad, but this is a very murky bug report. People that may try to fix this bug don't have any point of reference to begin with. Please try to provide more information.

@sandstormyun
Copy link

I had the same problem,the whole scene turned into the one single node "MissingNode",and I opened the .tscn file in txt format,it's just like this.

[gd_scene format=3 uid="uid://daphl2wep6gnl"]

[node name="MissingNode" type="Object"]
_import_path = NodePath("")
unique_name_in_owner = false
process_mode = 0
process_priority = 0
process_physics_priority = 0
process_thread_group = 0
physics_interpolation_mode = 0
auto_translate_mode = 0
editor_description = ""
script = null

@Athsmar
Copy link
Author

Athsmar commented Dec 1, 2024

Next time it happens, would you be able to share the .tscn file?

I will try, thanks

@molingyu
Copy link

molingyu commented Dec 2, 2024

I had the same problem,the whole scene turned into the one single node "MissingNode",and I opened the .tscn file in txt format,it's just like this.我遇到了同样的问题,整个场景变成了一个单独的节点 “MissingNode”,我打开了 txt 格式的 .tscn 文件,就是这样。

[gd_scene format=3 uid="uid://daphl2wep6gnl"][gd_scene 格式=3 uid=“uid://daphl2wep6gnl”]

[node name="MissingNode" type="Object"][节点名称=“缺失节点” type=“对象”] _import_path = NodePath("")_import_path = NodePath(“”) unique_name_in_owner = false process_mode = 0 process_priority = 0 process_physics_priority = 0 process_thread_group = 0 physics_interpolation_mode = 0 auto_translate_mode = 0 editor_description = "" editor_description = “” script = null 脚本 = 空

Can you share the .tscn file before it is overwritten by the wrong data?

This may be because your root node cannot find its tagged type when parsing (not registered in ClassDB).

If you use a custom type as the root node. When the corresponding script is renamed, the type information recorded in the resource file may not match the current information.

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