Does ResourceInteractiveLoader even work?

exuin

Followed tutorial here. Loading bar is just a simple ProgressBar. However, it doesn't update and just stays there frozen. I added a print statement to see if the progress function is actually being called and it is, but it's only printing once the scene has been loaded, so it really defeats the point of a loading screen.

DaveTheCoder

I ran into the same problem, still unresolved: https://godotforums.org/discussion/25077/background-scene-loading/p1

exuin

Darn. Well, I did find a thread that said that Resource Loading was changed for 4.0 though.

Megalomaniak

Well, i don't know, I did get it to update in my example in the other topic, but only a couple of steps. So progress is somewhat visible to the player but it's not a smooth progress.

exuin

Perhaps it's easier to just load in a new thread and then create a fake loading screen?

DaveTheCoder

In the topic I linked, I mentioned attempting to do the loading in a new thread, and it didn't solve the problem. But it could be a mistake in my code.

exuin

Yeah I tried loading a new thread too but then I realized that I couldn't get the progress for the loading bar.

DaveTheCoder

At least it sounds like it will work in Godot 4, based on that github link you posted. At my speed, Godot 4 will be released before I manage to publish anything. ;)

Bimbam

Sounds familiar, fairly sure for me it was because all my resources were embedded in very few .tscn files (making the resource loader have few jumps and long pauses between them).

Saving branches as their own .tscn and referencing .gltf models directly instead of resaving resolved it for me (and also makes saving/loading significantly faster. Basically don't use .tscn format to hold 3d models....ever).

DaveTheCoder

referencing .gltf models directly

By right-clicking on the .glb/.gltf file and selecting Instance?

Megalomaniak

I would expect so, yes.

Bimbam

I don't think the .gltf comment is necessarily related to your issue, but basically, this is good:

The children while greyed out can still be moved about as required and results in a .tscn file that is 188 bytes and rapid to save/load (sub 1s).

I think the main thing that irritated me was changes to materials/collision shapes would not persist through new imports of the same scene, so I used to think it was better to 'Make Local' the model/meshes. Then it looks like this:

The problem is this is now a ~218mb .tscn file and takes about 11s to save/load (mostly longer saving, but marginally longer loading too).

For whatever reason .gltf format (and I imagine obj/fbx etc.) is just faster and smaller, so now I try to do as much as possible in Blender (including -colonly collision shapes) and basically don't move or alter anything in Godot, just reference the original imported file. Materials inevitably need to be redone in Godot half the time just because Blender != Godot I guess, so whenever I edit them I save them to a separate directory so I can restore them after next batch of overwrites.