Skip to content

Conversation

@RTUnreal
Copy link
Collaborator

this helps with nixos support

@RTUnreal RTUnreal mentioned this pull request Sep 10, 2025
5 tasks
@JulianGro
Copy link
Member

Just FYI, the Windows build failing is an issue in master which I am fixing in: #1809

@RTUnreal
Copy link
Collaborator Author

I can wait and rebase it when it is merged

@JulianGro
Copy link
Member

This crashes on startup for me:

Thread 37 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff6d7fd6c0 (LWP 14962)]
0x00007ffff63c83b1 in FBXSerializer::extractMesh(FBXNode const&, unsigned int&, bool) () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libmodel-serializers.so
(gdb) bt
#0  0x00007ffff63c83b1 in FBXSerializer::extractMesh(FBXNode const&, unsigned int&, bool) () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libmodel-serializers.so
#1  0x00007ffff639dd63 in FBXSerializer::extractHFMModel(QHash<QString, QVariant> const&, QString const&) () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libmodel-serializers.so
#2  0x00007ffff63ad813 in FBXSerializer::read(QByteArray const&, QHash<QString, QVariant> const&, QUrl const&) () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libmodel-serializers.so
#3  0x00007ffff7803188 in ModelLoader::load(QByteArray const&, QHash<QString, QVariant> const&, QUrl const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libmodel-networking.so
#4  0x00007ffff77f8438 in GeometryReader::run() () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libmodel-networking.so
#5  0x00007ffff6ccff92 in ?? () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libQt5Core.so.5
#6  0x00007ffff6cccca1 in ?? () from /tmp/.mount_OverteAJKfGE/usr/bin/../lib/libQt5Core.so.5
#7  0x00007fffedc9cb7b in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:448
#8  0x00007fffedd1a7b8 in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb) 

Maybe one of the changed quantization defaults in Draco requires C++ changes on our side?

@JulianGro JulianGro linked an issue Sep 13, 2025 that may be closed by this pull request
@RTUnreal RTUnreal marked this pull request as draft September 14, 2025 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle status of Draco functions properly.

2 participants