It is awful to generate dedicated UID files for every script like Unity. I feel the file system in my project is polluted.
Is there any way to disable it in Godot 4.4?
2 Likes
From my understanding its not possible, i think its been tightly integrated into how godot manages resources and the project filesystem. I haven’t tried it out yet but im kind of annoyed by this prospect of updating in general.
If it allows me to just move things around in a file explorer and my game still works, i may change my mind.
There is some movement on this front.
FYI, I tried moving files outside the editor, and all variations broke the scene being moved.
moved attached scene script and uid file to another folder - broke scene
moved folder of scene, with script, to another path - broke scene
I’m a little confused of what the change solved other then moving files in the editor, which already worked, except for hard coded res:// strings in your scripts.
From all the visible errors it seems like the res paths are not getting updated in the .tscn files when the project reloads and fails.
I tried with a new project and it seemed to work.
It seems to really mess up existing project. The uid migration tool helps but I still got a couple of errors here and there that I had to solve manually by opening the affected scene or script and saving it.
For new projects using the new uid system from the start, everything works as expected.
1 Like
What’s the uid migration tool?
I was able to convert a project without issue. It was just moving things afterward, in a converted project, that i ran into issues. I suspect there could be cache in the .godot folder that may need to be cleared from 4.3 to 4.4. i want to test more.
Its real easy to undo the conversion if your using version control.
Dev snapshot: Godot 4.4 beta 3 – Godot Engine.
It’s under the Tool menu. It helps you upgrade your project to use uids.
Ah, thanks, that one was started automatically anyway when I opened my 4.3 project in 4.4 the first time.
I did a little more testing. it seems like if you have nested folders there is a consistent issue that some resource paths will not be updated. I specifically had trouble with images in this regard. but if the image resource is not in a nested folder it works fine.
the second issue is moving folders externally while the editor is running. this caused a lot of issues. but reloading the project, or closing your scene tabs that have moved resources seem to resolve the issue. the editor can be open just make sure related scene tabs are closed when you move folders.