[2.x] Consistently use the v6 Assimp binaries#2558
Merged
Conversation
…ntly use the v6 version
Beyley
approved these changes
Apr 3, 2026
github-project-automation
bot
moved this from Todo
to In Progress
in Silk.NET Development Tracker
otac0n
approved these changes
Apr 3, 2026
github-project-automation
bot
moved this from In Progress
to Done
in Silk.NET Development Tracker
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of the PR
This fixes #2556 by removing the old v5 Assimp binaries and updating the bindings to consistently use the v6 binaries.
Tested on Linux x64. I made a random animation and loaded it with the example code given in the issue.
The v5 binary gave
(0, 0, 0, 0)as the quaternion while the v6 binary gave(0, 0, 0, 1)for the second element.Related issues, Discord discussions, or proposals
Related issue: #2556
Discussion in Discord: https://discord.com/channels/521092042781229087/587346162802229298/1487541883931721929
Further Comments
I also checked the diff for the v2.23 Silk update to verify that no other native binaries had the same issue.