I was looking into the issues tab of godot for an unrelated issue, and ran into this: github.com/godotengine/... It sounds like the issue you're experiencing. They seem to believe it's a driver issue, and that running godot with --single-window fixes the issue for now. Worth a shot \o

Not sure 🤔 my gpu on the fedora is nvidia, and I’m using KDE Plasma as a desktop (Wayland)

My main machine is running fedora 42 but I bounce around to windows 11, osx, and cachyos in different machines. Haven’t noticed any issues in any of them with my current Godot build based on 4.5.1stable

Actually I've been using 4.5.1 stable, In the github repo there's a bunch of branches with different versions/iterations. I haven't noticed anything less stable with 4.5.1 O.o has been pretty good to me, but I haven't been doing a lot of VR development lately.

This is what it looks like in practice, you can see there that it's treated as a mesh itself like the .obj files are, so you can just plop it into a scene or into an existing meshinstance3d. You can also toggle save to file for it to create a .mesh file if you want to get rid of the .glb later

It's a part of my catch-all module of my own improvements and utilities: github.com/DanielSnd/Go... it's the "ResourceImporterGLBasMesh", unfortunately since it is a module it does require re-compiling the engine with it. But you could take the cpp files and make it into a gdextension easily enough

If it’s props and such (not rigged objects), I made a custom importer for glb that works akin to the obj importer. It makes life so much easier 😅 it also has little QOL features like resizing/changing position/rotation offset, optionally reconnecting materials to existing ones and calculate normals

Are you using CharacterBody's move_and_slide() for the movement? I've been running into some performance issues with it when characters are moving close together like that ;o

Thanks ^^

Thank you 😊 it’s been quite the journey.

Yeah can’t see a way you avoid manually writing it in the inspector, either with meta variables or a child node that holds the data in each of them. 😰

How is the information there being generated? Is it procedural or set manually? Is it different for literally every instance? My first thought is meta variables but they’re not super easy to write manually in the inspector as you also pointed out. But could be made easier with a custom plugin for it

What kind of meta data?

That’s it, no catch :) and it’s glorious! If you call that function you made that has an await with an await ahead of the call, you can wait for that function to end too, it’s awesome ^^

That is so incredibly cute, I love it. It looks gorgeous. Great job!

In the debugger panel, Misc. tab, whatever control is taking the mouse click shows up there. Next time you have to deal with it will be easier 😂 you’re welcome

I have been using this one, works well :) github.com/godotengine/...

As far as I can tell I’m the first one to go through it 😂🥲

Oh yeah xD it’s awesome!! docs.godotengine.org/en/latest/tu...