DragonBones / DragonBones/DragonBonesUnity
Child armatures not working.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 78
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
I can confirm that child armatures/skeletons do not work. Any thoughts on where the problem might be?
A new gameObject gets created for each child armature but it has no visible mesh. Also the gameObjects for the child armatures are not parented nor part of the main armature and are just floating off in space by themselves.
It may be better to use Unity 2d sprites and have a seperate sprite for each slot or bone. Or it would at least be nice to have the option to use sprites instead of a MeshRenderer. I see there is some code in UnityFactor that is commented out and uses the SpriteRenderer component for Unity sprites, is the planned for an update or was it replaced with the current MeshRenderer implementation?
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the child-armature case and inspect UnityFactor, including the commented SpriteRenderer code and the current MeshRenderer path. Trace how each child-armature GameObject is created, then verify whether its mesh is visible and whether it is parented into the main armature rather than floating independently. Done should mean the reported child-armature behavior is fixed or the intended sprite-rendering scope is clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100