Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Assimp joint transformation issue in Early Access build (3.3.0)
See original GitHub issueEnvironment
- LWJGL version:
3.3.0 - LWJGL build #:
11 - Java version:
16.0.1 - Platform:
Windows - Module:
assimp
Description
I apologize if this is not the correct place to report issues in non-release builds. If this is the case, please redirect me.
I am trying the 3.3.0 early access build and am seeing an issue with Assimp importing joint transformations. Animated models appear skewed and stretched 90 degrees in the vertical plane. The poses are timed correctly, just skewed and stretched. Static models (no joints or vertex weights) appear to import without issue.
The Assimp module from the release build (3.2.3) does not have this issue. Could it be an Assimp configuration change that I do not know about?
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The LWJGL 3.3.0-SNAPSHOT currently includes version 5.0.1 of Assimp. In particular, the commit https://github.com/assimp/assimp/commit/75144dd7fd9581888223041f62244d86198d5dca You can investigate the LWJGL 3 natives jar file of Assimp and you’ll see a
assimp.dll.gitfile in it that tells the Git commit hash. Also, there is https://github.com/LWJGL/lwjgl3/blob/master/doc/notes/3.3.0.md I am also a bit surprised that Assimp hadn’t had any release for over a year now, since 12 Jan 2020, while still the Git commits are quite active.Thanks for informing us that the issue is likely still present in the current Assimp library version. LWJGL will always try to update to the most up-to-date version of its supported libraries in a timely manner. So, we can only wait for the next version of Assimp to come out with a fix for that issue (apart from providing a PR in the upstream repo to fix it ourselves, of course), which will then make it into a new LWJGL snapshot/nightly build or release eventually. Though, I stand by my opinion that tracking every possible/conceivable bug in an upstream library also with an LWJGL bug ticket is not useful, since (as I mentioned) LWJGL will pick up with recent/new library versions anyway. So, these LWJGL bug tickets for thirdparty bugs would only be useful for being reminded of looking for updates of those third party library versions (which will happen periodically anyway).