All my work on Liblast is halted due to a blocking freeze bug.
I have a live presentation and workshop coming up in 4 weeks that depends on this tech, and I can't do anything at the moment.
In case you're familiar with Godot's C++ side or debugging C++ software in general, maybe you can help me out of this ditch?
Help!
https://github.com/godotengine/godot/issues/117712
Spreading the word is often a great help as well!
@unfa I'm not having the lockup issue. I am getting 28 errors on import when following your instructions but I get the below screen, and these lines on the console beyond where you lock up:
· IntroSequence: start
WARNING: 2D MSAA is enabled while there is no 2D content. Disable 2D MSAA for better performance.
at: _draw_viewport (servers/rendering/renderer_viewport.cpp:725)
[·] CVarTree: saving a read-only tree "base" to file. This is only useful for debugging.
[✓] CVarTree "base": saved to file OK
[·] IntroSequence: finished animation (intro)
[·] intro sequence finished...
ERROR: Path to node is invalid: 'Display/SubViewport'.
at: _setup_local_to_scene (scene/main/viewport.cpp:199)
GDScript backtrace (most recent call first):
[0] spawn_gui (res://addons/liblast_framework/core/core.gd:259)
[1] _init (res://addons/liblast_framework/core/core.gd:188)
[2] spawn_intro_sequence (res://addons/liblast_framework/core/core.gd:228)
[3] finish (res://addons/liblast_framework/gui/intro_sequence/intro_sequence.gd:28)
ERROR: Path to node is invalid: 'Display2/SubViewport'.
at: _setup_local_to_scene (scene/main/viewport.cpp:199)
GDScript backtrace (most recent call first):
[0] spawn_gui (res://addons/liblast_framework/core/core.gd:259)
[1] _init (res://addons/liblast_framework/core/core.gd:188)
[2] spawn_intro_sequence (res://addons/liblast_framework/core/core.gd:228)
[3] finish (res://addons/liblast_framework/gui/intro_sequence/intro_sequence.gd:28)
· CharacterSetupMenu found character body material: (res://addons/liblast_framework/data/materials/extended_materials/character_greg.tres):<ShaderMaterial#-9223371972950358403>
[·] CharacterSetupMenu found customizable color parameters: 4
This is on Linux Mint 21.3, XFCE, X11, Godot 4.6.1 .NET, AMD Radeon RX 6700.
1/2
@unfa Closing the game causes the below to appear:
WARNING: 1 RID of type "CanvasItem" was leaked.
at: _free_rids (servers/rendering/renderer_canvas_cull.cpp:2690)
ERROR: 1 RID allocations of type 'N10RendererRD14TextureStorage7TextureE' were leaked at exit.
WARNING: 9 RIDs of type "Texture" were leaked.
at: finalize (servers/rendering/rendering_device.cpp:7505)
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.6.1.stable.mono.official (14d19694e0c88a3f9e82d899a0400f27a24c176e)
Dumping the backtrace. Please include this when reporting the bug on: https://github.com/godotengine/godot/issues
Segmentation fault (core dumped)
@unfa you'll want to look at stack traces of all threads when something is hanging like that. gdb has the handy taas bt to get every thread's backtrace in just one command.
you'd probably want to see if letting the program continue for a moment lets any of the threads "do something" or if they are all waiting for something, and so on ...
@unfa I see from the GH comments that you're seeing the same behaviour even with older commits and Godot versions, which makes me suspect it's an interaction with a system library that got updated recently.
So it might be worth checking out your systems' update logs, to see what packages got updated around the time it started happening?
unfa🇺🇦
Trebach
Timo the timo
Selkcip
Gubbins