-
-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assimp 5.3 importer error: No suitable reader found (Linux64, Pioneer built from Master repo) #5832
Comments
This is because Gentoo ships a patched version of libassimp to work around a security issue/bug. Unfortunately, that patch completely disables the Collada importer - required to load .dae files - meaning the game absolutely cannot function at all and we cannot do anything about it. See the upstream discussion here: gentoo/gentoo#29231. The underlying bug is fixed in libassimp 5.4, which I encourage you to update to. |
I'm running into this issue on gentoo as well, but I have version 5.4.2 of assimp. This is a git build. Here are the messages I'm receiving:
|
The bug you're encountering is a completely different issue (as noted by loading a .obj file instead of .dae and the lack of a "no suitable reader found" in your logs). Please open it as a new issue if the issue persists. |
Hi, and thanks for taking a look.
Running Gentoo Linux 64 here. Building Pioneer from today's Master repo snapshot (because I am really desperate for the fix to the game-breaking bug #5804 ). All dependencies are provided as my distro's standard system-wide packages. Pioneer is built according to the provided instructions.
Interestingly enough, the binary 2024-03-14 release ran just fine with the all the same libraries (at least as fine as can be with the aforementioned game-breaking bug).
Observed behaviour
The game crashes while loading with these messages:
Expected behaviour
The game should at least load far enough to get to the main menu.
Steps to reproduce
My pioneer version (and OS):
Today's Master snapshot. Gentoo Linux 64 bit.
output.txt
Thanks for paying attention.
The text was updated successfully, but these errors were encountered: