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

Bilateral link between a resource and a scene corrupt the resource file #97144

Closed
gravit22 opened this issue Sep 18, 2024 · 1 comment
Closed

Comments

@gravit22
Copy link

Tested versions

I don't know about this. I belive it is present starting with Godot 4.0. Before there weren't resources to test.
Tested version Godot 4.3

System information

Godot v4.3.stable - Ubuntu 24.04.1 LTS 24.04 - X11 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1060 3GB (nvidia; 535.183.01) - AMD Ryzen 9 3900X 12-Core Processor (24 Threads)

Issue description

Bilateral link between a resource and a scene is present and scene is open, if Godot is closed and then the project is reopened it corrupts the resource file. After that the scene with corrupted resource file can't be opened, the only way to deal with it is to delete and create another resource. But then again, once scene is open and editor and Godot editor is closed and reopened, the issue have chance to appear again.
I understand that it is kinda bad link, when both files link each other, but it doesn't affect running performance, and since that I belive it should be allowed, and do not cause such issues

Steps to reproduce

Current project already contain corrupted file. If you want to test the process, just delete the resource tres file, then create another one, give it link to another scene, and that scene should have link to the resource. Then when Bug scene is open in editor, close it, and then reopen the project. There is a great chance that the resource will be corrupted

Minimal reproduction project (MRP)

Bug report.zip

@AThousandShips
Copy link
Member

This is a known limitation, see here, here, here, and here

Please see this proposal for this topic, but this is a known and documented limitation, so closing, but thank you for your report:

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