Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

[Xna/Monogame] AabbContainsPoint not working in the sample

kane

Hi,

I'm new here, currently evaluating Spine, using the XNA runtime, and so far it looks great.
But something is puzzling me, first here is the draw method from the sample:

protected override void Draw (GameTime gameTime) {
         GraphicsDevice.Clear(Color.Black);

     state.Update(gameTime.ElapsedGameTime.Milliseconds / 1000f);
     state.Apply(skeleton);         
     skeleton.UpdateWorldTransform();
     skeletonRenderer.Begin();
     skeletonRenderer.Draw(skeleton);
     skeletonRenderer.End();

     bounds.Update(skeleton, true);
     MouseState mouse = Mouse.GetState();
     if (headSlot != null) {
        headSlot.G = 1;
        headSlot.B = 1;
        if (bounds.AabbContainsPoint(mouse.X, mouse.Y)) {
           BoundingBoxAttachment hit = bounds.ContainsPoint(mouse.X, mouse.Y);
           if (hit != null) {
              headSlot.G = 0;
              headSlot.B = 0;
           }
        }
     }

     base.Draw(gameTime);
  }

I've added a breakpoint inside if (bounds.AabbContainsPoint(mouse.X, mouse.Y)), and wherever I put the mouse, it just never breaks. (using the spineboy skeleton, where headSlot is not null).
what could be wrong?

thanks a lot

kane

Mario

Is the coordinate system in which the mouse coordinates are reported the same as the coordinate system used for drawing?

kane

I don't know what spine is using as coordinate system, but the mouse should be in screen coordinate.
This can be reproduced easily, it's just the xna sample, and on my side the breakpoint never hits.

So, I did a little bit of homework and I found out that bounds.ContainsPoint(mouse.X, mouse.Y); is returning null too.
Looking at the values of bounds, it's definitely not right (see screenshot attached)
Which means the problem is more likely to come from bounds.Update(skeleton, true);

Digging a bit further, inside

SkeletonBounds.Update (Skeleton skeleton, bool updateAabb)

, I've found that the problem comes from line 66 in SkeletonBounds.cs:

BoundingBoxAttachment boundingBox = slot.attachment as BoundingBoxAttachment;

The conversion to BoundingBoxAttachment returns null, because the attachment instance is a RegionAttachment.

Mario

Yes, that is by design. You have to add Boundingbox Attachments to your models for SkeletonBounds to work. It will not work with Mesh or Region attachments.

kane

The C# runtime is weak by design indeed.

Let me be honest, this product might looks good from the outside, cause there is a nice packaging indeed,
but I can tell from the quality of the C# runtime (which is an important one) that this is technicaly weak.

Mario

Obviously I'd like to differ. This is not a runtime design issue, it's a conceptual design issue. SkeletonBounds is only meant to be used for bounding box attachments, as that's also what the editor does. You can always get the world vertices of other attachments by just inspecting their world vertices array.