Why are the debug results different between SkeletonViewer and Inspector?

Questions
1

I tried using Babylon.js’s SkeletonViewer. When I displayed a glTF model in SkeletonViewer, I noticed that it was different from the Debug display in the Inspector.
Why is this? Is it a problem with how I’m using it?

image
image1779×639 93.3 KB

image
image1727×627 97.8 KB

image
image1785×630 128 KB

2

cc @ryantrem

3

When you create the SkeletonViewer, you are passing in the mesh that is the root node (automatically created by the glTF loader, rather than the mesh that has the skeleton attached). So if you change your PG to reference meshes[1] and currentMeshes[1] it will work the same as in the inspector (where we search for all meshes associated with the selected skeleton). Here is your PG with this fix: SkeletonViewer Test | Babylon.js Playground

Thanks to @bghgary for the extra set of eyes :slight_smile:

4

Thank you. That was helpful.
By the way, is this option a new feature?

?inspectorv2

image
image1993×1040 217 KB

5

Oops I didn’t mean to include that in the link hah. But yes we are working on a new Inspector and will have a detailed announcement in the coming weeks!

6

It seems like it’s still a secret feature, so I’m looking forward to the announcement.

7

Nothing escapes @cx20’s watchful eyes. :wink: