Scale drag handle has unexpected behavior on parts with attachments

[Beartikal]

In studio, having a Part with an attachment offsetted away from the part will cause the Scale drag handle to extend beyond the part’s size boundaries to that of the attachment’s position, making scaling with the handles behave strange and awkward. The movement and rotation drag handles do not behave like this, leading me to assume this is a bug that is not intended.

Bug behavior: The part has an attachment as a child, and the attachment has a position away from that of the part. Using the scale drag handle on the part leads to strange scale handle positions.
This bug is easily reproducible just by having a part that has an attachment as a child and then offsetted away from the part. Then, switch to resizing drag handles, and the issue is shown.

In the photo above, the scale drag handle has positioned itself away from the part and towards the attachment.

Video showing the offsetted scale drag handles:

External Media

Using movement drag handles, it behaves as expected.

Expected behavior: The scale drag handles should remain where the part bounds are and should ignore any attachment children’s positions. Movement and rotation drag handles appear unaffected by attachments.

Image of expected behavior:

Video showing expected behavior:

External Media

This appears to be a bug because the movement handle and rotation handle do not do this, even when there is an attachment as a child.

[tnavarts]

This isn’t a bug as par se.

The current behavior is that the Scale tool scales all of the content in the selection, including Attachments, Parts, and many other things. And specifically, the Attachments are included in the computation of the bounding box to scale.

Always excluding Attachments definitely undesirable, because if you’re someone working on avatar rigs, constrained assemblies, or with 3rd party plugins which use attachments to define stuff it’s sometimes convenient to be able to scale a multi-selection of multiple attachments.

The current behavior is a little bit wonky as you can see, but the the obvious way of fixing it (excluding attachments entirely) removes some functionality, so we’ve avoided it so far.

Open to suggestions on exactly what behavior you want.