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

After Renaming Project - Certain .tscn cannot be loadrd #82515

Open
Lernwilliger opened this issue Sep 29, 2023 · 2 comments
Open

After Renaming Project - Certain .tscn cannot be loadrd #82515

Lernwilliger opened this issue Sep 29, 2023 · 2 comments

Comments

@Lernwilliger
Copy link

Godot version

4.1.1 Stable mono official

System information

Windows 10

Issue description

When I open the project after renaming. Some .tscn files are invalid. Before I renames the project everything worked fine.

If I open the tscn files in the explorer on some tscn, the images are like a blackscreen.
Warnung:
Szenendatei "name.tscn" scheint ungültig / fehlerhaft zu sein.

The errors that occure:
opening the .gd files in the editor did not help

Index out of bounds not only size 5 also other size numbers occure.

16959758761116945279359397479450

16959760277771015567340578049843

16959763377142669902820474492976

Steps to reproduce

I renamed a Project with many .tscn files. Now I cannot open some .tscn. I can only open them if I rename the project back to the original name, but if I do so.
Some other .tscn files are invalid to open.

Minimal reproduction project

I tried to make a minimal project by renaming but could not reproduce the issue. Maybe the issue occures on larger projects.

@Lernwilliger
Copy link
Author

What I found out is: renaming the project with the same name does fix it sometimes on startup. So that no errors occure

@Deozaan
Copy link

Deozaan commented Oct 1, 2023

4.1.1 has some serious bugs that can cause scene corruption when renaming files. The good news is that the bugs have been fixed in 4.2-dev5. But the bad news is that it appears there are no plans to back port the fixes to 4.1 because it's a big change that might introduce other regressions. My advice is to use version control software and always commit your work before renaming anything so you can revert if things break.

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

3 participants