Importing a mesh with armature as child object causes NPE on extracting bone data
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
crash log:
https://hastebin.com/asunagukas.sql
Easiest way around this is to just rename the parent object to Armature, and it is then imported correctly.
This happens because the Armature is assumed to be a top-level object, rather than a child of something else.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the mesh-import path that extracts bone data and reproduce the crash using a mesh whose armature is a child object. Consult the linked crash log and compare this case with the working import after renaming the parent to Armature. Done means the child-armature mesh imports without an NPE and its bone data is extracted correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100