Translate and scale controls missing from selected bone

[djoly]

Using 13.5.5 on Mac.

I notice that when I select a bone, the translate and scale control nodes are NOT visible on the selected bone, but appear on an unselected bone nearby (see pic). I end up having to click blindly where I think the controls should be, then they appear. Half the time I miss the mark, resulting in a rotation keyframe. Is this a bug, or is there a setting I can try to fix this?

I only noticed this issue after upgrading. Haven’t changed operating system version or anything else.

https://photos.app.goo.gl/HBSxMsVzMAfPAWiSA

[Daxel]

13.5.5 on W10 here. It works as intended: it doesn't matter which bone is currently selected, it shows the controllers of the closest bone to the cursor.

[Greenlaw]

Can you post the project? You can leave out the images since we only need to see the bones.

FWIW, I tried arranging bones in a demo project similar to what I see in your screen cap and it's working here. Of course, there may be something else going on in your project that's not visible.

For now, I suggest simply moving the eyebrow UP/Down bone out of the way. I normally attach my Smart Bone Dials to a mover bone so I can easily drag them out of the way of any skeleton bones that get too close or start to overlap the dials. For more info about this, see what I just posted here:

http://www.lostmarble.com/forum/viewtop ... 07#p205807

Hope this helps.

[Greenlaw]

Just to be clear, the appearance of the 'dot' widgets are not supposed to be associated with the currently selected bone. The dots move around as you hover into each bone's region, selected or unselected. This makes it easier to know which bone you are about to edit/animate when a bunch of bones are close to each other.

In short, the dots don't tell you which bone is selected, they tell you which bone you are about to select and animate.

Also, you don't even need to be clicking directly on a bone to rotate it, just be near it. It doesn't matter if the bone is currently selected or not, it just needs to be highlighted by the dots. Of course, once you start editing/animating this bone, it becomes the currently selected bone.

[ggoblin]

Do you see this behaviour where the dots appear on the bone nearest the cursor? I thinks thats normal. Or are they just stuck on one bone even if you move the cursor to the selected bone?

[djoly]

Thanks for the responses! After reading through them I realized the cause: I’m using Astropad Studio on an iPad to work through my desktop Mac. Because of that, the normal mouse hover behavior didn’t work until I set up a specific gesture to emulate it in Astropad. Thanks ggoblin for the gif and greenlaw for the great suggestions.

[Greenlaw]

That's good to know, and thanks for sharing your solution. I did wonder if this could be a tablet related issue. There have been a few curious cursor offset issues reported related to certain models of graphics tablets or tablet related settings (like Windows Ink,) and the more info the devs have the sooner they can fix issues.